Accessibility Team Meeting Notes: June 17, 2022

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 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 and find the meeting’s agenda here.

Team contributions to the Developer Resources blog

@bph joined our meeting to get in touch with our Team Reps regarding how we might be involved (editorial board) in a new blog project for the developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ website. A follow up should be out next week or so. Discussion points included:

  • The time this extra activity would stretch the team reps may drain resources needed here.
  • This could be a good opportunity to bring content added to our team’s documentation to a broader public.
  • @Hauwa Abashira offered to coordinate efforts between Learn and Accessibility; and
  • If you have other questions or if you want to be part of this effort, contact Birgit via Direct Message.

Pull Request about accessibility enhancements to Writing Flow in Gutenberg

@alexstine reported that this is a big improvement for blocks that are not single fields such as paragraph, heading, list, etc. There are 2 major adjustments. Kudos to Alex for this massive achievement.

No team updates or Open Floor items Due to the length of the discussion and updates a brief period was set aside here. Next week, bug scrub.

#meeting-notes

Accessibility Team Meeting Notes: May 20, 2022

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 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 and find the meeting’s agenda here.

Updates from Make Accessibility Working Groups

NOTE: Only groups that provided updates are shown below.

Documentation

@Hauwa Abashiya reported that @joedolson made an update to the Accessibility Handbook: How to Report Accessibility Issues. A note added about finding existing tickets and commenting at the top, and added an item about reporting 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/full site editing issues, as well as some formatting/language adjustments.

Gutenberg

@alexstine reported a few recent A11Y fixes. Other than that, really need feedback on this discussion. Help implementing would be great too. #38311 Improve keyboard navigation experience in all the block editors. He also mentioned wanting to make sure "we’re going down the right path. My latest comment called for a ton of changes and really needs a second set of eyes. Also, on the off chance this channel picked up any ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. devs is interested in contributing."

Open floor

@alexstine broached a topic for discussion — Due to 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 2022 (2-4 June), should the Accessibility Team meeting be rescheduled on June 3rd or be canceled? If canceled, the next meeting will not be until June 17th. He would be in favor of having next meeting on June 17th. #pizzatime

#meeting-notes

Accessibility Team Meeting Notes: April 15, 2022

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 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 and find the meeting’s agenda here.

Updates from the working groups

Only groups that provided updates are shown below.

Documentation

@joedolson proposed some documentation for the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party handbook, but there hasn’t been any movement there yet. Since 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. 1 is now released, he and @azhiyadev hope to have more time to follow up on that in the next weeks.

General

@ryokuhi reported that in the last few weeks, the Accessibility Team has been focusing on tickets milestoned for 6.0, so that they could be included in 6.0 Beta 1 (and, as a consequence, in the 6.0 release itself). In the next few weeks, the group is going to pick up with tickets in the Awaiting Review queue, which have been piling up a bit, and it’ll make sure to solve all bugs introduced during Alpha.

20 tickets with the accessibility focus have been closed in the 6.0 release to this point, a very good result. Special thanks go to @sabernhardt and @afercia for working on the code for Quick & Bulk Edit, which is now accessible to keyboard and screen reader users.

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/

@alexstine reported that there is a post coming out soon to track the accessibility of Gutenberg for the upcoming 6.0 release. The biggest issue he reported is that it’s very difficult to keep track of accessibility Pull Requests in Gutenberg because it’s hard to say when they’ll go from trunk to release. @alexstine also reported that he’s currently working on an issue about focus loss after selecting an option from the "Select Menu" dropdown and that his current focus is on some reusable elements of Gutenberg, which will have an effect on the whole Gutenberg project (including Full Site Editing).

@ryokuhi quickly apologized for not dedicating enough time during bug-scrubs to issues with 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, despite the Team had selected this as a main goal for the 6.0 release. As a possible solution, he suggested not to milestone too many TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets for 6.1, so that there is time to focus on issues with the block editor, and to dedicate specific bug-scrubs to Gutenberg in between releases.

Media

@joedolson reported that, while most of the media changes committed for the 6.0 release were minor tweaks, last week he also committed several changes relating to mobile views that are steps on the way towards redesigning the image editor.

Open floor

@joesimpsonjr asked how Team members felt the 6.0 release reflected some of the improvements desired from an accessibility standpoint. @joedolson‘s feeling is that the Team did well in targeting coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. goals, and pretty well in tackling block editor issues, but still it didn’t accomplish much at all in the way of looking at Full Site Editing.

