Accessibility Team Meeting Agenda: August 5, 2022

This is the proposed agenda for the weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Friday, August 5, 2022, 16:00 UTC.

  • Revisit: Are there candidates for the role of 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.?
  • @poena to discuss the accessibility of pattern previews included in theme pages;
  • Updates from working groups:
    • Design
    • Documentation
    • General
    • 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/
    • Media
    • 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.
    • Themes
  • Open floor

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

The Accessibility Team bug-scrub will be held on Friday, August 5, 2022, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

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

Team involvement at 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 2022 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/.

WordCamp US is happening in person in San Diego, California, with Contributor Day on Sunday, September 11th. The organizing team reached out to all the teams for Table Leads for the event and shared a post containing specific information.

@joedolson and @joesimpsonjr will be both attending. @alexstine will maybe spend a short time there, but not the entire day.

A short discussion followed about possible activities and issues that might arise.

Activities during Contributor Day revolve mainly around sharing accessibility information with contributors, and helping them understand what is needed to get started. @joedolson suggested focusing on mechanisms and learning, as this is more effective than fixing problems or resolving issues during the event.

Contributor Days are difficult to handle, because it’s hard to predict who will show up: both new and experienced contributors might attend, and they have completely different needs. Having more than one person to run things allow to have different processes for people with various levels of knowledge and skills.

If you’re interested in taking a role during WordCamp US Contributor Day, need more details, or want to propose a possible activity, reach out to @joesimpsonjr on Slack. A rough agenda will be discussed through direct messages with people involved or during next meeting.

Updates from the working groups

Only groups that provided updates are shown below.

General

@ryokuhi reported that since last meeting the Team has been focusing on the 21 tickets milestoned for 6.1. The last bug scrub was very productive, with at least a couple of tickets almost ready for commit.

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/

During the last bug scrub, the Team reviewed again the ticket about adding the accessibility-ready label to the Twenty Twenty-Two theme. Until there’s a mechanism to get a complete list of all blocks and variations for testing, it will be really difficult to close it. If such a list would be available, part of WordCamp US Contributor Day could maybe be dedicated to testing 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. output (also) using assistive technologies.

@alexstine has been working through a significant change to keyboard navigation in Gutenberg Pull Request 41645: it still has a few bugs, but would benefit from some testing.

Media

@joedolson has been short on time to work on media, and hopes to make significant progress next week. There wasn’t a lot of feedback on open issues, anyway.

Open floor

@ryokuhi reported that the Call for Team Reps had been written and reviewed, and it was published after the meeting.

@joesimpsonjr and @joedolson shared the Call for Speakers for WordPress Accessibility Day, inviting contributors to apply and share.

#meeting-notes

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

1. Accessibility Team Rep Discussion

@ryokuhi mentioned that he’s served as 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. over two years 9since June 2020) and he will be stepping away. What is the best approach to move forward? Currently a role shared with Joe and Alex, elections could be held now or later in September. Agreement that the elections should happen sooner than later, Stefano will remain until end of year if the role isn’t filled.

The normal process is to publish a post on the Accessibility Team’s blog and ask (or propose) contributors for the role and based on replies move foward. @joedolson nominated @sabernhardt during the discussion.

2. Updates for the working groups starting with General Team

@ryokuhi provided a status for General, sharing that the Proposed Schedule for WordPress 6.1 has been published. There are currently 20 tickets in the milestone, with 11 bug scrubs to take care of them, so we have plenty of time for that.

3. Documentaton Team

@joedolson proposed a change 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 handbook a few weeks ago, but there hasn’t been any movement on the issue. @Hauwa Abashiya will plan to view this week.

4. Media Team update

Joe Dolson is working on the image editor with hopes of releasing it in July.

#accessibility, #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 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 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: February 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, February 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 General Team@ryokuhi reported that all new tickets are being actively address as well as tickets milestoned for the next minor releases (5.9.1 and 5.9.2). The release date for the next WordPress 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. has been announced. The dates that interest us the most are:
  • Feature freeze on March, 29 (5 more bug-scrubs from now, with 10 tickets marked as enhancements and feature requests to be closed); and
  • 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 on April 12 (7 more bug-scrubs from now, with 15 tickets marked as bugs and blessed tasks to be closed).
  1. Report from Gutenberg Team — There has been testing (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. screen) with a few bugs found. @ryokuhi will comment on known issues and watch for new items as they are opened; and
  2. Report from Documentation Team — Hauwa stated that for for sections of the Team Handbook containing code blocks a review is needed. @joedolson will review when links are provided.

Open Floor

