This week in WordPress Accessibility, February 26, 2018

Transcript of a meeting in Slack.

About placeholders

In ticket 40460 there is discussion should placeholders be added to wp_login_form(). @afercia have written good summary in the comments why in this case placeholders would not be a good idea.

Therefore we decided to close the ticket. But discussion can continue in the ticket and valid use cases are welcome.

Handbook status update

First of March was our first deadline. We are not going to make it but we are progressing OK. We have marketing plan what to do after basic articles have been written.

List of must-have 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). ( fixes in 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. for version 1

  • Keyboard navigation through blocks needs to be greatly simplified and streamlined. See the experiment with navigation mode / edit mode.
  • For some components, there’s the need to constrain tabbing within the component (i.e. they should behave like “modals”).
  • The publishing flow needs to be simplified, currently its accessibility is terrible.
  • Everything needs to live inside the landmark regions.
  • Text mode: a simple textarea is the only guarantee to enable users to publish content, regardless of the device / technology they use.
  • Documentation for keyboard shortcuts and keyboard-only users.

We need to start testing more and open actionable issues.

Open floor

We ALL love snow and gold weather! ☃️❄️🌬