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

Accessibility Team Meeting Notes: December 3, 2021

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

Update from Working Groups

As usual, we had a round of updates from the various working groups inside our Accessibility team.

Design Team

Design Team news was shared by @shaunandrews, listing some tickets and issues on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and 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/ which might benefit from review from the team:

  • Ticket 54270 – About Page for 5.9 Release;
  • Ticket 54489 – Update the Dashboard Welcome Banner for 5.9;
  • Issue 37067 – Panel Color Gradient settings to use dropdowns; and
  • Issue 37075 – Load the template list in the site editor without page reloads.

@joedolson suggested that the priority should probably be the About Page for 5.9. Also, volunteers were requested to review these issues so that they’ll be handled. Joe volunteered for the Welcome screen update and possibly the About Page. @alexstine subscribed to the template selection issue to track its progress.

Documentation Team

@azhiyadev provided the update for the Documentation Team. During the week before the meeting, she had a further look at the handbook, checking for WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. versions referred to and updating broken links. She asked a couple questions.

  • Should the handbook be converted to using 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?
  • In terms of 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 recommendations, are there any concerns regarding plugins that haven’t been tested with the latest version of WordPress? An example of one that is recommended is WP Libre Forms (referred in the handbook and tested up to WordPress 4.8.17).

Regarding the use of the block editor for the handbook, @ryokuhi expressed an opinion that we should stick with the classic editor for the handbook, as 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/ is still difficult to use for people with disabilities (in case editing is needed by those using assistive technologies). @shaunandrews added that having more people use the block editor and report any accessibility issues is the best way to improve the experience.

Regarding recommended plugins, those that haven’t been tested at least with version 5.7 should be removed. Joe is really uncomfortable recommending anything that shows evidence of being abandoned in the repository. This section needs to be updated desperately.

Also, @azhiyadev asked if there were any recommendations for web forms plugins to be listed in the handbook. Contact Form 7 or Gravity Forms were suggested by @joedolson, but additional clarification was needed (regarding whether Gravity Forms’ WCAG 2.0 form field plugin is still needed). Finally, we should indicate that we have not conducted a full accessibility audit on these recommendations. 

General Team

At the moment there aren’t any accessibility tickets milestones for 5.9. For the news, 28 tickets milestoned for 5.9 will be included in the next release.

Media Team

This team has finished off quite a bit and is now planning for 6.0. Planning includes preparation for updating the search and filtering options in the Media Library.

Themes Team

@sabernhardt reported that Twenty Twenty-Two has an h1 related issue (Issue 233). @joedolson will comment on the issue and @ryokuhi stated we’ll probably need to discuss this issue again in the future to see if a review of the Accessibility-Ready guidelines is required.

Open Floor

There will only be a bug scrub on December 10th and our next team meeting will resume December 17th, our last gathering of 2021.

A reminder that WordPress Accessibility Day returns in 2022 and the first organizational meeting for this event kicks off December 16th. DM @joedolson for more details and an invitation.

#meeting-notes

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

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

Last week, it was decided that the nominations for team rep would stay open until this meeting due to lack of nominations. During the last week, @joedolson nominated @joesimpsonjr, who accepted the nomination. @alexstine and @ryokuhi offered to keep helping out as team reps for the next six months, when the nominations open again. For the time being, the Accessibility team will have three team reps to help share the role.

Possibility of switching to bi-weekly meetings

The team agreed to switch to bi-weekly meetings instead of weekly ones, which will be especially useful near critical release dates. On the weeks when a meeting is not held, there will be an asynchronous sharing, especially from working groups referents. The bug-scrubs will continue to happen weekly and the meeting times and days will stay the same.

Upcoming changes to meetings

Open floor

@joedolson and @alh0319 are starting to plan the WordPress Accessibility Day 2022. A few things will be done differently from the first event.

  • The event will be independently organized, without involvement of the WordPress Community Team.
  • Planning and coordinating will happen in the WordPress Accessibility Day 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/.. Anyone who wants to be involved in the planning can send a Direct Message to @joedolson on the Make WordPress Slack.

#meeting-notes

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