#meeting-notes

Accessibility Team Meeting Notes: April 1, 2022

These are the notes for the Make 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 meeting, that occurred Friday, April 1, 17:00 UTC. @joesimpsonjr filled in for @ryokui for this meeting. You can read the entire meeting transcript on 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 and view the Meeting Agenda here. The meeting begins on time at the conclusion of the bug scrub led by @sabernhardt, a welcome to new attendees with introductions, and rules for a family-friendly meeting.

Updates from working groups

  1. Report from Documentation Team@joedolson has been coordinating with @Hauwa Abashiya to follow up on the docs she brought last week, so those are progressing. For better clarity, I’m going to create a fully-realized demo of wp.a11y.speak() and place it in the wpaccessibility 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/ repo. He also been working on getting an accessibility doc added to the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developer’s handbook. Accessibility Document can be found here. Practically, only the main page probably needs to be in the plugin handbook; the four sub sections might be good additions to our handbook;
  2. Additional Report from Documentation Team@sabernhardt provided more General Updates later:
  • WordPress 6.0 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. 1 is April 12, with 20 tickets left in the 6.0 milestone.
  • Today’s bug scrub covered the 8 features and enhancements.
  • There are also 12 open bug tickets with the same deadline.
  • The Awaiting Review queue has 7 tickets, with only one opened since last week; and
  1. Report from 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/ Team@alexstine reported that Add screen reader instructions for navigating child blocks on block selection is currently blocked. @joedolson also asked for an update on #35483: Accessibility improvements for the Bulk Edit form

Open Floor

Our weekly meeting closed with this comment: @joesimpsonjr mentioned he is a Team Captain on the 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. US organizing team for this year’s event on September 9 through 11 in San Diego, California. It is in-person (if things continue to progress from a health perspective), but I wanted to invite anyone to participate:

#accessibility, #accessibility-docs, #meeting-notes

Accessibility Team Meeting Notes: March 18, 2022

These are the notes for the Make 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 meeting, that occurred Friday, March 18, 17:00 UTC. You can read the entire meeting transcript on 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 and view the Meeting Agenda here. The meeting begins on time at the conclusion of the bug scrub, a welcome to new attendees with introductions, and rules for a family-friendly meeting.

Updates from working groups

  1. Report from Design Team@ryokuhi is testing the change from the hash to the link icon in documentation, which is an improvement;
  2. Report from Documentation Team — There are two code snippets for @joedolson for review that @Hauwa Abashiya posted in the #accessibility-docs channel; and
  3. Report from General Team — The team is still keeping the awaiting review queue under control; There is one ticket milestoned for the 5.9.3 (the one about the accessibility-ready label for Twenty Twenty-Two); There are 7 tickets milestoned for 6.0 and marked as enhancements or feature request; and There are 17 tickets milestoned for 6.0 and marked as enhancements or feature request; Also, the feature freeze deadline was cancelled, so there’s no more need to differentiate between type of tickets. Finally, 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. 1 will be on 12 April, which leaves this team one extra week to work on tickets in this milestone.
  4. Report from Gutenberg Team — This team landed several big accessibility improvements to 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/ as described by @alexstine:

These updates ensure there will not be any regressions for list view in the future.

  • https://github.com/WordPress/gutenberg/pull/39302
  • https://github.com/WordPress/gutenberg/pull/39265

List view improvements:

  • https://github.com/WordPress/gutenberg/pull/38639
  • https://github.com/WordPress/gutenberg/pull/38679

Best of all, this adds much better support for blocks without the contenteditable attribute. Still a lot of work to do but heading in right direction.

  • https://github.com/WordPress/gutenberg/pull/37934
  1. Report from Themes Team@joedolson reported that there has been a fair amount of movement on https://github.com/WordPress/gutenberg/issues/39266, with the goal to create a mechanism for viewing & testing the output of blocks. A couple of PRs already available with ideas, plus another tool that could be incorporated into core to generate the data. This development is promising that they will be reaching the point where we can do proper testing of all of that output in a solid, reusable model. This is a very important step for serious auditing of block output and open a pathway for FSE theme to be considered accessibility-ready.

Open Floor

