Accessibility Team Meeting Notes: April 21, 2023

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

Updates from the working groups

Only groups that provided updates are shown below.

## Gutenberg Team Here’s a status update from @annezazu and 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/ team:

  • Mainly want to raise attention to the latest call for testing: https://make.wordpress.org/test/2023/04/17/fse-program-testing-call-21-front-page-fun/ combined with the latest update to the overall phase 2 issues: https://github.com/WordPress/gutenberg/issues/33094

### Media and Meta @joedolson provided the following updates on Media and 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. for discussion:

  • For media: the regression in media custom fields is fixed in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and just awaiting merging to 6.2.1; not much else has changed this week.
  • For meta: several changes made to alt text input, labeling, and public visibility for the photo library which should really improve that. For general: I’ve slated quite a few tickets from the distant past for 6.3 in the last couple weeks; if anybody wants to work on patches for those, or otherwise dive in, that would obviously be appreciated!

### Themes @poena generously provided the following update from the THEMES team: Themes: There is a proposal for reorginizing the theme developers handbook. There is a general request for feedback on the propsed outline. The feedback period for the outline ends on April 28, 2023. https://make.wordpress.org/themes/2023/04/04/theme-handbook-overhaul-proposal/ Kafleg, one of the team reps has also asked for help with some accessibility-ready theme reviews. Anyone interested can message him on slack or use the #themereview 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.

### Open floor

@joesimpsonjr asked if we’re all set as a team for 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’s 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/. @joedolson answered: We’re certainly set; we haven’t decided who is going to take responsibility for leading the table; I wanted to find out if any more people were likely to be there, first. It’s nice to be able to partner to run the table. I think that as long as Stefano and I are there, we’ll definitely have the table handled; that’s not a worry.

@joedolson made the following updates for consideration for the following teams/topics: As a general addition to the agenda, we should talk about WCEU and contributor day; I’ve written responses to the Make Team interview questions, which I’d appreciate feedback on. https://docs.google.com/document/d/19aC3kJF2PF0oSwUYub4K4taxvKVX3fhOHyST5EfF5A0/edit#heading=h.du9x0ee9zyb

@joedolson announced WP Accessibility Day save the date is out; it’ll be September 27th-28th.

@desrosj shared a crosspost on Cultivating More Effective Contributing on Contributor Days. Take a look when you have a moment…

@chaion07 shared this about WordPress 6.2 at https://make.wordpress.org/design/2023/03/30/why-jazz/

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility, #agenda, #meeting-notes

Accessibility Team Meeting Notes: April 7, 2023

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

## Updates from the working groups

Only groups that provided updates are shown below.