Our weekly meeting closed with these comments:

  • @estelaris is working on the redesign of the end-user documentation and wanted to follow up on an issue related to the hashtag used at the end of the headings. Comments After research he believes he has some good solutions but wanted to confirm with our team and hopes to post on Monday. Comments: Technical implementation is good and modeling on the WAI implementation would be fine. More comments promised if time permits; and
  • Discussion of a request for accessibility feedback on the 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/ navigation 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. by @getdave. His comment can be viewed on the weekly agenda. Kudos to @getdave for his approach on having this item considered — "let the Gutenberg contributors do their work, then when they are ready for feedback on specific topics."
  • @joedolson mentioned getting specific testing instructions is crucial mentioning @alexstine comment about block by block vs. overall systems testing. Without knowing the internal strutures of Gutenberg blocks, Joe’s practical approach is to test a block then leave it to others to figure out the best ways to resolve the issue. @ryokuhi believes the purpose of the issue is to have a single umbrella issue to keep track of all accessibility issues with the navigation block, referenced in the general issue to track progresses of the navigation blocks.
  • Reminder: some parts of the world will switch to Daylight Savings Time (DST) and we should consider revising our meeting times for next week’s meeting.

Accessibility Team’s goals for WordPress 6.0 and beyond

As the first 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. of WordPress 5.9 shipped on January 4, 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 is already gearing up for the next 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..

The 6.0 development cycle details and the potential release date are yet to be defined, pending a decision about the schedule for WordPress releases in 2022. Still, WordPress 6.0 Alpha began on January 4, and Trunk is now open for business; also, in case there will be four major releases in 2022, early planning will be essential to get things included in time for each release, especially if we want to tackle large projects.

Because of that, the Accessibility Team wants to revive the tradition started with WordPress 5.6 to collect ideas and ask for public feedback about possible team’s goals, which is why you’re invited to leave a comment below and propose which accessibility improvements you’d like to see shipped with WordPress 6.0.

The discussion to identify major team goals will be held during the next weekly meeting, happening on Friday, January 21, 2021 at 17:00 UTC in the #accessibility channel of the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

You’re more than invited to share your ideas, take part in the discussion and suggest what to prioritize. Just remember that, while the Accessibility Team is doing its best to make WordPress as accessible as possible, our team’s resources are limited and we’ll have to carefully decide what to focus on.
In case you aren’t aware, the Accessibility Team is organized into seven working groups, focusing respectively on Design, Documentation, Media, 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., General, 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/, and Themes. Such an internal organization has proven successful in keeping issues moving more quickly: as such, in the end, it’ll be up to each working group to decide what to work on and assess if a suggested goal can be completed by the 6.0 release or not.

If a certain goal isn’t selected for the 6.0 release, anyway, it might be reconsidered in the future and become a goal for one of the next WordPress major releases (maybe already in WordPress 6.1).

In general, trying to focus on goals that can be reached in a single release cycle is the best option to be sure that the work gets completed: if you think that solving a specific issue or adding a new feature may require work that spans over multiple releases, let us know and we’ll find together a solution to get this working.

If you have any questions, feel free to drop them in the comments below or in the #accessibility channel on Slack.

#6-0, #goals

Call for Team Rep Nominations

As announced during the last weekly meeting, all WordPress Teams have been requested to start the process to select the new Team Reps. Since I’ve been 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. for about 16 months now and @alexstine has been in the role for almost a year, this seems like the perfect time for us to step down, so that someone else can take up the role.

To learn more about the role, you can check the article about what it means to be a Team Rep. In summary,

Team Rep is a leadership role that is mostly administrative in nature; it is not a Lead role.
Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities.
Someone who is a leader in a team can lead whether they are doing the team rep job or not.

Traditionally, 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 has had two Team Reps, which is really useful because it allows them to share responsibilities, divide tasks and cover each other when needed.

If you would like to be considered for the role or know someone who would be a great fit, you have the opportunity to nominate yourself or others by adding a comment to this post. Remember that, if someone nominates you, but you don’t feel like accepting, you should feel more than free to say no: your nomination be considered only if you explicitly agree.

We’ll be reviewing nominations during the weekly meeting happening on Friday, November 12, 2021 at 17:00 UTC. Depending on the number of submissions, the eventual voting round will take place during the following week, with Team Reps being elected during the meeting happening on Friday, November 19, 2021 at 17:00 UTC.

If you have any questions about the Team Rep role or the nomination process, please feel free to reach out to @alexstine or me (@ryokuhi) in the comments or 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 with a Direct Message or in the accessibility channel. Both of us have already agreed to support the new Team Reps during the transition period.

Thanks to @alexstine, who peer reviewed this post before the publication.

November 12, 2021 update

As of today, no one volunteered or nominated someone else as a possible Team Rep. Because of that, during the weekly meeting, the team agreed to extend the deadline for nomitations by one extra week.

We’ll be reviewing again nominations during the weekly meeting happening on Friday, November 19, 2021 at 17:00 UTC.

#team-reps

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/

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