Accessibility Team meeting notes – March 6, 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 implications of the recent change to the full-screen mode in the editor

The team discussed the recent change to the full-screen mode in the editor. There is a general concern about the usability and accessibility implications this new default setting will have. In particular, this change potentially violates WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.’s success criteria of Consistent navigation and Consistent identification.

@audrasjb volunteered to summarize the team’s feedback and create an issue on 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/’s 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.

Planning for the upcoming start and end of daylight saving time (DST) in some countries and regions

The team agreed to not change our meeting times for the time being. We’ll revisit this topic and adjust if necessary once all countries and regions have changed DST observance.

#meeting-notes

Accessibility Team Meeting Agenda: March 6, 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 March 6, 2020 at 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 March 6, 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

Accessibility Team meeting notes – February 28, 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.

Improve the Handbook recommendation for abbreviations and acronyms

@afercia raised that in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #46980, the accessibility team set some new practices for abbreviations (and acronyms). That would be relevant to add them to the Core Handbook section about abbreviations as well.

Basically:

  • Evaluate which abbreviations can be removed in favor of full text
  • For the other cases: provide an expansion of the abbreviation/acronym/neuronym in plain text on first use
  • Use an <abbr> to mark up the abbreviation (which provides a hint to user agents on how to announce/display the content)
  • Do not use title attributes

@audrasjb to touch base with the Docs team on Monday, to see how the handbook page could be improved.

Edit from Monday: the Docs team doesn’t manage the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook, it’s under Core team responsibility.

Accessibility team goals for WP 5.5

All the accessibility tickets in the 5.5 milestone can be found using this Trac query.

@joedolson noted that it would make sense to have as a goal is more aggressive work during alpha, so that we can dedicate more attention to the final product during 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. & RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge..

@afercia added that apart from bugfixes, it would be nice to have at least a couple user-facing accessibility improvements for 5.5.

@audrasjb noted that milestone 5.5 will be open for commit right after WP 5.4 Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 is out.

The team tried to summarize the main current projects of the team for Core and to get somebody to take point on each project:

  • Accessible color schemes: Provide some accessible color schemes for WP-Admin. Milestoned to WP 5.5. Lead: @joedolson
  • Alternative WP List Tables views: Propose an alternative way to display List Tables in WP-Admin. Milestoned to WP 5.5.
  • “Howdy fly-out menu”: Refine/replace the upper-right WP-Admin fly-out menu. Milestoned to WP 5.5. Needs someone to take the lead on this task.
  • Uniform Search: Redesign of the search in WP-Admin. Milestoned to WP 5.6 as it will need a lot of work ahead of the 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. development cycle.
  • WP-Admin Colors: Not milestoned for the moment.

Update on WP Accessibility Day

Quick update from @joedolson: It’s moving forward. Goal is to announce on March 25th; there’s a design in the works, so we’re on target. The website is currently under construction, thanks to @xkon. Regular meetings are hosted on #accessibility-events 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/. channel (requires registration).

Not much else to report right now. There is a budget mostly worked out, looking for sponsors to cover the captioning & transcription costs, etc.

Open floor

@joedolson: Ticket #49517 needs some discussion with the editor team, although it’s a very clear cut issue from the accessibility side.

@ellatrix is going to revert the related pull request on 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/.

Accessibility Team Meeting Agenda: February 28, 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 28, 2020 at 16:00 UTC.

  • Improve the Handbook recommendation for abbreviations and acronyms
  • Accessibility team goals for WP 5.5
  • Update on WP Accessibility Day
  • 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/ issues/pull requests
  • 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 28, 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).

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