Accessibility Team Meeting Agenda: January 31, 2020

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). ( team meeting on Friday, January 31, 2020, 16:00 UTC.

  • Incorrect cursor used on buttons: this TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket needs a decision from the accessibility team.
  • Disabled button doesn’t look disabled: another Trac ticket that could use our collective feedback so it can move forward.
  • Video Block: alternate sources such as ogv and webm file formats: 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. issue that needs the team’s feedback.
  • Test the Navigation block: Last week the design team asked our help with testing the Navigation 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.. If you can, please add your feedback and comments to the linked spreadsheet.

The Accessibility bug scrub will be held on Friday, January 31, 2020, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at (requires registration).