X-post: Daylight Saving Time Meeting Planning

X-comment from +make.wordpress.org/updates: Comment on Daylight Saving Time Meeting Planning

Accessibility Team meeting notes for February 21, 2020

These are the weekly notes for the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Discussion on the Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. testing

A few weeks ago, we started doing a11y testing on a new navigation menu block in Gutenberg. @nrqsnchz will be moving the results of these tests into GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository.

It’s important to note that the release of the navigation menu block was postponed.

Discussion of team involvement in Gutenberg development

We continued the discussion from last week regarding the team’s participation in the Gutenberg repository in GitHub.

There was a general consensus that being a small team, our time and bandwidth are limited. That being said, we’d still like to add a couple of items to our team process to try to mitigate this.

We agreed to start raising two Gutenberg issues that need accessibility feedback each week during our team meeting.

We’ll also look at adding a SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. – GitHub integration to our team channel that posts issues that need accessibility feedback. We’ll give this integration a try and keep it if it’s working, or remove it if we find that it adds to much noise to our channel.

Another idea that was suggested was to add an additional Gutenberg-specific bug scrub session to our meeting schedule. This could be weekly, or perhaps every two weeks. Would you be interested in participating in these additional triage sessions? We ask members of the team to add their comments and suggestions in the comments of this post.

Improve the small user sub window at the right corner on the admin bar

We discussed this Trac ticket about usability issues of the ‘My account’ dropdown menu (also known as the ‘Howdy fly-out’) in wp-admin.

The team agreed that accidental triggers are common with this menu, and argued the importance and relevance of its contents.

@danihooven, @joedolson, and @afercia (a.k.a. ‘The Howdy Force Team’) agreed to continue researching this ticket and will be following up.

#meeting-notes

Accessibility Team Meeting Agenda: February 21, 2020

This is the proposed agenda for the weekly accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting on Friday, February 21, 2020, 16:00 UTC.

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday, February 21, 2020, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#meeting-notes

Accessibility Team meeting notes for February 14, 2020

These are the weekly notes for the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Discussion of the updated button component in 5.4

We discussed a recent update introduced to the Button component in 5.4. The team agrees that the implementation of fixed heights in buttons will break accessibility. Furthermore, this goes against the recent CSS changes introduced to wp-admin in 5.3

This topic led to a discussion about processes, the pace of development of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, and communication between teams. We agreed to come back to this concern next week, and address how, if possible, the Accessibility team can be more involved in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository.

Feedback on the TabPanel component

We discussed this issue in the Gutenberg repository that requires accessibility feedback. A decision needs to be made in terms of how keyboard navigation should behave in a tabbed interface. We currently implement custom navigation for the tabs located in the editor inspector (Gutenberg sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.), while the WAI-ARIA Authoring Practices recommend a different approach. A summary of our feedback will be posted on the issue.

#meeting-notes

Accessibility Team Meeting Agenda: February 14, 2020

This is the proposed agenda for the weekly accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting on Friday, February 14, 2020, 16:00 UTC.

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday, February 14, 2020, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Accessibility Team meeting notes for February 7, 2020

These are the weekly notes for the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Discussion on the accessibility status of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.

Discussion continued from last week on the topic of the accessibility status of the Gutenberg blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. inspector (sidebar).

The team had a very productive discussion that addressed the longstanding accessibility issues, recent improvements, and suggestions for solutions.

The team agreed to work together on a proposal that described the problem, suggests needed structural changes, and provides visual concepts.

Once 5.4 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. is out, @joedolson, @afercia, and @nrqsnchz will collaborate to create the proposal.

Status update on 5.4 tickets

@audrasjb shared the status of the accessibility tickets in the 5.4 milestone in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. At the time of writing, there are 36 in the milestone, of which

  • 5 are closed as fixed
  • 4 are open and tagged for commit

Because Beta 1 is planned for February 11, the next a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) bug scrub (February 10, 2020, 17:00 UTC) will most likely focus on punting tickets for future releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..

There are still a few tickets that could be worked on and still make it in. Help on moving these forward is much appreciated.

#meeting-notes

Accessibility Team Meeting Agenda: February 7, 2020

This is the proposed agenda for the weekly accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting on Friday February 7, 2020 at 16:00 UTC.

  • Discussion on the accessibility status of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme..
  • Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. tests results.
  • Status update on 5.4 tickets.
  • Open floor

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday February 7, 2020 at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

WP Accessibility Day: Planning meeting 3

WP AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Day planning continued on Tuesday, 22 January, 2020

Slack transcript

Updates from Community Team

No existing guidelines about support, but we can provide a list of needs & they can let us know how they can help. Dates are up to us.

@nataliemac volunteered to start developing a budget

@xkon volunteered to offer advice from WP Translation Day experience.

@audrasjb Learned that we need to secure hosting & domain name for ourselves, and will touch base with sponsors to provide this.

Design phase

Design team is established, will meet before the next meeting to start planning. Will use WP Accessibility GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ team to coordinate development.

Date Commitment

Committed to September 26th. Some possible events we want to avoid collision with aren’t announced, so we can’t make plans around those.

Timing will be 24 hours, midnight to midnight UTC.

Next meeting:

The next meeting will be Wednesday, February 5, 2020, 16:00 UTC

Accessibility Team meeting notes for January 31 2020

These are the weekly notes for the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Incorrect cursor used on buttons

The accessibility team has made a final recommendation on this ticket from the WPCampus accessibility report. The pointer cursor should be reserved for links, and an affordance for buttons can be communicated in other ways, such as noticeable hover and focus styles.

Disabled button doesn’t look disabled

The team also shared their recommendation on this ticket about disabled button styles. Because contrast requirements don’t apply to disable interface controls, we don’t have any issues with the design team making a call on changing this.

Video blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. settings for alternate sources

The team agreed to have a more broad-ranging conversation about the accessibility of navigation to and from the block inspector (sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.) in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. We’ll continue this discussion at next week’s meeting.

Feedback on the Navigation block

Members of the team are encouraged to try out the Navigation block in Gutenberg and provide feedback. We’ve created a spreadsheet to collect everyone’s results.

#meeting-notes

Accessibility Team Meeting Agenda: January 31, 2020

This is the proposed agenda for the weekly accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting on Friday, January 31, 2020, 16:00 UTC.

  • Incorrect cursor used on buttons: this TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket needs a decision from the accessibility team.
  • Disabled button doesn’t look disabled: another Trac ticket that could use our collective feedback so it can move forward.
  • Video Block: alternate sources such as ogv and webm file formats: GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ issue that needs the team’s feedback.
  • Test the Navigation block: Last week the design team asked our help with testing the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.. If you can, please add your feedback and comments to the linked spreadsheet.

The Accessibility bug scrub will be held on Friday, January 31, 2020, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda