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

Documentation of 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/’s accessibility features

We continued the discussion about documenting the features present in Gutenberg that help make the editor more accessible and the best way to bring awareness to them.

We agreed that this documentation should be easy to find and not buried or hidden under a menu. Some of the features we think would make part of this documentation are:

  • Edit and select modes
  • 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. Navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. and block breadcrumbs
  • Top toolbar
  • Spotlight mode

We agreed to continue this discussion next meeting.

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

As @audrasjb steps down from being a team rep to focus more of this time on the Core team, the team is planning to launch new team rep nominations during the next team meeting. @nrqsnchz will continue to be team rep and the new person to fill JB’s place will share tasks and responsibilities with him.

Open floor

@afercia reminded everyone of the list of tickets that need help from the Editor and Media teams. @audrasjb will be reaching out to those teams.

Andrea also asked if there has been any progress or updates on the PR for addressing accessibility concerns of WritingFlow. There’s been consensus around creating a setting to turn this feature on and off and those involved are currently discussing how to call this setting in the PR.

#meeting-notes

Accessibility Team Meeting Notes: May 29, 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.

Prototype: move blocks between levels with keyboard

The team discussed this 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/ PR that explores adding the ability to move blocks in and out of nesting levels with keyboard only.

We agreed that is is a very welcoming and promising exploration. There was a particular interest in figuring out what would be the best way to communicate these position changes to screen readers.

Accessibility audit of the new auto-update feature for plugins and themes

We discussed the recently merged auto-updates feature for plugins and themes from an accessibility perspective. There was discussion about how links that act like buttons should be handled, clarity of announcements, hiding icons, and button labels that change.

@ryokuhi had the excellent idea of bringing some of these issues to next week’s WCEU 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/..

Please refer to the Slack discussion for a more detailed overview.

Documentation of Gutenberg’s accessibility features

We discussed how to better inform users of the various accessibility features that are present on 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. The idea of creating documentation and adding a link to it, such as “Accessibility Help” was well received.

We agreed to bring back this topic on next week’s meeting and look at all the different accessibility features and options that would be useful to have documented.

#meeting-notes

Accessibility Team meeting notes – May 22, 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.

Preparations for team facilitators for WCEU 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/.

Those of us who have signed up to help and facilitate during WCEU contributor day were made aware of the latest updates and requests from the organizing team.

Updates on 5.5 projects

@audrasjb updated the team on the progress of Alternate list views, which is ready and awaiting reviews.

@afercia also shared that the removal of infinite scrolling from the media grid is also ready and waiting and accessibility review.

If you can, please help review those tickets and leave your feedback.

@nrqsnchz shared a WIP mockup of a dark, high-contrast theme for wp-admin as part of the accessible color schemes the team is working on.

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/ issues

Edit mode: arrow up/down should not move to other blocks

The team continued the discussion on this Gutenberg PR that looks to improve navigation for screen reader users when in Edit mode.

We agreed that creating a setting or option that enables or disables WritingFlow would be a favorable path forward. There are still concerns about how this setting would be called and how obvious it could be. @alexstine left a summary of the team’s discussion on the initial issue.

Add screen reader only text format

The team also discussed this Gutenberg issue that proposes adding a text format option to mark text as screen-reader only.

The team agreed that this is a very interesting suggestion that could be beneficial in a variety of use cases. There is also concern about possible abuse or misuse of such feature, and the negative implications that it could have for accessibility.

@nickthegeek added a summary of our discussion to the issue.

#meeting-notes

Accessibility Team meeting notes – May 15, 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.

Sort any remaining tasks for WCEU 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/.

The team tackled the remaining tasks due for WCEU 2020 Contributor Day. We set May 28, 15:00 UTC, as the time to hold office hours in 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. @ryokuhi, @audrasjb, and @nrqsnchz volunteered to help.

Review of 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/ issues

The team reviewed and discussed two Gutenberg issues from an accessibility perspective.

The first issue was Improve “Visibility” and “Publish” labels in Post Settings, where a better, more accessible way for displaying these statuses is being explored.

We agreed that the last suggestion should be evaluated and followed up.

The second issue reviewed was Edit mode: arrow up/down should not move to other blocks. This is a PR that aims to change keyboard navigation on edit mode in order to avoid an unexpected switch between blocks that particularly affects users of assistive technologyAssistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the technology needed to accomplish such tasks. https://en.wikipedia.org/wiki/Assistive_technology.

We couldn’t cover a full discussion and analysis so we agreed to revisit this topic at the next meeting.

#meeting-notes

Accessibility Team meeting notes – May 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.

Announcing the first WordPress Accessibility Day!

The first ever WordPress Accessibility Day was just announced this week:

Starting at 18:00 UTC on October 2nd, 2020, the WordPress Accessibility Team will sponsor a 24-hour online event focused on WordPress and Accessibility. If you want to learn about the future of accessibility in WordPress, join us for 24 hours of mind-expanding online learning!

Speaker submissions will be opening soon, so keep an eye on wpaccessibilityday.org.

A big round of applause to all the folks who’ve been working hard on planning and putting together this event. Please spread the word!

Review 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/ PR

The team reviewed and discussed this Gutenberg PR that implements the roving tabindex pattern on 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. toolbar.

We agreed that this is a welcoming change but expressed concerns on how a change like this could be communicated to end-users.

Open floor

@afercia shared the work he’s been doing on #50105. Feedback and help testing the patch is needed.

#meeting-notes

Accessibility Team meeting notes – May 1, 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.

WCEU 2020 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/. tasks

