Accessibility Team Meeting Notes: February 1st

Meeting notes on Slack

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. Phase 2 Widgets Screen

  • Goal is to start using blocks on the widgets screen; building out blocks to match existing widgets
  • Discussion of the general design, layout and 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). ( of new page
  • Current design repurposes Gutenberg layout
  • Reproduces same issues with 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. as in Gutenberg editor
  • Should we focus on improving the Sidebar 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. or different design in Widgets?
  • Design should be consistent; so fixing the Sidebar UI is important
  • Many possible issues to address; top priority is topbar/inspector (Sidebar) navigation

Validate 5.2 Accessibility focused tickets scope / Triage update

Currently 30 accessibility tickets milestoned for 5.2. All of them have owners. Depending on 5.2 schedule, we may not be able to handle more.

5.2 schedule is currently an unknown factor.

Current goal: handle these 30 tickets for 5.2, revise based on schedule.
Ambition goal: work on #31818 (Uniform Search) if 5.2 schedule allows.