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



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

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

The Accessibility bug scrub will be held on Friday 3 May 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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 Notes for 4/26/2019

Meeting transcript on Slack

1) WordPress 5.2 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 work statement

Nobody was clear on what this was about, but believe that it may have been in reference to the accessibility team update published by @audrasjb on April 21st. Assuming it is, and moving on.

2) User Input Validation

Tickets have been raised recently that address this, and it’s something that we should handle much better throughout WordPress. Input validation and error reporting are addressed in two 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/. success criteria, both within the parameters we’re committed to meeting (Level A and AA.)

@greatislander will create a tracking ticket to get this started. It’s probably a large project to tackle, but having a ticket to reference for future planning is useful.

4) Update on Automated Testing

@greatislander Requested a change in agenda order. Based on feedback from @rianrietveld after 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/. London, is exploring ways of producing a more usable list of output. Currently, tests produce a massive quantity of terminal text. Need to reduce the scope of tests run at once and/or generate a reference file that can be used outside of terminal.

3) Uniform Search planning

@joedolson and @nrqsnchz worked on documenting the current user experience on each search model. Progress is being tracked on Google docs.

Next step is to elaborate the basic outline produced in the first phase to incorporate the assistive tech experience.

Noted that while the original project scoped 5 independent search experiences, changes to WordPress since the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket was created have reduced this to 4. Yay!

5) Update on User Docs

While nobody had time to follow up on this during the week, @bemdesign noted that @chrisvanpatten posted a brief comment in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor 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 noting that progress is finally moving forward again.

6) W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. Alt Decision tree

Finalized decisions: We are going to copy the decision tree into the WordPress 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) handbook, then begin sourcing translations.

Question was raised whether we will share translations with the W3C – and yes, we will.

@audrasjb has volunteered to tackle the copying process.

7) Updated accessibility ticket spreadsheet

@nataliemac worked on updating the accessibility ticket spreadsheet, confirming resolution on numerous tickets.

Accessibility meeting agenda for 26 April 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 26 April 2019 at 15:00

  • WordPress 5.2 Accessibility Team work statement (@audrasjb)
  • Discuss user input validation (see #47018) (@afercia)
  • Update on Uniform Search progress (@joedolson, @nrqsnchz)
  • Update on Automated testing (@greatislander)
  • Update on User Handbook (@karmatosed)
  • Continuing discussion: strategies for use of the W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. alt decision tree in translations. (@joedolson, @afercia)
  • Open Floor

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

The Accessibility bug scrub will be held on Friday 26 April 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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