Accessibility Team Meeting Notes: June 26, 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.

At the beginning of the meeting, we welcomed three new contributors: @squarebraket, @sarahricker and @azhiyadev; the last two of them had volunteered to join the Accessibility Team in view of the WordPress 5.6 special release, when they will be in charge of the accessibility focus.

Discussion about the new 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/ inserter

The first discussed item was the design difference between the preview of blocks and patterns in the Gutenberg editor and its impact on usability/accessibility.

@afercia pointed out in a comment to the umbrella issue about the inserter that two regression were introduced by recent pull requests: one is already closed, but the other issue (about the Block Inserter not constraining tabbing) is still open and should be solved in time to ship with 5.5. On the same topic, @joedolson underlined the fact that all panels should always constrain tabbing and that this should become a general pattern.

A lively debate about various aspects of usability/accessibility followed; topics discussed included:

  • consistency between the blocks panel and the patterns panel;
  • solving the double tab stop problem in the patterns preview;
  • removal of the expandable blocks groups;
  • limiting the number of patterns displayed in their panel.

Full discussion about the new Gutenberg inserter is available in Slack and a comment to the issue about accessibility improvements to the inserter will summarize the different points of view.

Discussion about alternate views for list tables

Ticket #49715 is one of the focus topic of the Accessibility Team for WordPress 5.5 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.. With 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. release approaching, the Team agreed to refresh the latest patch according to the suggestions in the last comment to the ticket, so that we can ship a sort of working “framework” to support alternate table view and iterate during next release. @audrasjb will take care of the refresh.

Related to the same topic, the Team decided to move ticket #48751 to the 5.6 milestone.

Discussion about the ‘Howdy menu’

Ticket #48894 is also one of the Team priorities for 5.5 release. Discussion had already taken place during the bug scrub: the Team decided to ship the feature as is and iterate during next release, unless there will be objections from the Design Team.

Open floor

A number of items were suggested for the open floor, but we didn’t have time to discuss all of them.

Accessibility improvements to the new ‘Plugins & Themes Auto-Update’ feature

After WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 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/., no extra steps have been made to solve accessibility issues discussed during May 29, 2020 weekly team meeting. @ryokuhi will open a ticket to address them before or during beta. (Edit: ticket #50512 is now open)

Update on prefixes to admin notices

Following last week discussion, the commit to remove of the ‘Error:’ prefix from the admin notices (discussed in ticket #47656) was reverted. Ticket #50442 to add prefixes to all admin notices was also created.

It was noted that notices in Gutenberg don’t have any prefix, so, for consistency, prefixes should also be added to Gutenberg notices. @audrasjb offered to open an issue on the Gutenberg repository.

Also, a few options to improve the accessibility of notices where added to the original ticket: @afercia volunteered to open ticket #50486 to better address them.

Open topics

There was no time to tackle other topics: they will be addressed during next meetings. Future points to discuss are all related to the Gutenberg editor:

#meeting-notes

Accessibility Team Meeting Notes: June 19, 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.

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. 🎉

After accepting nominations, I’m happy to inform that @ryokuhi has been selected as our new Team Rep. Together, we’ll be sharing Team Rep responsibilities and helping the Accessibility team make WordPress better for everyone.

Discussion of Remove ‘Error:’ prefixes from error notices as they’re redundant

We discussed Remove ‘Error:’ prefixes from error notices as they’re redundant, a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket that is proposing remove type prefixes to error messages in wp-admin.

There are various opinions around whether type prefixes, such as ‘Error’, ‘Warning’, ‘Success’, etc. are needed, or are simply redundant on wp-admin messages and notifications.

The discussion was very constructive and informative, I encourage those interested to read it in full.

We agreed that uniformity was important and that this topic is closely related to the work happening on the WP Notify feature. For now, we decided to revert the removal of the ‘Error’ prefix and gather more feedback.

#meeting-notes

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

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. nominations

The team has published a call for Team Rep nominations. We will be accepting submissions this week and will proceed with a vote during our next team meeting.

Next steps on documenting 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

The team will follow up on this task by creating a list of all the accessibility features in Gutenberg that need documenting. Once we have this list, we’ll start thinking about how we’d like to document these and where and how these will be communicated to users.

Call for testing: Removal of Infinite Scrolling from the media grid

As reported by @afercia, #50105: Remove infinite scrolling behavior from the Media grid is ready for accessibility testing. In particular, feedback is needed on focus management when new attachments are added to the media grid after users click “Load more”.

Help testing and providing feedback is appreciated on the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket linked above.

Alternate views for WP List Tables

The team also discussed #49715: Alternate views for WP List Tables as some decisions need to be made.

The conversation centered around having three different views for tables, something like compact, default, and expanded, and the possibility for a global setting to allow the user to choose which view they prefer by default.

Report on the progress made during 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/.

Team members that facilitated during WCEU Contributor Day reported on the progress made during the event.

Along with attendees, the group worked on a ticket for the Plugins & Themes Auto-update feature and also worked on reporting an issue and submitting a pull request in the Gutenberg 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.

#meeting-notes

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 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 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 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 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

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

WCEU 2020 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/. tasks

In preparation for WCEU 2020 contributor day, the team continued discussing the tasks that need to be addressed before the event. Most of these tasks already have an owner and progress is being made.

5.5 work updates or requests for help/feedback

@ryelle, @joedolson and @nrqsnchz continued the discussion on the Accessible Color Schemes project. It was decided to start creating mockups for high and low contrast, and light and dark color schemes.

Open floor

@joedolson made the team aware of a request to present at WP Campus Online about the status of the Gutenberg accessibility audit performed last year.

#meeting-notes

Accessibility Team meeting notes – April 24, 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.

Progress report on 5.5 work

The team has been making progress towards our planned work for the 5.5 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.:

@afercia noted that some of the 5.5 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets might need to be pushed to the Editor and Media teams and that we need to know who the release focus leads are for those teams so we can refer to them.

@ryelle created this Trac ticket to move forward the discussion around creating new color schemes. @ryelle, @joedolson, and @nrqsnchz agreed to continue the discussion after the meeting.

@audrasjb has a patch ready for the WP-Admin fly-out menu ticket and is working on a first draft for the Alternate List Tables work.

Anyone interested in getting involved on any of these projects is encouraged to reach out. Your help is needed.

WCEU2020 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/. team tasks

We continued discussing the tasks that need our attention for Contributor Day during WordCamp Europe 2020. We’ve set up a spreadsheet in order to keep track and review progress.

@ryokuhi, @joedolson, and @nrqsnchz have signed up to help facilitate during the day. We still need more folks to sign up in order to be able to more comfortably cover all the hours needed.

We also discussed how many working groups we expect to need and also be able to handle. We agreed that two working groups divided by level of experience contributing to WordPress would be a good plan.

Folks interested in helping on any of these tasks are welcome to chime in too!

Open floor

@ryokuhi reminded everyone that the WordPress Accessibility Day website will be going live next week.

Next WPAD planning meeting will be held on Wednesday, 29 April at 16:30 UTC.

#meeting-notes