Accessibility Team Meeting Notes for 5 July 2019

Meeting transcript on Slack

Media tickets updates

A few more tickets discussed, but relatively little progress this week.

Success Metrics and framing for 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/ SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.

@sarahmonster raised the concern that we were looking at options without having done prior work to determine what was considered success and how to evaluate that, so we’ve taken a step back to define that.

Secondarily, we want to move away from discussing this in a private conversation and improve transparency as we brainstorm.

Still in progress at defining the path for opening this discussion; summer plans & WCEU have slowed progress.

WCEU Update

@ryokuhi was at the WP 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) theme auditor table, which was very interesting.

@poena commented that the themes table was in a different room from the theme auditor, so they couldn’t work together.

@ryokuhi Would very much like to see more presence from #a11y team members at major WordCamps and contributor days

Discussed the feasibility of that, given the expense for members & size of the team; considered the possibility of having a remote 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/. focused on accessibility.

Gutenberg Open Forum

@ryokuhi will add some thoughts about Snackbars

Continuing discussion, by mutual agreement, focused on how we might imagine a remote contributor day for accessibility & other teams.

X-post: Updates to the WordPress User & Developer Survey

X-comment from +make.wordpress.org/updates: Comment on Updates to the WordPress User & Developer Survey

Accessibility Team Meeting Agenda for 5 July 2019

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 5 July 2019 at 15:00 UTC

  • Update on Media accessibility tickets
  • Discuss success metrics and framing for evaluation of solutions for 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/ SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. planning
  • Update from 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. EU attendees
  • Open floor discussion on Gutenberg

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub is cancelled for today.

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).

Accessibility Team Meeting Notes for 28 June 2019

Meeting transcript on Slack

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) amendments to theme review requirements

The theme review team would like to assess adding some of the theme accessibility-ready requirements to the standard requirements for all themes hosted at 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/. They specifically want to focus on requirements with low design impact, anticipating pushback from theme designers.

@joedolson recommended incorporating the keyboard navigation, control, skip link, and form labeling requirements from the existing accessibility-ready requirements.

Briefly discussed why 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/. can’t be directly applied to the theme review process.

WP Theme Auditor

@greatislander provided a summary of the current status of WP Theme Auditor project and invited theme review team members to participate in developing the next steps in the project – better reporting outside of the terminal & making it easier to run the theme auditor via the command line.

@poena Mentioned that the Tide team has data from Lighthouse run in the theme directory previewer.

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/ “Snackbar” UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.

Gutenberg 6.0 introduced a new type of notice used for saving/failure notices, described as “Snackbar” notices.

These notices introduce some accessibility concerns, primarily 1) because they appear in an obscure corner of the screen disassociated from the action that triggered them (problematic for zoom users, tunnel vision caused by various eye disorders, screen readers) and 2) because they automatically disappear after 10 seconds, violating the WCAG timing requirements.

There are additional questions whether this mode of notification is fundamentally valuable. Further discussion will be addressed on GitHub to address whether this is a good method of providing notices; if so, the accessibility issues will be further assessed.

Accessibility Team Meeting Agenda for 28 June 2019

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 28 June 2019 at 15:00 UTC

  • Themes: what accessibility requirements should be integrated into normative theme requirements?
  • Themes: WP Theme Auditor tests
  • Discuss 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/ “Snackbar” notices.
  • Update on Media accessibility tickets
  • Discuss success metrics and framing for evaluation of solutions for the Gutenberg SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. planning
  • Update from 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. EU attendees
  • Open floor discussion

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub is intended to be held on Friday 28 June 2019 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).

Accessibility Team Meeting Agenda for 14 June 2019

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 14 June 2019 at 15:00 UTC

  • Evaluate @afercia proposal to make some of the WPCampus report tickets a “blessed task” so they can be addressed across several releases
  • Specific tickets are identified as Media / Themes team priorities. Let’s try to find the best way to collaborate to solve them
  • Few tickets are very quick fixes if there’s design feedback. Let’s discuss how to address them with Design team
  • 4 other specific tickets:
    • https://core.trac.wordpress.org/ticket/45094
    • https://core.trac.wordpress.org/ticket/47123
    • https://core.trac.wordpress.org/ticket/47456
    • https://github.com/WordPress/gutenberg/issues/15847
  • Open floor discussion

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub is intended to be held on Friday 14 June 2019 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).

Accessibility Team Meeting Notes for 7 June 2019

Meeting transcript on Slack

Team Goal progress

