Accessibility Team Meeting Agenda: April 23, 2021

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 23, 2021, 16:00 UTC.

  • Proposal to improve usage of keywords and labels on accessibility tickets, issues and pull requests
  • Updates from working groups
  • 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 23, 2021, 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 16, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Planning bug-scrubs and meetings for WordPress 5.8 release

Following updates to the 5.8 release cycle timeline and to the 5.8 pre-planning post, the next WordPress release cycle is now more defined.

@ryokuhi introduced the discussion, highlighting the main points.

  • Following the first round of testing on Full Site Editing, the plan is to merge some features in the next release.
  • In earlier releases, work on existing bugs could be done also during 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., but in the latest releases Beta was intended exclusively to fix bugs introduced during each release cycle. To allow specific time to bug squashing, a new “Feature freeze” deadline is introduced two weeks before Beta 1: after Feature freeze, only bug fixing is allowed.
  • At the time of the meeting, without taking in consideration GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and Full Site Editing, there were 17 tickets in the 5.8 milestone: 1 ticket is marked as early , 1 ticket is a feature request , 7 tickets are enhancements  and 3 don’t have an owner (but the team has to address only 2 of them).
  • As the difference between enhancements and bugs is now significant again, the team needs to decide how to prioritize work, given that until now bug-scrubs focused mainly on tickets in the Awaiting Review queue and that new features or enhancements should be ready by May 25.

A discussion followed about how to prioritize work so that all tickets marked for 5.8 will make it in the release.

The main decision was to have to two checkpoints on April 30 (right after the second Go / No Go test on Full Site Editing) and on May 21, to better keep track of what areas need more help and to decide if extra meetings or bug-scrubs are needed.

Also, in the next weeks bug-scrubs will gradually move from focusing on Awaiting Review, to Feature Requests and Enhancements, and then to Bugs and Tasks.

Updates from working groups

Only groups which had updates shared them.

Gutenberg

@annezazu shared a few updates about Full Site Editing and Gutenberg in general.

  • The call for testing on the Query Block was shipped with feedback due by May 5: as 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. will almost certainly be included in 5.8, contributors are invited to test for accessibility concerns as soon as possible.
  • The post about the first Go / No Go test helps to understand the major areas of focus for Full Site Editing in 5.8, so it can be an interesting reading. According to the post, the main areas in need of tests are template editing and major blocks like the Navigation Block and the Query Block.
  • A Pull Request to add block titles to the block switcher label will be included in version 10.5 of 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.
  • The Pull Request about focusing the save button when the save panel opens might need some extra feedback.

Documentation

@Jill Mugge reported that the working group is adding more accessible patterns and antipatterns. During the meeting, she suggested that creating a template for documentation could be helpful to stay consistent and improve accessibility, so she volunteered to do it.

Media

@joedolson reported that he did some work and that he should make more progress by next week.

Open floor

A clarification was given about why threads should be avoided on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#meeting-notes

Accessibility Team Meeting Agenda: April 16, 2021

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

  • Planning additional bug scrubs and meetings for WordPress 5.8 release.
  • Updates from working groups
  • 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 16, 2021, 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 9, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Quarterly community updates

Every three months, all Make WordPress teams are asked to update the community at large about what they are doing, so that everyone is aware of what’s going on. All updates are collected in a post published in a specific section of the WordPress website.

Previously, discussion about what to write in the post was left to the team reps, but @alexstine and @ryokuhi agreed that bringing it in the wild would be good for the team.

During the meeting, the team discussed about the challenges and big wins for the team in the preceding three months. @ryokuhi offered to integrate the points brought up during the meeting with the team goals for the next release and to write the report. Updates for the first quarter are now available on the Make website.

Updates from working groups

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 and @poena shared a few updates regarding Gutenberg and Full Site Editing

Full Site Editing updates

Gutenberg highlights

Documentation

@Jill Mugge has been working on accessible patterns and antipatterns.

Media

@joedolson reported that everybody on the media team has been very busy in the last month, and nobody has done work on any open tickets yet.