In preparation for WCEU 2020 contributor day, the team continued discussing the tasks that need to be addressed before the event. Most of these tasks already have an owner and progress is being made.

5.5 work updates or requests for help/feedback

@ryelle, @joedolson and @nrqsnchz continued the discussion on the Accessible Color Schemes project. It was decided to start creating mockups for high and low contrast, and light and dark color schemes.

Open floor

@joedolson made the team aware of a request to present at WP Campus Online about the status of the Gutenberg accessibility audit performed last year.

#meeting-notes

Accessibility Team meeting notes – April 24, 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.

Progress report on 5.5 work

The team has been making progress towards our planned work for the 5.5 release:

@afercia noted that some of the 5.5 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets might need to be pushed to the Editor and Media teams and that we need to know who the release focus leads are for those teams so we can refer to them.

@ryelle created this Trac ticket to move forward the discussion around creating new color schemes. @ryelle, @joedolson, and @nrqsnchz agreed to continue the discussion after the meeting.

@audrasjb has a patch ready for the WP-Admin fly-out menu ticket and is working on a first draft for the Alternate List Tables work.

Anyone interested in getting involved on any of these projects is encouraged to reach out. Your help is needed.

WCEU2020 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/. team tasks

We continued discussing the tasks that need our attention for Contributor Day during WordCamp Europe 2020. We’ve set up a spreadsheet in order to keep track and review progress.

@ryokuhi, @joedolson, and @nrqsnchz have signed up to help facilitate during the day. We still need more folks to sign up in order to be able to more comfortably cover all the hours needed.

We also discussed how many working groups we expect to need and also be able to handle. We agreed that two working groups divided by level of experience contributing to WordPress would be a good plan.

Folks interested in helping on any of these tasks are welcome to chime in too!

Open floor

@ryokuhi reminded everyone that the WordPress Accessibility Day website will be going live next week.

Next WPAD planning meeting will be held on Wednesday, 29 April at 16:30 UTC.

#meeting-notes

Accessibility Team meeting notes – April 17, 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.

Continue the discussion on the team’s planned work for 5.5

The team continued discussing our planned work and projects for the 5.5 release:

These are all well underway and work and/or discussion has begun. If you are interested in collaborating and contributing to any of these efforts please feel free to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the team in the comments of this post or in our Slack channel.

Start planning for WCEU 2020 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/.

It was recently announced that WordCamp Europe 2020 is moving online and they are now asking teams to prepare for Contributor Day.

Our team needs to plan ahead in order to make the most of this day. The activities that we need to prepare for are:

  • Update the ‘Getting Started at a Contributor Day’ 
  • Video introduction from an experienced contributor
  • Plan your team tasks for the day (good first tasks vs. tasks for experienced contributors)
  • Look for experienced contributors that will facilitate and help other contributors during the day
  • Plan intro session 
  • Make a rough estimate of how many working groups your team needs during the day
  • Schedule a special office hour in 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/. specifically targeted for new contributors (between 25 May and 3 June 2020)

We’ve created a spreadsheet to keep track of progress and status. If you’re interested in helping please reach out.

WP Accessibility Day update

Plans for WPAD are slowly moving along due to a shortage of volunteers and world events. The aim is to announce it next week.

The organizing team will create a list of microtasks, so more volunteers can get involved.

The next meeting is scheduled for Wednesday, April 22 at 16:30 UTC in the #accessibility-events channel in Slack.

Open floor

@afercia has a proof of concept patch for ticket #40330 that adds a “Load more” button below the attachments list in the Media Library. He’s asking for feedback on the button’s behavior once all attachments have been loaded.

Please feel free to review the ticket and add your comments.

#meeting-notes

Accessibility Team meeting notes – April 10, 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.

Meeting times change to observe DST

The team agreed to move the meeting times one hour earlier to adjust to DST. @nrqsnchz will update the meeting dates in the various places where it is announced.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. auto-updates 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 team behind the Core auto-updates plugin has made significant progress and is requesting feedback from the team. There is a call for testing with all the details and information needed.

Working plans for 5.5

As discussed in previous meetings, the team has formulated a list of projects we’d like to focus on for 5.5:

Call for volunteers

Folks who are interested in participating and helping on any of these projects are welcome to chime in in the comments of this post. We’ll continue to discuss progress and direction during our weekly team meetings.

5.4 retrospective and call for feedback

The team was reminded of the 5.4 retrospective and call for feedback and was invited to leave comments on that post.

+make.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//core/

#meeting-notes

Accessibility Team meeting notes – April 3, 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.

Help testing the WordPress Auto-updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.

@audrasjb and @pbiron asked the team for help testing the Auto-updates Feature plugin. This is 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 that aims to provide automatic updates for plugins and themes feature as an opt-in feature.

You can find more information about the plugin on the plugin’s page and report any issues you come across to the plugin’s GitHub repository.

Statement on the use of Crowdcast for WP community events

We discussed the Community team’s consideration to use the Crowdcast streaming platform for online events. Knowing how inaccessible Crowdcast is, the Accessibility team wants to help the Community team find better alternatives. @joedolson wrote this post with recommendations for alternative setups and suggestions to make online events more accessible.

Open Floor

Team meeting time change due to DST

@ryokuhi reminded the team that we haven’t made a decision about moving our meeting time to adjust to DST. This is a change we’ve done in the past, and that other teams have done as well.

The consensus from team members present was that it was OK to move the meeting time, but we’d like to give folks who could not attend the chance to have their say.

Please let us know in the comments of this post if you are in favor of or against moving the meeting time an hour earlier to adapt to DST.

We will be making a final decision during our meeting next week.

+make.wordpress.org/core/

#meeting-notes