Media tickets: moving forward, could use some prioritization work to help with focus. More about order than importance. Ordering will be set in the tracking spreadsheet. In general, tackling major tickets like #47141 should probably happen first, as those should get plenty of time in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to identify any problems from the patching. @afercia committing patch for #47141 today. [Publication Note: committed in https://core.trac.wordpress.org/changeset/45499.]

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: no update today.

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 at WCEU

Want to try and integrate some testing with 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 into the Gutenberg testing plans for 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. EU. @joedolson will publish a notice to announce that; @audrasjb and @afercia will take care of helping coordinate tests.

Gutenberg Keyboard Shortcuts

@karmatosed posed questions concerning how to optimize current keyboard shortcuts, plan a pattern to ensure future optimization, and how to make shortcuts visible to users.

@joedolson Noted that the fundamental idea of creating ideal keyboard shortcuts is flawed because of the complexity of conflicts and patterns for existing shortcuts in other applications. Creating customizable keyboard shortcuts that allow users to optimize shortcuts for their own use is the ideal. This doesn’t prevent us from choosing sensible defaults, but sensible and optimal are not the same.

Agreed that what we need to do is explore mechanisms to create a keyboard customization UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. This UI would also help as a mechanism to communicate shortcuts.

Gutenberg Open Floor

@joedolson updated group on progress from last week’s discussion of the flawed sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. UI in Gutenberg. @nrqsnchz, @sarahmonster, @mapk, and @kjellr have been brainstorming ideas and concepts that provide a design that can display the controls effectively without depending on a sidebar that is located remotely in the DOM.

@afercia commented on recent PRs and proposals that are doing a good job of moving controls out of the sidebar.

Gutenberg open floor review

Original proposal suggested trying open floors for a month to integrate team meetings. Assessing effectiveness.

General feeling is that communication is improving, but question posed whether resolutions to the larger Gutenberg issues as raised in the WP Campus audit are happening.

Group agreed that more time is required to assess this. Will reassess in a month, and consider at that time whether to continue practice for a month or try an alternate approach. Alternate approaches from anybody who wants to make a change should be made available in writing at the meeting.



Gutenberg testing with Assistive Technology at WordCamp EU

During 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. EU, the testing team will be running usability tests of the WordPress block editor. We’re hoping for some of those tests to be run using 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 and by users with disabilities.

Jean-Baptiste Audras (@audrasjb) and Andrea Fercia (@afercia) will help coordinate this with the testing team. If you’re going to be attending WordCamp EU in Berlin and use any form of assistive technology or identify as a user with a disability, please comment on this post, so we can communicate with you to coordinate that!

We’re interested in any and all user testing: if you experience issues due to dyslexia, color blindness, use a screen reader, use zoom applications or any other input or output tool, please consider helping out!

Tests will be scheduled for 30 minute blocks and time slots are available on either Friday, 21 June or Saturday, 22 June.

Accessibility Meeting Agenda for 7 June 2019


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 7 June 2019 at 15:00.

  • WordPress 5.3 main Accessibility Team goal progress:
    • Media tickets progress
    • 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 progress
  • Accessibility team at 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. EU
  • Gutenberg keyboard shortcuts discussion
  • Gutenberg open floor discussion
  • Gutenberg open floor discussions: helpful or not?

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub is intended to be held on Friday 7 June 2019 at 14:00.

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).



Accessibility Team Meeting notes for 31 May 2019


Meeting transcript on Slack

Team Goal progress

Media tickets: tickets have been reviewed and triaged, media team is starting to tackle. @afercia is tackling #47141.

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: many issues are in progress. Early yet.

Glossary implementation on Make sites

Discussed concerns with implementation. Current implementation has some degree of 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), but doesn’t give users a lot of choice; no option to dismiss definitions and reads them automatically, rather than giving user choice. The vocabulary is probably also too broad, encompassing general terms not specific to WordPress that perhaps should not be in the purview of our glossary.

Goal:

1) The user needs to be able to choose whether to read the definition or not.
2) In order for that to be relevant, focusing on the term needs to convey to the user that there is more information – a definition – available.
3) Having activated the definition, the user needs to also be able to choose how to move away from it.
Right now, none of these are true.

Gutenberg 5.8 Widgets UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.

Quickly got derailed into general comments about the Gutenberg sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. construction. Noted some issues in the widgets UI:

  • 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. selection area invisible in some circumstances
  • Add block button not findable

Gutenberg open floor

Discussed sidebar issues, and the specific concerns about focus order & DOM ordering that make the sidebar difficult for keyboard navigation.

@joedolson, @mapk, @sarahmonster, and @nrqsnchz will coordinate to plan possible options.