Accessibility Team meeting notes for January 31 2020

These are the weekly notes for the 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 that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Incorrect cursor used on buttons

The accessibility team has made a final recommendation on this ticket from the WPCampus accessibility report. The pointer cursor should be reserved for links, and an affordance for buttons can be communicated in other ways, such as noticeable hover and focus styles.

Disabled button doesn’t look disabled

The team also shared their recommendation on this ticket about disabled button styles. Because contrast requirements don’t apply to disable interface controls, we don’t have any issues with the design team making a call on changing this.

Video 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. settings for alternate sources

The team agreed to have a more broad-ranging conversation about the accessibility of navigation to and from the block inspector (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.) 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. We’ll continue this discussion at next week’s meeting.

Feedback on the Navigation block

Members of the team are encouraged to try out the Navigation block in Gutenberg and provide feedback. We’ve created a spreadsheet to collect everyone’s results.