WordPress Accessibility Meeting Notes for 27 Sept 2019

Meeting transcript on Slack

Progress on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets

31 open tickets in 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) focus remaining. There are a total of 138 open tickets in the 5.3 milestone. 6 tickets relating to contrast and focus have been reopened for continuing work. 32 tickets in the accessibility focus have been fixed.

CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. Changes related to link focus style

After the focus and contrast changes, the link focus style is a dotted outline. This is a regression against the previous 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., which used a blue glow focus. Discussed options and agreed that switching to a solid outline and adding and outline offset of 2 pixels will improve. Also noted that the admin nav menu is using the same color as the main focus, needs to be reversed.

This change will also need to be ported to 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/, and that may not be able to happen by 5.3.

Off-agenda: discussion on whether we have time to complete changes.

@karmatosed raised a question whether we should focus on moving continuing changes to 5.4 rather than attempt to complete this for 5.3

After discussion, generally agreed that the continuing changes for focus and contrast are minor tweaks, and while there are a large number of tweaks, we should have time to complete them.

Noted that while release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. status closes trunk to new enhancements, tweaks to the contrast changes are bugs, and can continue through the RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage.

Next accessibility bug scrub

Next bug scrub will happen on Tuesday 1 October 2019 at 16:00 UTC in the #accessibility 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.

Twenty Twenty Status

Twenty Twenty has 9 accessibility labelled issues awaiting attention. @poena raised the menus as the biggest concern, needing review. There’s a PR by @acalfieri waiting to land on the menus – we’ll take a look at it after this is finished.

New EU accessibility standards

Note: on 23 September 2019, the first stage of the European Union directive on accessibility of websites and mobile applications came into force. This stage requires all public sector new websites to be accessible. Existing websites have until 23 September 2020 to be made accessible; all public sector mobile apps have until 23 June 2021.

The EU directive uses 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.1 at level AA as their reference for a harmonized standard.

After WordPress 5.3, we will discuss updating the WordPress accessibility standards to WCAG 2.1. This was last discussed in October 2018, and was inconclusive.

WordPress Accessibility Meeting Notes for 20 Sept 2019

Meeting transcript on Slack

Open Floor

There was no set agenda for this meeting.

The meeting opened with a discussion of ticket #30180. The ticket, while not of itself a crucial task, was a kicking off point for a deeper conversation about trying to work more effectively across teams.

This was a complicated conversation, so in this summary I aim to do my best to convey the essence of the conversation, primarily focusing on the experience from within 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. For a detailed picture, please read the meeting transcript.

The overall point was the difficulty the accessibility team in specific – and all teams in general – have had in making progress on tasks that fall across other team’s responsibilities. This is particularly difficult in the more specialized areas of code, such as the Media Library, where specific knowledge of the inner workings are more rare.

The problem we would like to solve is, at root, the challenge of balancing goals with labor in a realistic manner. We, as a team, have very limited time that can be committed to any given task as well as having expertise primarily in accessibility, which may not benefit us mechanically when working in a specific idiosyncratic technology. To help meet goals, we have tried to work with other teams to delegate responsibility on tickets to people with more specialized experience, while remaining available to consult on the results.

The experience we have had with this has been poor, leaving us feeling that our only ability to accomplish goals is the technical tasks we have the bandwidth to complete ourselves. While many people do step forward and help, this doesn’t result in an overall feeling of forward momentum.

Among the challenges shared are the fact that many contributors to the project cannot plan their time effectively due to the lack of a structure 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. schedule. While employees of a company will have their hours structured such that they can dedicate the necessary time to a project after that project is scheduled, voluntary contributors inevitably have other responsibilities and commitments. Short notice of a release schedule does not allow those contributors to arrange their availability such that they can contribute in a healthy manner.

The meeting discussed four separate major challenges:

  1. Meeting specific goals for the accessibility tickets planned for WordPress 5.3.
  2. Communicate more effectively across teams.
  3. Component maintainence priorities.
  4. Release scheduling and the budgeting of goals over time.

It is important to us, as a team, to state that this is a problem we see throughout the WordPress project, and is not unique to this release or to our team. We don’t feel that these problems reflect individual failures; it’s the result of a systematic failure stemming from a lack of collaborative processes and insufficient opportunity to plan during the times between releases.

Better long-term planning and better release schedule pre-planning to set goals and define the capabilities across teams would be a critical step in making each team be more capable of meeting their individual goals.

The Accessibility Team would like to continue to move forward to work across teams to make this a better experience. We’re continuing to explore ways to improve the process through cross-team collaborations and shared meetings, and hope that we can all collaborate more effectively with improved processes.

Accessibility Team Meeting Notes: 13 Sept. 2019

Meeting transcript on Slack

Update on 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Tickets & Upcoming Bug Scrubs

There are now 49 open tickets in the 5.3 milestone report. Some of these are close to commit, a few more have patches but need finalizing. Still some tickets without owners.

Scheduling an additional bug scrub for Tuesday 17 September 2019 at 15:00 UTC to work through them further.

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/ Navigation/Edit Mode.

