Accessibility Team Meeting Notes: October 19, 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 the meeting’s agenda here.

Updates from the working groups

Only groups that provided updates are shown below.

General

@ryokuhi reported that there are no tickets in need of special input from the team. During bug scrubs, the team is focusing on tickets milestoned for the next incumbent releases (6.0.4, 6.1, and 6.1.1) and on tickets Awaiting Review, to keep the queue under control. There are already 11 tickets milestoned for 6.2, which the team will start reviewing in the next few weeks.

By the time WordPress 6.1 will be released, 30 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets with the accessibility focus will have been fixed. @annezazu summarized in a post on the Make Core blog all accessibility improvements in WordPress 6.1.

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/

@annezazu shared for awareness a Pull Request to introduce a Browse Mode in the site editor.

@alexstine asked for some testing and feedback on the Pull Request to modify the shortcut which focuses the list view and on the Pull Request to improve region navigation. These are related to the Pull request to imporve regions and shortcuts in the editor.

Media

@joedolson slated two tickets from the WP Campus Gutenberg report for WordPress 6.2: one is about insufficient form semantics and the other is about insufficient labelling and inappropriate nesting of form controls. These tickets, together with the one about text inadvertently rendered by assistive technologies, will be all tackled as a group.

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.

@joedolson shared that HelpHub, the part of the 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 which includes end-user documentation, is undergoing a redesign. It’s going to follow the same patterns used for other redesign, but it should get some accessibility attention in the near future. For more details, there’s a post about HelpHub redesign in the Make Documentation blog.

Open floor

@joedolson reminded about WordPress Accessibility Day, happening on November 2-3, 2022. Registration is open (at the time of the meeting, more than 500 people had already done it), sharing on social media is appreciated (the website is wpaccessibility.day), and volunteers are still needed, especially for the post-event video-editing work (please reach out to Isla Waite in the WordPress Accessibility Day Slack instance).

If you’ve been a (more or less) regular contributor to the Accessibility Team in the past year, please send a Direct Message to @joedolson, who will add the appropriate Accessibility Team member or contributor badge to your WordPress profile.

@joesimpsonjr shared the page with the newly added venue accessibility checklist page in 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. Organizer Handbook, to tackle a few accessibility issues that impacted on the experience of a few participants during WordCamp US 2022.

#meeting-notes

Accessibility Team Meeting Notes: August 19, 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 the meeting’s agenda here.

Updates from the working groups

Only groups that provided updates are shown below.

Documentation

@azhiyadev reported that she will check out Sa11y, an accessibility tool for content creators, and that she will report back about it.

General

@ryokuhi reported that the Team is monitoring tickets in the Awaiting Review queue (at the time of the meeting, there were 12 of them, like two weeks before) and tickets milestoned for the 6.1 release (at the time of the meeting, 16 of them were still open and 12 of them were closed). Among the tickets closed in the two previous weeks, there is also the ticket to add functions for required fields indicator and message

As the 6.2 milestone has already been opened, the Team is now able to re-milestone tickets that won’t make it for 6.1 without need to move them to Future Release.

Media

@joedolson reported that he only removed the ticket about redesigning the admin Image Editor from the 6.1 milestone, due to lack of time to work on it.

Themes

@ryokuhi reminded the Team that on Friday, September 2nd, part of the meeting will be dedicated to discuss the use of the accessibility-ready tag for 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.-based themes. He’ll publish the post about it: @joedolson volunteered to x-post it to both the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the Themes Teams.

Open floor

@joesimpsonjr asked if someone from the team is planning to join the Accessibility Table durign 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/. of 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, apart from him and @joedolson.

Also, @joesimpsonjr asked how to handle the new Team Reps nomination process, where nobody nominated or accepted the nomination. After a short discussion, it was simply decided to consider the current nomination process "closed", to unpin the post from the blog and to wait until November to open a new Call for Team Reps.

@ryokuhi reminded that he won’t be able to attend the bug scrub on 26 August 2022, but that @chaion07 had volunteered to facilitate it.

#meeting-notes

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

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

@ryokuhi posted a Call for Team Rep Nominations on 15 July 2022, asking team contributors if they were interested in taking the role he has held for a more than two years.

@sabernhardt was nominated by @joedolson and @ryokuhi, but he had already expressed his doubts at the time of the nomination.

The call stays open for now until further notice.

Accessibility of pattern previews in theme pages

In a message on the channel, @poena had asked to discuss the new feature adding pattern previews to individual theme pages, which had an issue that prevented navigating through the pattern list when using keyboard only.

By the time of the meeting, the issue had been solved, but the new interface would still benefit for some extra accessibility testing: findings might be added as comments to the ticket on Meta Trac about adding pattern demos to themes and new bugs can be reported by creating new tickets on 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. @Ryokuhi reported that he was able to spot a couple bugs while quickly testing.

Updates from the working groups

Only groups that provided updates are shown below.

Design

@ryelle shared that the 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/ redesign is underway and that the current progress can be viewed on the staging site. Bespite being still in progress, accessibility feedback on the homepage and the download page is welcome and can be added to the repository of the wordpress.org block-based theme.

Documentation

@azhiyadev reported that a few minor changes were made last week. She invited everyone who spot anything that needs updating to let her know and that she’ll try to dedicate more time to the team, as far as daily job allows it.

General

@ryokuhi reported that the Team is keeping track of tickets in the Awaiting Review queue (at the time they were 12) and of tickets milestoned for the 6.1 release: at the moment, 17 of them are still open and 10 of them have already been 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/

In a message posted before the meeting, @get_dave asked for accessibility feedback on the Pull Request about adding custom labels to blocks in list view. @joedolson already gave a quick feedback, but such a feature could use some more feedback.

Themes

@poena completed a review of the accessibility of the Twenty Twenty-Two theme and added the findings as a comment to the ticket about adding the accessibility-ready label to the Twenty Twenty-Two theme. The only issue is that the aria-hidden attribute is missing from icons in the query pagination: such an issue has already been addressed in Gutenberg and will be included in the 6.1 release.

She also asked if the team wants to use the accessibility-ready tag for 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. themes at all: it was decided to rediscuss this issue during the meeting happening on September 2, 2022, inviting contributors to Gutenberg and to the Themes Team to attend to have a preliminary discussion about the topic. After that, discussion can continue through comments to a post published on the Accessibility Team blog or by bringing discussion to a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat.

Open floor

@joesimpsonjr reported that he submitted information about Table Leads for the Accessibility Table 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 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 Sunday, 11 September 2022: @joedolson and @joesimpsonjr will be present all day long, with @alexstine possibly joining for part of it and @ryokuhi available remotely through Slack. They will prepare a list of small potential tasks people can look at, covering a broad spectrum of knowledge bases and specialties, including docs, testing, coding, etc.

Congratulations to @joedolson and @alexstine for being accepted as speakers for WordCamp US!

@ryokuhi won’t be able to attend the bug scrub on 26 August 2022, but @chaion07 volunteered to facilitate it.

#meeting-notes

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