Our weekly meeting closed with this comment:

  • @ryokuhi won’t be able to attend the April 1 and possibly the April 15 meetings and @alexstine and @joesimpsonjr will fill in. Thanks for the huge amount of work accomplished and to everyone for attending.

#accessibility, #meeting-notes

Accessibility Team Meeting Notes: March 4, 2022

These are the 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 every other Friday. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Revision of meeting and bug-scrub times

In view of the switch to Daylight Saving Times in various parts of the Northern Hemisphere, the team agreed to keep the current starting time for bug-scrubs (16:00 UTC) and meetings (17:00 UTC) until the end of March. Beginning with 1 April 2022, weekly bug-scrubs will be held every Friday at 15:00 UTC and meetings will happen on the first and third Friday of each month at 16:00 UTC.

Team involvement during 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

Members of the organizing team of WordCamp Europe reached out to the team to discuss how the accessibility team could be involved in the activities of WordCamp Europe, especially during the 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/. happening on 2 June 2022. @ryokuhi plans to attend and already made himself available to facilitate work at the accessibility table.

On the other side, it’ll be very difficult for the accessibility team to facilitate also a second accessibility table dedicated to the Accessibility WP Theme Auditor, as suggested: the people who were coordinating the project at the time are no more active in the accessibility team and the team size has shrunken since last WordCamp Europe. As such, the team agreed to focus on a single accessibility table.

If someone else is attending WordCamp Europe, and if they are available and willing to contribute to the activities of the accessibility table during the Contributor Day, they can reach out to @ryokuhi on 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/. either directly or in the #accessibility channel.

Updates for the working groups

Only groups that provided updates are shown below.

Documentation

@azhiyadev reported before the meeting that there are no updates from the group.

General

The group continues to monitor tickets in the Awaiting Review queue, to avoid them piling up. There are 2 tickets milestoned for 5.9.2, which the group is monitoring. There are 9 enhancement or feature request tickets milestoned for 6.0, with two more weeks to get them committed. There are 15 bug tickets milestoned for 6.0, with four more weeks to get them committed.

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/

Before the meeting, @getdave shared a Pull Request about converting classic menus in block ones that will probably benefit from some feedback from the team.

@isabel_brison left a comment to the meeting agenda (apologies for not mentioning it during the meeting), asking for feedback on an issue about keyboard shortcuts and the best alternatives to the current 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 setup. List View is crucial to accessible navigation of the editor content, so it would be good to ensure that the shortcut to open it works across all screen readers. In order to include this feature in the 6.0 release, it should be ready before 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. 1, which leaves not too much time to work on it.

Media

@joedolson reported that work is in progress; as the features the group is working on are quite complicated, it isn’t easy at the moment to predict what will make it in the release. A couple of easy fixes should be done in about a week.

Themes

@joedolson reported that he’s working to identify some better workflows for testing Gutenberg blocks. Given that the accessibility of Full Site Editing themes is highly dependent on the output of blocks, this is extremely important to assess if such themes are accessibility-ready.

Open floor

No topic was raised during open floor.

#accessibility-docs, #meeting-notes

Accessibility Team Meeting Notes: February 4, 2022

These are the notes for the Make 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 meeting, that occurred Friday, February 4, 17:00 UTC. You can read the entire meeting transcript on 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 and view the Meeting Agenda here. The meeting begins on time at the conclusion of the bug scrub, a welcome to new attendees with introductions, and rules for a family-friendly meeting.

Updates from working groups

  1. Report from General Team — Since it is right after a major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality., they’ve been focusing on issues milestoned for the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.. And they’re checking issues in the awaiting review queue, to avoid things piling up. There’s no set timeline for the 6.0 release yet, so, if possible, we’ll try to dedicate more time during bug-scrubs to 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.
  2. Report from Gutenberg Team@alexstine brought Ticket #37934 Fix useFocusFirstElement in non-contenteditable Blocks up for discussion, stating that this item could use a lot of testing. The code used was great for older Blocks but not as good fro the newer ones. Suggestion by @joedolson is to try to replicate the scenario described in the "How has this been tested?" section. Questions like, "is there a list of blocks this issue applies to?" assuming it not only applies to columns but also groups, etc. Groups will be harder (to test) because there is nothing currently in a Group 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. right now that will receive focus because they are all child Blocks. This will be improved in future pull requests, making sure every Block has at least one focussable element. There should be some improvement with the Columns Block. Finally, this does work despite the failing tests meaning @alexstine will need to track down some dedicated help to debug.
  3. Report from Media Team — Most of the goals for media are set. There are a handful of accessibility issues to tackle. Time permitting, Joe will add some other things, but if the admin image editor redesign is going to have any feasibility, he can’t add much more.
  4. Report from Meta Team — Although there was a member present to report, the big change is the new headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. across .org. It could probably stand a review, if anybody has time. There is one bug that needs to be reported, but could use further investigation.

