Accessibility Team Meeting Agenda: June 12, 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, June 12, 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, June 12, 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: June 5, 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.

Documentation 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/’s accessibility features

We continued the discussion about documenting the features present in Gutenberg that help make the editor more accessible and the best way to bring awareness to them.

We agreed that this documentation should be easy to find and not buried or hidden under a menu. Some of the features we think would make part of this documentation are:

  • Edit and select modes
  • 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. 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. and block breadcrumbs
  • Top toolbar
  • Spotlight mode

We agreed to continue this discussion next meeting.

Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nominations

As @audrasjb steps down from being a team rep to focus more of this time on the Core team, the team is planning to launch new team rep nominations during the next team meeting. @nrqsnchz will continue to be team rep and the new person to fill JB’s place will share tasks and responsibilities with him.

Open floor

@afercia reminded everyone of the list of tickets that need help from the Editor and Media teams. @audrasjb will be reaching out to those teams.

Andrea also asked if there has been any progress or updates on the PR for addressing accessibility concerns of WritingFlow. There’s been consensus around creating a setting to turn this feature on and off and those involved are currently discussing how to call this setting in the PR.

#meeting-notes

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

  • Continue the discussion from last week on the documentation of the accessibility features 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/
  • Start nominations for a new team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.
  • Open floor

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, June 5, 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).

#agenda

Accessibility Team Meeting Notes: May 29, 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.

Prototype: move blocks between levels with keyboard

The team discussed this 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/ PR that explores adding the ability to move blocks in and out of nesting levels with keyboard only.

We agreed that is is a very welcoming and promising exploration. There was a particular interest in figuring out what would be the best way to communicate these position changes to screen readers.

Accessibility audit of the new auto-update feature for plugins and themes

We discussed the recently merged auto-updates feature for plugins and themes from an accessibility perspective. There was discussion about how links that act like buttons should be handled, clarity of announcements, hiding icons, and button labels that change.

@ryokuhi had the excellent idea of bringing some of these issues to next week’s WCEU contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

Please refer to the Slack discussion for a more detailed overview.

Documentation of Gutenberg’s accessibility features

We discussed how to better inform users of the various accessibility features that are present on 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. The idea of creating documentation and adding a link to it, such as “Accessibility Help” was well received.

We agreed to bring back this topic on next week’s meeting and look at all the different accessibility features and options that would be useful to have documented.

#meeting-notes

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

  • Help test and provide feedback on Prototype: move blocks between levels with keyboard
  • Discuss an accessibility audit of the new auto-update feature for plugins and themes
  • Discuss documentation 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/’s accessibility features

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, May 29 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 – May 22, 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.

Preparations for team facilitators for WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

Those of us who have signed up to help and facilitate during WCEU contributor day were made aware of the latest updates and requests from the organizing team.

Updates on 5.5 projects

@audrasjb updated the team on the progress of Alternate list views, which is ready and awaiting reviews.

@afercia also shared that the removal of infinite scrolling from the media grid is also ready and waiting and accessibility review.

If you can, please help review those tickets and leave your feedback.

@nrqsnchz shared a WIP mockup of a dark, high-contrast theme for wp-admin as part of the accessible color schemes the team is working 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/ issues

Edit mode: arrow up/down should not move to other blocks

The team continued the discussion on this Gutenberg PR that looks to improve navigation for screen reader users when in Edit mode.

We agreed that creating a setting or option that enables or disables WritingFlow would be a favorable path forward. There are still concerns about how this setting would be called and how obvious it could be. @alexstine left a summary of the team’s discussion on the initial issue.

Add screen reader only text format

The team also discussed this Gutenberg issue that proposes adding a text format option to mark text as screen-reader only.

The team agreed that this is a very interesting suggestion that could be beneficial in a variety of use cases. There is also concern about possible abuse or misuse of such feature, and the negative implications that it could have for accessibility.

@nickthegeek added a summary of our discussion to the issue.

#meeting-notes

Accessibility Team Meeting Agenda: May 22, 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, May 22, 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, May 22, 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 – May 15, 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.

Sort any remaining tasks for WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

The team tackled the remaining tasks due for WCEU 2020 Contributor Day. We set May 28, 15:00 UTC, as the time to hold office hours in our 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. @ryokuhi, @audrasjb, and @nrqsnchz volunteered to help.

Review 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/ issues

The team reviewed and discussed two Gutenberg issues from an accessibility perspective.

The first issue was Improve “Visibility” and “Publish” labels in Post Settings, where a better, more accessible way for displaying these statuses is being explored.

We agreed that the last suggestion should be evaluated and followed up.

The second issue reviewed was Edit mode: arrow up/down should not move to other blocks. This is a PR that aims to change keyboard navigation on edit mode in order to avoid an unexpected switch between blocks that particularly affects users of assistive technologyAssistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the technology needed to accomplish such tasks. https://en.wikipedia.org/wiki/Assistive_technology.

We couldn’t cover a full discussion and analysis so we agreed to revisit this topic at the next meeting.

#meeting-notes

Accessibility Team Meeting Agenda: May 15, 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, May 15, 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, May 15, 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).

#agenda

Accessibility Team meeting notes – May 8, 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.

Announcing the first WordPress Accessibility Day!

The first ever WordPress Accessibility Day was just announced this week:

Starting at 18:00 UTC on October 2nd, 2020, the WordPress Accessibility Team will sponsor a 24-hour online event focused on WordPress and Accessibility. If you want to learn about the future of accessibility in WordPress, join us for 24 hours of mind-expanding online learning!

Speaker submissions will be opening soon, so keep an eye on wpaccessibilityday.org.

A big round of applause to all the folks who’ve been working hard on planning and putting together this event. Please spread the word!

Review 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/ PR

The team reviewed and discussed this Gutenberg PR that implements the roving tabindex pattern on 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. toolbar.

We agreed that this is a welcoming change but expressed concerns on how a change like this could be communicated to end-users.

Open floor

@afercia shared the work he’s been doing on #50105. Feedback and help testing the patch is needed.

#meeting-notes