The team discussed the practical experience of using the mode switching in various AT we’ve tested. The call for testing did not yield any responses.

Several people noted that the new 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. works quite well for keyboard users.

For screen readers, it’s more mixed: requires double escape to exit edit mode, the experience with NVDA/Firefox is buggy. NVDA has some known issues right now with Firefox, so this should be tested with FF 71 Nightly, which is anticipated to fix some issues.

Overall:

– It’s a good improvement for keyboard 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) and some assistive tech.
– Doesn’t work well with Firefox and NVDA: this needs to be investigated and addressed before 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..
– Add audible messages, e.g.: “WordPress edit mode activated” and “WordPress navigation mode activated”.
– The button text needs to communicate the available action. 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. type is not an action. Should probably be ‘Edit [block name]’ That would be much more clear for all users.

Twenty Twenty: Should main menu and search be ARIA modal dialogs?

The accessibility team discussed ticket #80.

Team agreed that yes, this is an appropriate choice and would make a good model for implementation of an ARIA modal for menus. The source order should be retained in logical order rather than moving the menu source elsewhere so that child theming isn’t made excessively complicated.

Feedback on Gutenberg Proposal for Content Block Areas

Commented that the use of modes has potential for good UI, as discussed for Navigation/Edit in the editor, above.

No other new comments, other than reiterating that 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. continues to be a concern in Gutenberg.

Open Floor

  • Discussed accessibility of 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/. threads. They are now navigable and readable. Notifications are limited, but this is also true for all other users. Slack threads can be used, but (as always) are not the right place for primary topics of conversation.
  • @nataliemac needs volunteer teaching assistants for WCUS.

Accessibility Team Meeting Agenda: 16 August 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 16 August 2019 at 15:00 UTC.

  • Priorities & goals for WordPress 5.3 and
  • Assign owners for tickets assigned to WordPress 5.3 milestone
  • Open floor

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

The Accessibility bug scrub will be held on Friday 16 August 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).

Call for Gutenberg User Testing

With the release of Gutenberg 6.3 yesterday, 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/ implemented an important new step towards a more accessible editing experience. That change is the Navigation Mode. Rather than needing to tab through hundreds of controls to get from 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. to block, you will move from block to block using a single press of the tab key, and can enter Editing Mode by hitting Enter.

This change is an important step to allow users to navigate between blocks more easily . However, it needs user testing to identify weaknesses, bugs, and usability flaws.

In testing this 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., please consider the following questions:

  1. Is my place on the page clear when navigating?
  2. Can I identify the block I’m on when tabbing through resources?
  3. Do the keyboard assignments work as expected in my setup?

Any feedback you can provide is welcome; but as always, with any feedback, please clearly indicate the browser, operating system, and any 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 in use during your test.

Gutenberg 6.3 can be downloaded from the WordPress.org repository.

You can add your feedback as a comment here, or directly to the relevant GitHub issue.

Accessibility Team Meeting Notes: 9 August 2019

Meeting transcript on Slack

Call for Testers: Support Navigation and Edit Mode

For reference, see the related pull request on Gutenberg GitHub repository.

Lacking a pre-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. version to share, we’ll wait on the official release 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/ 6.3, then publish a call for testers. Release is expected on Wednesday, August 14th.

Joe Dolson will write up the call for testing.

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

Will pass off further discussion of WP Accessibility Day to the volunteer organizing team. Need to establish a method to coordinate between organizing team & then plan periodic reports back to the Accessibility team on progress.

@audrasjb & @joedolson will coordinate that.

Ticket Ownership for WordPress 5.3

Proposed schedule has been published, so we have some idea of what to target. Proposed schedule is for November 12th, so we’ll operate on the assumption of a probably September 23rd 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..

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) team members should spend time reviewing the tickets slated for next release to identify candidates they believe they have time to coordinate on.

Even if a ticket has an owner, a lack of activity may suggest that the owner will be open to changing the assignment.

Need to communicate more with the Media team to get ownership of the many Media tickets targeted for this release.

Don’t hesitate to request feedback from various teams by assigning task-related keywords to a ticket – this can be significantly more effective than trying to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” an individual for feedback.

Open Floor

Work on re-thinking 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. 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. has been slow; trying to get that re-started as the summer winds down.

@arush mentioned earlier that 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/. threads are now accessible; need to do some research to identify whether we should now allow them in meetings.

@joedolson will contact Amanda to ask for her thoughts.

@joedolson has started working on updating .screen-reader-text info; but it’s been slow.

Discussed mobile device skip link issue addressed.

Accessibility Team Meeting Agenda: 9 August 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 9 August 2019 at 15:00 UTC.

  • Call for testers on “Support Navigation and Edit Mode”
    (for reference, see the related pull request on Gutenberg GitHub repository)
  • WP Accessibility Day – pass off to organizing team for planning. Set organizing team meetings
  • Assign owners for 53 tickets assigned to WordPress 5.3 milestone, 5.3 development schedule
  • Open floor

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

The Accessibility bug scrub will be held on Friday 9 August 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 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.

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.