Accessibility Team Meeting Agenda: July 1, 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, July 1, 2022, 16:00 UTC.

  • 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. discussion.
  • 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, July 1, 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).

#agenda

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 Agenda: June 17, 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, June 17, 2022, 16:00 UTC.

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, June 17, 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).

#agenda

X-post: Announcement: Incident Response Training

X-comment from +make.wordpress.org/updates: Comment on Announcement: Incident Response Training

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 Agenda: May 20, 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, May 20, 2022, 16:00 UTC.

  • 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, should the Accessibility Team meeting be rescheduled on June 3rd or canceled? If canceled, the next meeting will not be until June 17th.
  • 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, May 20, 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).

#agenda

Accessibility Team Meeting Agenda: May 6, 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, May 6, 2022, 16:00 UTC.

  • Request for feedback on the WordPress Accessibility Statement.
  • Teams activities during Wordcamp Europe.
  • 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, May 6, 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).

#agenda

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

X-post: WordPress 6.0 Accessibility Improvements

X-comment from +make.wordpress.org/core: Comment on WordPress 6.0 Accessibility Improvements

Accessibility Team Meeting Agenda: April 15, 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, April 15, 2022, 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 be held on Friday, April 15, 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).

#agenda