Accessibility Team Meeting Notes: September 25, 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.

Accessibility review of toolbars in the 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. editor

We reviewed and discussed a few issues that introduce new editing functionality to the block’s toolbar. We agreed that replacing elements “on the fly” was not a recommended pattern. It unexpectedly removes elements from the DOM and can break expected interaction.

We support a solution currently being explored in this Gutenberg PR and will test it once the code is ready.

On-demand announcement to screen readers via a keyboard shortcut of the block’s contents

We also discussed this proposal on a Gutenberg issue that suggests providing a keyboard shortcut to allow screen reader users to hear the full contents of a block when triggered.

There are concerns about keyboard shortcut conflicts and of adding more shortcuts to an ever-growing list. There is one solution currently being explored on this issue in the Gutenberg repo that will allow users to customize keyboard shortcuts. We think that it might help alleviate these concerns.

We also discussed the possibility of adding a skip-link that will let keyboard users quickly jump to and find the list of available shortcuts. We think it’ll be useful to explore.


WordPress Accessibility Day

We were also reminded that WordPress Accessibility Day is next week, October 2nd, 2020 at 17:45 UTC. Make sure to add it to your agenda and the organizing team is still in need of volunteers.

#meeting-notes

Accessibility Team Meeting Agenda: September 25, 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, September 25, at 15:00 UTC..

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, September 25, at 14: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: September 4, 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.

Organization of an extra meeting to discuss specific 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

The team discussed adding an additional one-off meeting to address specific Gutenberg features for the WP 5.6 release that require special attention.

Given that there was no consensus on a date and time for this meeting, we will be using our regular meeting time next week to discuss and address these issues.

During the discussion, it was also proposed for the Accessibility and Design teams to hold office hours once a week. As suggested by @sarahricker:

It is intended a place for general feedback re: Gutenissues and to get a few eyes on big issues so they can be brought to light quicker. And to help anyone who needs help with 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) concepts.

The team thought this to be a great idea and are looking forward to hear more and participate. Be on the lookout for more information coming soon from @sarahricker and @karmatosed.

Adding a screen reader announcement to the last 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. in a list

We finished discussing this Gutenberg issue that proposes to add a screen reader announcement to last block in the block list by @alexstine.

The team agreed this is a good idea and should be tried and tested in a PR.

Adding a 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. for navigating template, posts, and pages inside the block editor

We discussed this Gutenberg issue that explores a new sidebar UI for navigating between templates, posts, and pages without leaving the editor.

A concern around having too many sidebars (and sidebars in general) and how this new one being explored looks different was raised, and an argument in favor of hierarchy and information architecture was also brought up.

The feedback will be added to the issue.

The image block’s editing tools break the toolbar keyboard accessibility

We also looked at this issue that reports that the image block editing tools are triggering a focus loss, thus affecting keyboard accessibility of the toolbar.

We discussed alternatives worth exploring and will leave feedback in the issue.

#meeting-notes

Accessibility Team Meeting Notes: August 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.

WordPress 5.5 release post-mortem

The team shared and discussed what we thought went well and went wrong with our team’s projects and tasks during the release of WordPress 5.5.

The issue of not enough early involvement and feedback during design and development updates to the 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. editor was brought up a few times and discussed at length. We all agreed that the process needs to be improved and our team is still very limited in terms of time and resources.

We agreed to explore solutions and ideas that would help us improve this cycle and follow-up in a separate document or post. @sarahricker volunteered to put all of this feedback together.

Team goals and priorities for WordPress 5.6

We reviewed the suggested projects and priorities that were added to the call posted earlier this week. After some discussion and a show of hands, the following projects gathered enough interest and participation:

  1. Updating the WordPress Accessibility coding standards from 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/. 2.0 to WCAG 2.1 and document accessibility anti-patterns
  2. Accessibility of the WordPress 2021 default theme
  3. A feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. to create an “Accessibility Statement” tool with features equivalent to Privacy Policy Tools

All other items on the agenda that couldn’t be covered will be added to next week’s meeting agenda.

#meeting-notes

