Accessibility Team Meeting Agenda: January 22, 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, January 22, 2021 at 16:00 UTC.

  • Status updates from the working groups and poll for groups that need assistance
  • Continuing discussion about 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/ issue regarding focusing blocks after adding them with the inserter
  • 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, January 22, 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: January 15, 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.

Discuss the Goals for WordPress 5.7

Collect updates/feedback from the different working groups.

  • Media: moving through older TRACTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets.
  • Docs and accessibility patterns: no updates to share. Require feedback on documenting accessibility patterns.
  • Start the ground work of phasing out the accessible view in the widgets screen: 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/ may be replacing the widgets screen, more to come soon.
  • Making sure there is a plan in place to have team to team communication to help with WordPress Learn: @alexstine will attend the meetings and help out the Learn team with cross-communication.
  • More Accessibility Ready tag reviewers for themes team: more frequent training around theme review guidelines. The possibility of pre-recording training sessions for independent learning.

Discuss the 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/ issue about “Avoid focusing blocks when inserting them into the canvas”

Discussion will continue in the GitHub Issue. @ryokuhi wrote a summary in the issue on what was discussed in the meeting.

Open floor

There was a super quick open floor, but nothing new was brought up.

#meeting-notes

Accessibility Team Meeting Agenda: January 15, 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, January 15, 2021 at 16:00 UTC.

  • Discuss the goals for WordPress 5.7. Check in with working groups for progress updates. Goals list available here.
  • Discuss 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/ 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/ issue: Avoid focusing blocks when inserting them into the canvas.
  • 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, January 15, 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: January 8, 2020

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 the working groups’ activities

During holiday season, there were no accessibility team’s meetings, so the main goal of the meeting was to get updates from the various working groups and identify areas that most need some extra help, to make good use of the time left before 5.7 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..

Documentation

@Hauwa Abashiya reported that last discussion happened before Christmas and that the group agreed to continue to work on accessibility patterns.

Media

@joedolson reported that some triage was done and that there are some plans, but given the holidays only little work was done. The working group will need some extra help before beta, especially from developers who know the media library (and there are only a few of them, unfortunately).

Themes

@poena left a note before the meeting to inform that the Themes Team moved forward all themes with the accessibility-ready tag under review.

@joedolson reported that the Accessibility Team and the Themes Team joined forces to update the accessibility-ready guidelines to improve clarity and include some new requirements added for WordPress 5.5. The draft about proposed updates to requirements for accessibility-ready themes is public and contributors are invited to leave their feedback.

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 reported about the first in a series of call for testing for the Full Site Editing outreach experiment. Feedback is due by Wednesday, January 13th, but the date can be extended if needed. More call for testing will follow, this one was mainly highlighted to remind team contributors about this opportunity.

@sarahricker asked the team to follow two Gutenberg issues that are considered must-haves for WordPress 5.7:

Contributors are also invited to have a look to the Accessibility audit project board.

Design

@sarahricker reported her plan to continue with joint office hours between accessibility and design teams.

@jameskoster asked for feedback about the desing of the issue about making the block navigator persistent and adding hover indication on the canvas before it moves to development.

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 suggested to open a ticket to improve the exposure of information about accessibility-ready themes.

General

The bug-scrub before the meeting was very productive: all tickets in the 5.7 milestone have an owner, so they are monitored by at least one team contributor.

Open floor

@Hauwa Abashiya asked if some team contributors could attend the meetings of the new Learn working group. Next meeting is on Thursday, January 20, 2021 at 15:00 UTC, after that meetings will be every first and third Thursday of the month at 19:00 UTC.

@sarahricker asked to include updates about the team goals for WordPress 5.7 in the next meeting agenda.

@alexstine asked for some extra testing on ticket #52073.

#meeting-notes

Accessibility Team Meeting Agenda: January 8, 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, January 7, 2021 at 16:00 UTC.

  • Review of the working groups’ activities during holiday season and of areas in need of extra help for next release.
  • 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, January 7, 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: December 18, 2020

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.

Main team goals for WordPress 5.7

