Accessibility Team Meeting notes: Feb. 22, 2019

Meeting notes on Slack

Uniform Search Planning (#31818)

  • Start advance planning on unifying search 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. – targeting 5.3
  • Focus on primary search interfaces (posts, comments, users, themes, plugins, etc.) first, but consider 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/ searches as well
  • Aim to reduce from 5 distinct search UIs to max of 2
  • Search is handled variably in PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. & JS, JS is in jQuery, backbone, and ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. in different contexts.
  • @ryanshoover proposed an ES6 class usable in all JS contexts.
  • Will begin by listing requirements (@joedolson)

Update on User Handbook

  • Still no updates anywhere. No idea what’s happening here.

Prioritize Gutenberg 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) issues for 5.2

  • Set working meeting to triage the 122 current Gutenberg a11y issues to identify priorities for WP 5.2
  • @ryelle, @greatislander, @sami.keijonen, @afercia, and @joedolson will find a time to triage and create a priority spreadsheet.

Issues for Discussion

#13900: Replace placeholder with label

  • Definitely in favor of principle
  • Proposed design seems fine, as long as it’s consistently applied; we didn’t see any specific concerns with the proposal.

#13688: Surface keyboard shortcuts visibly

  • Intriguing idea
  • Could be helpful for helping people remember shortcuts
  • Visual only; screen reader users already have audio reminders of shortcuts
  • Probably not a priority, but this could be useful.

#13663: Improve keyboard navigation between 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. inspector and block

  • Solution keeps being proposed to have 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. toggle shift focus to the inspector; these functions need to be separate.
  • If the toggle shifts focus, it means there is no option for sighted users to view the inspector settings without being forced out of their current context