Open Floor

Our weekly meeting closed with these comments:

  • Destiny asked how the Learn session prep going and volutneered to assist if needed; and
  • To catch up on team news, goals, and more articipants were pointed here to get meeting recaps, agendas, and upcoming meeting information.

#meeting-notes, #training

Accessibility Team Meeting Notes: January 21, 2022

These are the notes for the Make 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 meeting, that occurred Friday, January 21, 17:00 UTC. You can read the entire meeting transcript on 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 and view the Meeting Agenda here. The meeting begins three minutes after the hour at the conclusion of the bug scrub, a welcome to new attendees with introductions, and rules for a family-friendly meeting.

Review Goals for WordPress 6.0 Release

Discussion of Goals for WordPress 6 Release and comments received on post written by @ryokuhi. Thanks for comments provided by @Benachi and @joedolson.

Major Goal Proposals

We have two proposals as major goals for the next release:

  1. Revise a requirement for accessibility-ready themes. @joedolson will work with @benachi to determine what changes are needed and author appropriately.
  2. Contribute more heavily to the accessibility 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/. More proactive monitoring is needed with issues and testing.
  3. Changing the issue and/or Pull Requests template asking explicitly for steps to follow to reproduce is crucial to reduce testing time and improving feedback.
  4. Dedicating some time during bug-scrubs to Gutenberg issues might be a starting point to reduce accessibility issues.
  5. Reviewing how accessibility labels are used in 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/ and how we’re getting notified in this channel might also be beneficial.

Open Floor

A lively discussion closed with these comments:

  • In terms of prioritization, the WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor needs to be used to build a site whereas Full Site Editing experience is not (unless they use themes that support it). As such, it is the reasoning to priority the Widget Editor; and
  • If anyone is interested in what the #training team is planning for 2022, comments are still open

Suggested Priorities during Discussion

  1. Get Keyboard use for 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. Widget environment (currently not an option);
  2. Try to make Columns Block accessible via dialog which should help in several areas including the Full Site Editor; and
  3. Gutenberg accessibility should be a priority. As described in this ticket by @alexstine, a group of patches around problems don’t work when new functionality comes along. The Team needs to determine what attention can be put on Gutenberg, being more effective, and invest the appropriate time testing and commenting on issues.

Additional Perspective Requested

What are the challenges faced in seeing accessibility issues through on block editor, full site editing, etc (for those new to the Team)? In response, the Team hasn’t had a Lead on Gutenberg Development since the departure of Andrea Fercia with only one person actively working in from Accessibility (@alexstine). It is a a shortage of availability from our Team, coupled with the very high levels of complexity required to work on Gutenberg with a level of comfort with ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/..
Some of the challenges are:

  • Learning React is a low priority environment or isn’t often a requirement for projects professionally for many; and
  • There’s also a correlation with no WordPress Accessibility Contributor Sponsorships for development;

Other Discussion Talking Points

  • Is there agreement on what topics are a top priority for the Team that can be brought to a wider group for implementation assistance?
  • Are any of these things we can help push to the finish line or find more eyes for (mention of seven current issues in progress)?
  • Get more GitHub notifications coming in to Slack ensuring that any items labeled Accessibility lands there;
  • Being aware of issues or having the time to review while balancing too many (could become spammy if too much). Every UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it./UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. change has the potential to upset the accessibility of the experience regardless of tags. This is one of the biggest issues with trying to keep current with Gutenberg accessibility. We as a Team need to catch more than we currently do. With a very small team, can we set up a monitoring rotation?;
  • Pros and cons of notifications, applying milestones (possibly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.), use of labels, tracking issues and pull requests reviews discussed at length;
  • When issues are resolved, accessibility wins should be pushed out to a larger audience to garner attention;
  • Although an Accessibility Review is already required, our Team needs to have better management of the process and a bigger team is needed. Often time is wasted trying to figure out what needs to be tested and how;
  • Pull requests should include testing steps. An example of this issue can be found at https://github.com/WordPress/gutenberg/pull/38012;
  • @alexstine provided a list of Accessibility GitHub labels noting that all the sub-labels were created following the WP Campus audit;
  • Based on extensive discussions around creating new issues, issue sweeping ridealongs, custom fields, labels on pull requests @alexstine opened a proposal to modify the pull request template to include a subheading for specific testing instructions; and
  • Further clarification on ridealong suggestion by Destiny, Hauwa Abashiya suggested doing something similar to a First-time Contributor session to onboard new Team members to the nuances of Accessibility and the issues discussed today. She’d be happy to work on a lesson plan to put on Learn WordPress for new contributors. She’ll follow up with @joedolson.

