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 Agenda: May 22, 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, May 22, at 15: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, May 22, at 14: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: WCEU 2020 Online Contributor Day: All that team facilitators and experienced Contributors need to know

X-post from +make.wordpress.org/updates: WCEU 2020 Online Contributor Day: All that team facilitators and experienced Contributors need to know

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 Agenda: May 15, 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, May 15, 2020, at 15: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, May 15, 2020, at 14: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: WCEU Online 2020 Contributor Day: Submit your introduction videos, office hours times and introductory session needs this week

X-post from +make.wordpress.org/updates: WCEU Online 2020 Contributor Day: Submit your introduction videos, office hours times and introductory session needs this week

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 Agenda: May 8, 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, May 8, 2020, at 15: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, May 8, 2020, at 14: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

Announcing the first WordPress Accessibility Day!

Starting at 18:00 UTC on October 2nd, 2020, the WordPress 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 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!

We anticipate opening for speaker submissions within the next two weeks, where we’ll be looking for speakers who want to explore a wide variety of topics, including

  • theme accessibility,
  • 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 accessibility,
  • accessibility testing,
  • writing and managing accessible content,
  • the future of WordPress accessibility,
  • WordPress and ATAG (Authoring Tool Accessibility Guidelines),
  • current and upcoming accessibility standards (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.2, WCAG 3), and
  • assistive technologies.

Follow along at WP Accessibility Day, where we’ll be publishing our call for speakers, call for sponsors, and all sorts of information about our plans for the day!

To learn more, join members of the organizing team for an online panel discussion of WordPress Accessibility and the event on Thursday, May 21st, 2020 – Global Accessibility Awareness Day. We’ll chat about accessibility, talk about the event, and answer your questions.  Share your questions on our Twitter account @WPAccessibility or send an email through the WP Accessibility Day contact form. Time and venue yet to be determined – sign up for the WP Accessibility Day email list to be notified about the panel!

Do you want to help organize WordPress Accessibility Day? We can use more volunteers! We’re currently meeting every Wednesday at 16:30 UTC in the #accessibility-events 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 – join us if you want to help!

#wpa11y

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