Given that WordPress 5.9 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 released on Tuesday, November 16, 2021, @ryokuhi suggested to skip the point about the updates from the working groups and to quickly go through the other points, in order to allow more time to go through the tickets milestoned for 5.9 which weren’t discussed during the bug-scrub that had started before the meeting.

Team Reps nominations

As no one nominated either themselves or someone else for the role, the team agreed to postpone the deadline for nominations by one week: the new deadline is November 19, 2021. You can find more information in the Call for Team Reps nominations post.

@joedolson suggested the possibility of moving to bi-weekly meetings, to reduce the burden on Team Reps. This proposal requires extra discussion and will be considered during one of the next weekly meetings, when the team will be less focused on the next release.

Open floor

No topic was raised during open floor.

#meeting-notes

Accessibility Team Meeting Notes: November 5, 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.

Updates from working groups

Only groups that provided updates are shown below.

General

Feature Freeze for WordPress 5.9 happens on Tuesday, November 9, 2021: enhancements and feature requests have to be committed before this deadline, but the team has been working a lot on them and there are only a few of them that might be punted.

There are 18 tickets marked as bugs and tasks currently milestoned for 5.9: 3 of them were reviewed during the bug-scrub before the meeting, the rest of them will be reviewed either asynchronously or during next bug-scurb, hopefully in time for 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 will happen on Tuesday, November 16, 2021.

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/

The GitHub issue about adding hover color options to the Button block probably won’t be included in WordPress 5.9.

Media

The media team is working on various minor fixes and enhancements.

Themes

The Twenty Twenty-Two issue about hover, active and focus styles for buttons is worth reviewing, given that these styles will not be handled natively in Gutenberg, at least not in WordPress 5.9.

Open floor

Reminder: beginning with the next meeting, the weekly meeting will start at 17:00 UTC, with the bug scrub starting at 16:00 UTC.

Don’t forget to nominate yourself or someone else as Accessibility 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. by adding a comment to the Call for Team Reps post.

Given the large amount of spamming pingbacks that appeared below the Call for Team Reps post, the team is considering the possibility to disable pingbacks on the Make WordPress Accessible website.

#meeting-notes

Accessibility Team Meeting Notes: October 22, 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.

Results from bug-scrub and meeting time change poll

The results are officially in. The new bug-scrub time will be 16:00 UTC and the meeting time will be 17:00 UTC. The first bug-scrub and meeting to be affected by this change will be Friday, November 12, 2021 16:00 UTC.

Nominations for new team reps

It is that time of year again when the Accessibility team is looking for new team reps. @alexstine is coming up on a year and @ryokuhi on sixteen months. Check out Team Rep Nominations post for some background.

This is the process that was followed before and that will be implemented again for the process.

  1. A call for Team Reps post was published: add a comment to this post to nominate yourself or someone you think is fit for the role.
  2. We’ll leave the post open for comments for a couple of weeks. During the next but one meeting, we’ll review nominations and, in case there are more than two candidates, we’ll organize a poll to select the next Team Reps.
  3. We’ll leave the poll open for one extra week, so that the new Team Reps will be chosen by November 19.

If you have any questions, please feel free to reach out @alexstine or @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 via DM or in the accessibility channel.

Accessibility improvements to the Media Library regarding infinite scroll

In response to a comment on infinite scroll by @priethor, @joedolson left some notes during the chat, which are reported below.

Navigating items with arrow keys, being dependent on relative visual location, are difficult for screen reader users to use. Arrow key navigation of a grid is spatial, and spatial relationships change based on viewport, so they lose pattern repeatability for screen reader users between devices. It’s easy to get lost, because there’s no real point of reference or order.
What I’d like to see in a new media library is to give list & grid views equal importance. Right now, the grid view is extremely dominant: there’s no list view available anywhere outside of the library, so using media is heavily dependent on navigating the grid.
The media library, as it stands, doesn’t offer a lot of flexibility in navigation, so all users are forced into the same interaction set. Media absolutely benefits from a visual navigation, since it is a predominantly visual medium; but since the people using media are not necessarily able to benefit from visual navigation, there needs to be a mode of navigation that is better suited to those needs.
For example, if what you’re looking for is a Word document in the current media grid, the visual layout is really not helpful at all; visual scanning provides minimal benefit.
Finding a way to make a fundamentally spatial/visual navigation usable for all is a limiting approach; it’s always going to be a fairly crappy experience for people who don’t benefit from spatial/visual information. While it’s beneficial to have keyboard navigation within a spatial grid, the accessibility problem is communicating meaningful information about current position within that grid to non-visual users. It’s better overall to have multiple navigation methods, so that users can take advantage of the mechanisms most suitable to the type of media they’re handling and their preferred method of locating media.
The crucial thing for accessibility is that there is an accessible way to accomplish every task. It is not necessary for every method of accomplishing that task to be equally accessible to all users.
With the addition of an effective alternative view, the ability to flex other options in the grid view increases significantly.
In summary:
The fundamental point is that trying to find a perfect solution to the grid navigation is solving the wrong problem.

