Accessibility Team Meeting Notes: February 19, 2021

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.

Final review of WordPress 5.7 goals

  • Accessibility: most tickets have already been handled.
  • Media: starting to plan 5.8 goals.
  • Documentation and Accessibility Patterns: no updates on progress. @joedolson said he would shift some of his focus in to writing WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) 2.1 docs now that we’ve arrived at RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. Contributions always welcome. Plan is to have docs done by 5.7 release. Contribute here.
  • WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Screen: @joedolson created a TRAC ticket. Next week we’ll discuss timeline.
  • Learn WordPress: meeting notes from yesterday.
  • Themes: no update to share.

Open floor