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 A WordCamp is a conference where the WordPress community come together to teach one another what they’ve learned throughout the year and share the joy. https://central.wordcamp.org/about/. 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 A WordCamp is a conference where the WordPress community come together to teach one another what they’ve learned throughout the year and share the joy. https://central.wordcamp.org/about/. 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 A WordCamp is a conference where the WordPress community come together to teach one another what they’ve learned throughout the year and share the joy. https://central.wordcamp.org/about/. 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.



Accessibility team meeting notes for 17 May 2019

Meeting transcript on Slack

Primary Goals for WP 5.3

Rough timeline for 5.3 is mid-August. That gives about 2 months until 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..

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/ audit issues are in progress, and are a priority; other priority should be the 43 tickets slated for next releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. Many of these are media tickets, which would be a good focus with broad applicability between Gutenberg and classic editor experience.

@anevins and @karmatosed will take lead to triage and communicate with media/design teams as appropriate.

Improving form input validation is a valuable project, but probably not in scope for 5.3. @greatislander will open ticket, with plans to research during 5.3 and hopefully be able to implement in 5.4.

User Handbook

No evidence of this happening; we need to work on reviewing the content written by @abrightclearweb, get it up to date, then make a publication plan.

Gutenberg Open Forum

New member made observations about learning 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:

Sometimes it can be tricky to move blocks around. Drag and drop doesn’t work too well for me, so I use the arrows on the left side. They’re not that big in size and can be tricky. I was also stumped by the right 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. settings when I first got started. It took some time to get use to how they work and how the context changes depending on what block I’ve selected, if any.

@Chuck, user of Zoom software

Improving control size would be helpful.

Accessibility meeting agenda for 31 May 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 31 May 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
  • Glossary Implementation on Make sites
  • 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.
  • Gutenberg open floor discussions

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

The Accessibility bug scrub is intended to be held on Friday 31 May 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 meeting agenda for 24 May 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 24 May 2019 at 15:00.

  • WordPress 5.3 main Accessibility Team goals:
    • Team focuses
    • Media tickets
    • 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
  • Gutenberg open floor discussions
  • Quick review of the “alt text decision tree” Handbook document

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

The Accessibility bug scrub is intended to be held on Friday 24 May 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: May 10, 2019

Meeting transcript on Slack

WPCampus 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) Audit

Discussion about how to organize both 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/Accessibility and Design teams to handle accessibility issues (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/ issues but also fundamental issues found in the editor).

The accessibility team main concern is that the Gutenberg team would maybe going to focus on GitHub issues (which is understandable) and ignore the wider 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./usability issues uncovered in the report.

The idea is not to ignore GitHub issues but to find ways to handle broader fundamental issues with the editor.

@mapk: “One super helpful way to understand the usability issues from the report would be to actually see the tests performed”. The question to be asked to WP Campus (@bamadesign).

The Gutenberg team asked to open issues for these general issues to they can be milestoned. There is a need for a starting point.

@afercia noted many (if not all) of the broader accessibility/usability issues reported in the Accessibility Audit were already reported by the team: Report on the Accessibility Status of Gutenberg (October 29).

@karmatosed: “I’ll add that whilst we all need to learn and iterate, there’s been a large move on that front. I want to for example call out the work of @lukepettway and others coming to the design meeting. @bemdesign has been incredible coming to design a11yAccessibility 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) audit triages”. Which is a good starting point to work together on design principles in the editor and in WordPress in general.

According to the Gutenberg Team, it would be useful to use concrete examples for each issue so it can be better surfaced/discussed/addressed.

@afercia: “I’d like to outline is that these broader issues can’t be solved with technicalities. There’s no ARIA, no focus management, no JS tricks that can solve these broader issues.”

@audrasjb said moving from the main editor to the 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. and go back to the editor is an example of very difficult tasks the users have to do to manage their post when they use assistive technologies.

@matveb: said it also shows something everyone was aware, but never reached a good solution for.

@afercia listed some examples:

These two examples are more related to the general design rather than technical implementation. Settings should be easily reachable starting from 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.. Ideally, they should follow the block in the DOM order. That makes the whole idea of sidebar an accessibility anti-pattern.

@joedolson: “Getting a shared understanding of the essential characteristics of interaction flow for 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 is a valuable step in getting a better process; discussing the technical issues with the sidebar/block interaction helps us get closer to that.”

@matveb: “I’d like to understand if the problem is even more fundamental between trying to accommodate editing and navigation under a single view mode […] it can be an essential paradigm for framing the conversation”

@afercia said other similar editors have a clear distinction between “view” and “edit” mode.

@joedolson: “Understanding the problems with jumping between disparate objects using the keyboard is a big part of it. Keyboard are largely dependent on linear flow, moving one step at a time between neighboring focusable objects. Keyboard shortcuts, while possible, are extremely difficult to make 1) perceivable, 2) understandable and 3) robustly supported, which makes them hard to depend on. So recognizing that elements that aren’t sequential is very difficult to navigate between is important. The problem isn’t in making the keyboard navigation better, but placing related elements next to each other in the DOM.”

In conclusion, it was decided to add a 15 minutes timeslot in the accessibility meeting time dedicated to having an open floor period where anybody can show up and chat on any accessibility topic.

Accessibility meeting agenda for 17 May 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 17 May 2019 at 15:00.

  • WordPress 5.3: main accessibility goals.
  • Update on Automated testing (@greatislander)
  • Update on User Handbook (@karmatosed)
  • WPCampus Accessibility Audit: discussion about how to organize both 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/, Accessibility and Design teams on process improvement for accessibility. For coordination purposes, this portion of the meeting will begin strictly at 10:45 am.

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

The Accessibility bug scrub is intended to be held on Friday 17 May 2019 at 14:00 and will be focused on remaining Gutenberg issues with the “Needs Accessibility Feedback” label. @afercia is unable to run the bug scrub, and we don’t currently have a plan for somebody else to lead this.

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