Design

@sarahricker had been away for a few weeks and no one else was able to report.

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 reported that there were no updates regarding meta.

Themes

@poena left a note after the meeting.

  • There was no progress regarding the workshop for reviewing accessibility-ready themes
  • There was no progress regarding adding more end user information about what accessibility-ready means
  • The list of approved themes waiting for accessibility-ready review is empty, but the Michelle live theme is waiting for it

General

Bug-scrubs are still focused on clearing the Awaiting Review queue as much as possible. As soon as the 5.8 release date is confirmed, focus will move to tickets in the 5.8 milestone (currently, there are 15 of them).

Open floor

@paaljoachim asked for general and accessibility feedback about two Learn WordPress tutorials he wrote. This lead to opening an issue to fix the contrast problem in the Code Block CSS in the Learn WordPress repository.

#meeting-notes

Accessibility Team Meeting Agenda: April 9, 2021

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 9, 2021, 16:00 UTC.

  • Quarterly community updates
  • Updates from working groups
  • 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 9, 2021, 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 2, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Update from working groups

  • Design: no update.
  • Docs and Patterns: added some notes around tables.
  • General: no update.
  • 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/: no update.
  • Media: no update.
  • 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.: no update.
  • Themes: no update.

Feedback requested

The following items need feedback.

Open floor

Add testing instructions to Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ pull request template that way instructions are always provided on how to test a change.

#meeting-notes

Accessibility Team Meeting Agenda: April 2, 2021

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, 2 April 2021, 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, 2 April 2021, 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: March 26, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Update from working groups

  • Design: no update.
  • Docs and Patterns: @Jill Mugge has done some work on the Pattern Library, specifically the Alternative text pattern as well as fleshing out more topics under Content patterns. @azhiyadev has started to work on the accessibility handbook.
  • General: no update.
  • 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/: A few updates
  • Media: lots of planned work but no progress at this point.
  • 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.: no update.
  • Themes: no update.

Open floor

  • Next week @azhiyadev will run the accessibility team meeting and @alexstine will cover the bug scrub.
  • Even though more clocks are changing due to daylight savings time, bug scrub and meeting times will stay the same.

#meeting-notes

Accessibility Team Meeting Agenda: March 26, 2021

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, March 26, 2021 at 16:00 UTC.

  • Updates from working groups
  • 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, March 26, 2021, at 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: March 19, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Review of accessibility team’s goals for WordPress 5.8

Following the pubblication of the call foor WordPress 5.8 Accessibility Team’s goals and the decision to postpone the discussion by two weeks, a general discussion took place about some of the proposed goals for next release.

WordPress 5.8 will be out in July 2021, but the exact date hasn’t been set yet.

Here are the main takeaways of the discussion.

  • 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/ development will be followed more in detail. @ryokuhi volunteered to review the page about Gutenberg testing to update it and create a routine to test if users relying on assistive technologies (for example, using only keyboard navigation and/or screen readers) would be able to perform standard tasks in 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.
  • Also, Full Site Editing (which will land in the next release) will be a priority. @critterverse agreed to try to keep up with the FSE outreach experiment by testing using assistive technologies, making sure there’s some accessibility coverage and reporting to the team with the results.
  • Work on documentation will be central even during the next release. @Hauwa Abashiya reported about a discussion regarding the possible audience for the accessibility handbook, which includes both creators (designers and developers looking for resources about accessibility) and contributors (who want to contribute to the project itself). As such, the documentation working group will focus around:
    • the about page (what the team does, the different working groups)
    • the Getting Started or Get Involved chapter (how the team works, onboarding, ways you can contribute, etc.)
    • resources for creators (tools, pattern library, etc.)

It’ll be up to each working group to keep moving towards these (and other) goals during the release cycle, so all contributors are invited to join a working group and become a representative for a working group, in case there isn’t one.

Open floor

@Jill Mugge friendly reminded all WordPress contributors to always add the alternative text to images in posts.

#meeting-notes