Accessibility Team Meeting Notes: 30 August 2019

Meeting transcript on Slack

Progress report on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. tickets

There is 66 accessibility focused tickets in milestone 5.3:

  • 10 are fixed
  • 56 still need to be fixed

To help them moving forward, two additional bug scrubs are scheduled, on Tuesday 3 September 2019 at 15:00 UTC and Tuesday 10 September 2019 at 15:00 UTC.

@afercia noted that some of those tickets are close to commit. Andrea will try to commit some of them in the next days.

@joedolson won’t be able to address his own tickets until 14 September.

@anevins is going to update the #core-media tickets spreadsheet to highlight media tickets that still need some work.

Assign owners for tickets slated into WordPress 5.3 milestone

@abrightclearweb asked what ticket owners are supposed to do exactly.

@anevins: “They make sure the work gets done by either assigning the work to a practitioner (comes with pretty pleases) or by doing it themselves. They just drive the work forward.”

@joedolson: “it can including writing the patch, but doesn’t need to.”

@abrightclearweb took ownership on #47477. @kjellr will also help on that ticket if needed.

For further informations about testing a patch, see the related core handbook page. However, that assumes contributors have a working development environment. Patch can also be tested directly by applying the patch manually. @joedolson also shared a generic document on creating and applying patches (not about WordPress, but it would work).

At the moment this summary is written, there is still 10 tickets without owner in milestone 5.3. Any contributors are welcome to ask for ownership in 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). ( SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel.

Open floor

The accessibility team discussed ticket #47149. Some comments were added in the ticket.

@afercia noted aria-controls shouldn’t be used anymore and quoted a tweet by Steve Faulkner:

In short, JAWS was the only 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. to actually use aria-controls and the implementation was just confusing. An other post was also quoted for further informations about aria-controls.

@audrasjb changed the initial 5.3 additional bug scrubs time from 14:00 UTC to 15:00 UTC to make it easier for US contributors.

#5-3, #bug-scrub, #tickets