[### General Team[(https://wordpress.slack.com/archives/C02RP4X03/p1680883795044319)

  • Reviewed 11 tickets 11 tickets in today’s bugscrub, slated several for 6.3 and closed two.

### Gutenberg Team

  • @annezazu reported on the following for the Gutenberg Team: I want to note this new layout type called “grid”: https://github.com/WordPress/gutenberg/pull/49018 It would be rad to get some reviews here! Finally, various modals are becoming more common and I’d love to get some early a11y thought around unifying the various modals here: https://github.com/WordPress/gutenberg/issues/39308 #49018 Try adding a grid layout type WordPress/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/ | Mar 12th | Added by 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/ #39308 Align pattern / template part modal dimensions, and add view options WordPress/gutenberg | Mar 9th, 2022 | Added by GitHub

### Media Team @joedolson provided the following updates on Media and 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. for discussion:

  • There’s a regression in media modal custom fields caused by some accessibility changes, so that’s a priority right now, targeted for 6.2.1. The change that prevented a loss of focus also caused custom fields not to display on newly uploaded items. So we’re hoping not to have to revert that, and find an alternative solution. Otherwise, just scoping out what will fit into the 6.3 plans. See: https://core.trac.wordpress.org/ticket/58051

### Meta Team Joe also provided this for the Meta Team: There’s a lot going on in Meta right now, but probably the biggest thing we should be watching for is the possible switch from Slack to Matrix for a core chat service. It’s still very much in exploration stages, but it could mean significant changes in work flow. Mozilla switched to Matrix in 2020; here’s some info from Marco Zehe on using it with a screen reader: https://www.marcozehe.de/how-to-use-element-and-matrix-with-a-screen-reader/ Otherwise, there’s the ongoing redesign efforts and various new systems being spun up. It’s a lot to track…

Open floor

@joesimpsonjr mentioned making submissions for the WordPress Community Summit and announced @alexstine is helping organize 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 2023.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility, #agenda, #meeting-notes

Accessibility Team Meeting Agenda: April 7, 2023

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, April 7, 2023, 16:00 UTC.

  • 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 also be held on Friday, April 7, 2023, 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, #agenda, #meeting-notes

Accessibility Team Meeting Notes: January 20, 2023

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

@ryokuhi updated the group on a discussion in the channel about links opening in a new tab and it was pointed out that there isn’t anything about it in the Accessibility Handbook. @joedolson clarified provided a link to this topic in the Docs guide although without the accessibility reasons and mention by @sabernhardt it’s also in the Accessibility Handbook. Brings up the need for cross-referencing. Anyone interested, please make a Pull Request to the Doc Style Guide to add the cross-reference.

General

@ryokuhi shared that the General Team is:

  • currently focusing on the Awaiting Review queue and on tickets milestoned for 6.2;
  • at the moment, all the 12 tickets Awaiting Review have been reviewed at least once;
  • there are 15 tickets milestoned for 6.2, with 14 of them already reviewed in the last two bug scrubs;
  • following discussion on #56228 last week, we need a few eyes on the related Gutenberg Issue 42373, so that we set the time frame to milestone the related coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue; and
  • 6 more tickets were already committed for the next release.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/

Before the meeting, @annezazu reported this for the Gutenberg Team and welcomes comment:

  • Latest update for phase 2 items: https://github.com/WordPress/gutenberg/issues/33094#issuecomment-1384570000
  • Accessibility review for the offcanvas editor issue: https://github.com/WordPress/gutenberg/issues/46939
  • A run down of items for the training/docs/polyglot crew that might be helpful: https://make.wordpress.org/training/2023/01/13/information-sources-for-wordpress-6-2/#comment-3629

Media

@joedolson shared a post on media management that we may want to discuss during our next Media Team meeting.

Open floor

Notes during Open Floor:

  • Our Call for Team Rep nomination is still open at https://make.wordpress.org/accessibility/2022/12/02/call-for-team-rep-nomination-december-2022/. We’d love for someone to step forward to support this team’s efforts; and
  • @joedolson reiterated the need for testing on the FSE experience; anybody can do it: just spend time with the environment and see what accessibility issues you spot.

#accessibility, #meeting-notes

Accessibility Team Meeting Notes: December 16, 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 a few statistics for TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets collected at the time of the meeting.

  • There were 10 tickets in the Awaiting Review queue, all of them reviewed at least once. One of them is in the process of being moved to 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..
  • There were 16 (+ 1) tickets already milestoned for the next major release (6.2), with no timeline for the release set yet.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/

Before the meeting, @annezazu reported that the Pull Request to introduce browse mode broke the ARIA landmark structure: this is being addressed in issue 46509. She also reported that the 19th call for testing for the Full Site Editing Outreach Program has been released and, as always, testing with keyboards and screen readers is really appreciated.

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 a request for feedback about the refresh of the showcase site, which was published in the #accessibility channel the week before the meeting.

Open floor

@joedolson and @alh0319 shared about an offer from Pagely to pay for some WordPress user testing. Full discussion was very long and can be found in the #accessibility channel. @alh0319 is working on a list of instructions for testers, which will be shared for feedback here as soon as they are ready.

@afercia made a proposal to establish Accessibility Office hours. The proposal was met with wide support, and @afercia is free to work out the details.

Hostinger has offered team contributors attending 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. Asia 2023 an invitation for a Contributor Day dinner. If anyone is attending and is willing to volunteer as a representative for the Accessibility Table, please let the team know in the Slack channel.

For the next two weeks, the Team will check on Wednesday whether someone is available to facilitate the bug scrub.

@ryokuhi is stepping down from his role 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.. The Call for Team Reps is still open: if you want to candidate yourself or if you have a name for a possible Team Rep, write it in the comments to that post.

#meeting-notes

Accessibility Team Meeting Notes: December 2, 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 a few statistics for TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets collected at the time of the meeting.

  • There were 13 tickets in the Awaiting Review queue, all of them reviewed at least once.
  • There were 16 tickets already milestoned 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. (6.2), with no timeline for the release set yet.

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 asked to have a look to the Pull Request to move the Post or Page title to the top toolbar and to the related issue, which he isn’t convinced about.

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.

Before the meeting, @alexstine asked to watch Meta ticket 6608.

Open floor

@bph asked for accessibility feedback on the usage of the title field of the Code 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. (which is added by 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) in the WordPress Developer Blog. Full discussion on the topic can be found on Slack, and a summary of the discussion is available on @bph‘s personal blog. The team suggested changes to the plugin itself, to improve its accessibility. When the new implementation of the block is ready, the topic will be discussed again during a meeting. If you want to add something to the conversation, feel free to drop a line in the #core-dev-blog channel on Slack.

@joesimpsonjr, who is part of the Lead Team for 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 2023 and the Community Summit, invited Make WordPress Accessible Team contributors to share topics for discussion at the Community summit, an event that will provide a valuable opportunity to hold in-person discussions on important topics across contributor teams and community-wide. To suggest possible topics, you can use the form on the Community Summit website.

As already announced, @ryokuhi is stepping down from his role 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.. As such, a Call for Team Reps was opened: if you want to candidate yourself or if you have a name for a possible Team Rep, write it in the comments to that post.

Update 9 December 2022: A link to the summary of the discussion about the Code Block from @bph‘s blog was added.

#meeting-notes

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