As @priethor wasn’t able to attend the meeting, the topic will be considered again when he’ll be able to join for one of the next meetings or asynchronously.

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/: adding an announcement on formatting change for screen readers

@alexstine asked for feedback and some extra testing from screen reader users on the related pull request.

Open floor

Next week there won’t be an extra bug-scrub in view of the 5.9 release; maybe an extra bug-scrub will be held during the following week, but it’ll be decided during the next weekly meeting.

Given the large participation during the extra bug-scrub held last Wednesday, it was proposed to change the bug-scrub time once a month, but this will be reconsidered after the meeting time change.

#meeting-notes

Accessibility Team Meeting Notes: October 22, 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.

Updates from Working Groups

Only Working Groups that provided updates are shown below.

Design

@chaion07 highlighted these two proposals that might be worth looking in to.

General

  • Today, there was a brief pause on tickets milestoned for 5.9 due to the reviewing of the Awaiting Review queue. It may be worth having an extra bug scrub considering we’re quickly approaching the release deadlines. There will be an extra bug scrub on Wednesday, October 27, 2021 at 16:00 UTC.
  • Currently, there is also not an Accessibility Release Coordinator for 5.9. See the related Slack message here. Please message @audrasjb if you would like to volunteer or have further questions about the role. @alexstine offered to take this role if one other person would assist.

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/

  • The official WordPress 5.9 Feature Go / No Go post has been published. There are some Gutenberg items included that the team may be interested in testing.
  • The following 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/ issue needs testing and, if replicated, a patch. accessibility: impossible to add or edit a post’s title with Jaws for Windows screen reader activated

Media

  • @priethor left a comment regarding infinite scroll in the Media Library. Our current plan is to discuss this during next weeks Accessibility meeting.
  • @madtownlems is currently working on a 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 that may improve accessibility of existing images without Alt Text. The plugin is not yet publicly available, but we’ll let everyone know when it is ready for testing. @sabernhardt shared the following TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket, containing some background about reusing Alt Text: improve the user interface to ensure correct usage of the image alt text.

Themes

While there were no updates from the Themes group today, it is likely time to start allocating some focus to the new Twenty Twenty-Two theme. This Twenty Twenty-Two GitHub Issue is currently tracking accessibility.

Open floor

Just a reminder to vote on which meeting time will work best for you. The poll will remain open until Friday, October 29, 2021 16:30 UTC.

#meeting-notes

Accessibility Team Meeting Notes: October 15, 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.

Updates from Working Groups

Only Working Groups that provided updates are shown below.

General

Going through TRACTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets milestoned for 5.9 in the New Features and Enhancements categories. Will finish this off soon, probably by next week.

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/

Although there were no updates shared from the Gutenberg group today, this post on accessibility improvements in Gutenberg might be worth highlighting for anyone who hasn’t read it yet. This 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/ Pull Request could also use screen reader testing. List View: experiment with only rendering a fixed number of items

Media

@joedolson reported about progress redesigning the image editor and requests feedback on these tickets. View the comment here

Themes

While there were no updates from the Themes group today, it is likely time to start allocating some focus to the new Twenty Twenty-Two theme. This Twenty Twenty-Two GitHub Issue is currently tracking accessibility.

Open floor

Just a reminder to vote on which time zone will work best for you. This is the new time zone which will be used for Bug Scrubs and Meetings. Vote here The poll will remain open until Friday, October 29, 2021 16:30 UTC.

#meeting-notes