#meeting-notes

Accessibility Team Meeting Notes: January 7, 2022

These are the notes for the Make 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 meeting, that occurred Friday, January 7, 17:00 UTC. You can read the entire transcript on our Slack channel and view the Meeting Agenda here. The meeting begins on time after the conclusion of the bug scrub, a welcome to new attendees with introductions, and rules for a family-friendly meeting.

Goals for WordPress 6.0 release

  • @ryokuhi suggested that with WordPress 5.9 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 released this past Tuesday and WordPress trunk is now the 6.0 Alpha, it’s probably a good time to begin defining goals for the next release; and
  • With WordPress 5.6, 5.7 and 5.8, we pubished post on the Make Accessibility Team site, asking for public feedback on possible major team goals for the next release. For the 5.9 release, we didn’t do this; after some discussion, now is a good time to publish this; and
  • This post, Accessibility Team’s Goals for WordPress 6.0 and Beyond, is a good starting point for new contributors.

Updates from Working Groups

  • Media Team @joedolson reported that this team is setting goals for 6.0 with a major focus being the redesign of the Media Library’s Image Editor.

Update from January 7 Bug Scrub

  • There are no open accessibility issues for 5.9, but we’re keeping an eye on the About Page;
  • There’s an open ticket milestoned for 5.9.1, which is either a 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/ or a Twenty Twenty-Two theme issue;
  • There are 9 tickets in the awaiting review queue; and
  • There are already 17 tickets milestoned for 6.0.

Open Floor

@sabernhardt requested at least one more reviewer for a developer note about theme-focused tickets (such as the toolbar scroll padding, the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. image alt attribute, and the RSS widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. icon). Please reach out directly if interested. @ryokuhi closed the meeting with a quick reminder that next bug-scrub will be on Friday, January 14th at 16:00 UTC and the next Team Meeting will be on Friday, January 21st at 17:00 UTC.

#meeting-notes

Accessibility Team Meeting Notes: December 17, 2021

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.

Plans for meetings on January

After moving from having weekly meetings to having meetings every other week, it would be good for people willing to attend meetings to know in advance when they will be.

@joedolson suggested about moving to two meetings per month, so that it would be easier to add meetings in the meeting calendar. As this doesn’t seem to be too big of a change from having a meeting every two weeks, the team agreed to hold meetings on the first and third Friday of every month at 17:00 UTC. Bug-scrubs will continue to be held weekly on Friday at 16:00 UTC.

Updates from working groups

Only groups that provided updates are shown below.

Documentation

@azhiyadev reported that there aren’t significant updates: she’s still going through the handbook and updating it. She’s also keeping an eye on the discussion for the WordPress 5.9 About page.

General

@ryokuhi reported that the 5.9 milestone on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. is clear from tickets and that the awaiting review queue is almost clear, with only 7 tickets left.
13 tickets have already been milestoned for WordPress 6.0, no one with the early keyword.

Media

@joedolson reported that there are no significant updates from the media working group, which is mostly getting started in planning for WordPress 6.0 and monitoring for anything that needs to be fixed.

MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.

@alexstine reported that he had opened a ticket on Meta Trac about using the image caption as alternative text for single images in the Photo Directory. @joedolson suggested to make clear that the picture description will also be used as Alt text or to create a new ticket to add a separate alt attribute when uploading the image.

Open floor

@ryokuhi quickly reminded that there won’t be either bug-scrub or meeting on both December 24, 2021 and December 31, 2021.

#meeting-notes