A short while ago, the team published a post on the blog asking for suggestions on what to work on in WordPress 5.7. Accessibility Team’s goals for WordPress 5.7 and beyond Here is what the team has decided to focus on.

  • Media
  • Docs and accessibility patterns
  • Start the ground work of phasing out the accessible view in the widgets screen
  • Making sure there is a plan in place to have team to team communication to help with WordPress Learn
  • More Accessibility Ready tag reviewers for themes team

Discussion about teams activity during the holiday season

It was decided that teams and sub groups would operate asynchronously through the holiday season. An extra bug scrub was proposed if it ended up being needed.

Open floor

There was not enough time remaining for open floor.

#meeting-notes

X-post: FSE Program Testing Call #1: Template Editing

X-comment from +make.wordpress.org/test: Comment on FSE Program Testing Call #1: Template Editing

Accessibility Team Meeting Agenda: December 18, 2020

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, December 18, 2020 at 16:00 UTC.

  • Main team goals for WordPress 5.7
  • Discussion about teams activity during holiday season
  • 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, December 18, 2020, 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’s goals for WordPress 5.7 and beyond

After the release of WordPress 5.6 on December 8th, the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team is already at work to plan the next release.

The 5.7 development cycle hasn’t been defined yet, but a tentative release date was set for March, 9th 2021, a bit less than three months from now. This isn’t really a lot of time: after the release of the first 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., only bugs introduced during the relase cycle can be fixed, with no possibility to add new features or enhancements or to fix bugs introduced in WordPress 5.6 or before. Given that some contributors may slow down their activity during alpha because of the holiday season, it’s probably better not to delay further the discussion on possible targets.

Because of this, the Accessibility Team is going to discuss possible goals for the 5.7 release during the next weekly meeting, happening on Friday, December 18, 2020 at 16:00 UTC 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).

By that time, you are invited to suggest possible goals as a comment to this post, so that it can be included in the discussion.

Given the team decision to create working groups focusing on specific areas of interest, it’ll be up to each working group to set goals and choose targets for the release, but you’re more than invited to share your ideas, take part in the discussion and suggest what to prioritize.

If a certain goal won’t be selected for the 5.7 release, it can always be included in the list that will be created for the 5.8 release.

Four WordPress releases are planned in 2021 with shorter release cycles: if you think that solving a specific issue or adding a new feature may require work that spans over multiple releases, let us know so that we can try to coordinate and help to get the job done.

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

#5-7, #goals

Accessibility Team Meeting Notes: December 11, 2020

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 the team’s activities for 5.6 release

WordPress 5.6 is out since Tuesday, so the team reviewed the main accessibility achievements of the release.

  • 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 now supports adding captions and subtitles to videos
  • The new Twenty Twenty-One theme is not only accessibility-ready, but also addresses more specialized standards from WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 at level AAA
  • A feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. to add an accessibility statement has been worked on during the release
  • Documentation is being rewritten to better describe accessibility patterns and antipatterns

Also, the team was able to build bridges with other teams, component maintainers and focus areas: this was greatly valued both inside the team and from the outside, and cooperation will hopefully improve even more when the new organization of the team in working groups will come into effect.

Team members were in general satisfied with the achievements and are looking into reaching even greater results in the next release.

Planning of weekly meetings during holiday season

Given that December, 25th and January, 1st fall on Friday, no meeting will happen on these days. This means that the next but one meeting will be on January, 8th.

The 5.7 development cycle hasn’t been defined yet, but the release is currently planned for March 2021, so the alpha period will happen mostly during the holidays.

A first step to set and reach targets would be to collect ideas: whoever wants to make a suggestion is invited to add a comment to the self-contained post about accessibility goals for WordPress 5.7.

During next weekly meeting, suggested goals will be discussed, but in the end it will be up to each working group to decide what to focus on for the release, based on the number of contributors and their time availability.

During holiday season, each working group will organize on its own. If needed, extra meeting and/or bug scrubs can be organized, but contributors are always encouraged to work asynchronously and ask for help at any time in the channel.

More details will be worked out during next weekly meeting.

Open floor

@Hauwa Abashiya asked what would be the best way for the training team to reach out for help from the accessibility team regarding accessibility questions raised in the creation of the learn.wordpress.org platform.

Given that most of the work is done in the GitHub repository of the learn WordPress project, it was suggested to create a specific label, so that team members can quickly identify issues related to accessibility.

#meeting-notes