Accessibility Team Meeting Agenda: August 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, August 28, at 15:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the team in the #accessibility 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.

The Accessibility Team bug scrub will be held on Friday, August 28, at 14:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).

#agenda

Accessibility Team’s goals for WordPress 5.6 and beyond

Following a pattern established during the last WordPress releases, it has become common for the WordPress 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 to set targets for each release during the final stages of the previous one.

Given the heavy involvement of the Team between 5.5 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 and the 5.5 release, it was impossible to discuss possible goals before. Also, given that the kickoff meeting for WordPress 5.6 took place on Wednesday, 19th August, this discussion can’t be delayed anymore.

As such, the Accessibility Team is going to discuss possible targets for WordPress 5.6 during the next weekly meeting, which will take place on Friday, 28th August, 2020 at 15:00 UTC.

If you have an accessibility goal you would like to see the team pursue on WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., you are more than invited to add it in the comment section below and let us know. You are then invited to attend to the next weekly meeting, when possible goals will be discussed and prioritized.

If a certain goal won’t be selected for the 5.6 release, it can always be included in the list that will be created for the 5.7 release.

While a strict timeline can’t be set too many months in advance, the next Call for Accessibility Team’s goals will likely be published around Friday, 13th November, 2020, that is, the Friday before WordPress 5.6 RC 1. Possible goals will then be discussed during the weekly meeting on Friday, 20th November, 2020. Around the same time, an extra bug-scrub to identify possible good-first-bug Core tickets and 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 will take place.

All the above dates are flexible and can be changed according to specific needs, in particular in case they run the risk of detract from bug fixing during 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..

Such an early planning will probably become even more useful with next releases, given that four major WordPress releases are already planned for 2021 and each release cycle will be shorter. Planning in advance possible goals during Release Candidate will also allow contributors to have a break in between releases, reducing possible sources of burnout.

#5-6, #goals

Poll: Accessibility Team meeting day and time

Following the tie between moving the meeting to Tuesday, at 15:00 UTC, and keeping Friday, at 15:00 UTC as the meeting time, we decided to hold another round of voting to break the tie.

We’ll keep the new poll open until Friday, August 21, 2020, at 15:30 UTC, and will review the final count during our team meeting.

Please cast your vote.

Accessibility Team Meeting Notes: August 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.

Review poll results for the proposed changes to the team meeting day and times

Following the discussion and voting for a new meeting day and time, the team reviewed the result of the poll. We had a tie between two options: moving to Tuesday, at 15:00 UTC, and keeping Friday, at 15:00 UTC as the meeting time.

We decided to hold another voting round in order to break the tie. Please cast your vote on the new poll.

Discussion about updating the WordPress Accessibility coding standards to 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/. 2.1

The team agreed that with the WCAG 2.2 draft already having been published, it was time we updated the WordPress coding standards to conform to WCAG 2.1, level AA.

We think it would be great to aim for the updated coding standards to be updated along with the upcoming 5.6 release. @sarahricker, @azhiyadev, @joedolson, and @nrqsnchz agreed to form a squad and start coordinating the work that will be needed, such as writing the requirements and creating some examples.

Advancing the Editor Interface

The team reviewed this new proposal from @itsjonq that looks to create a new foundation for the WordPress components library. The goal is to make it easier for contributors to create cohesive interfaces and conform to standards and best practices.

While still in the early stages, this proposal can have a great impact by standardizing and enforcing the accessibility of the components we use to build WordPress.

#meeting-notes-2

#meeting-notes

Accessibility Team Meeting Agenda: August 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, August 14, 2020, at 15:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, August 14, 2020, at 14: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).

Accessibility Team Meeting Notes: July 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.

This week we decided to continue the discussion around 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. focus outlines that started during the accessibility bug scrub right before our team meeting.

Rather than try to summarize it, I encourage those interested to follow the discussion in Slack.

We agreed to revisit this topic and discuss possible proposed solutions during our next extra bug scrub planned for Tuesday, August 4, 2020, at 15:00 UTC.

We also agreed to revisit the agenda items planned for today’s meeting during our meeting next week.

#meeting-notes-2