This update informs you about:
- new and updated documentation on wpaccessibility.org;
- work in progress.
New and updated documentation on wpaccessibility.org
- Quick wins to improve the accessibility of your website.
- The Reading guide, vistors now can find content by role or expertise instead of by topic only.
- A Disclaimer, in short: This documentation is intended to help the WordPress community understand and implement accessible practices. It is not a replacement for the official Web Content Accessibility Guidelines.
Focus management
- Frontend code: Handling visual and keyboard focus, with subpages addressing:
- Webforms: No positive tabindex.
- Design and user experience: Styling focus and hover states of interactive HTML elements.
Training
Start with accessibility: How to get training to learn web accessibility, with subpages addressing:
- Online training. An overview of training, meetups and conferences to learn accessibility.
- Books. Recommended books about web accessibility.
- Online events. An overview of training, meetups and conferences to learn accessibility.
- Knowledge resources. Knowledge resources and newsletters on web accessibility.
- Education & Discussion Groups. How to find peer support and meet people to learn accessibility.
Current handbook
We will wait with transferring the current Accessibility Team Handbook to GitHub until later, we need to explain and discuss this in more detail with the Meta team. Maybe WordCamp Europe will be a good opportunity for this.
Work in progress
We are discussing if and how to set up a “Can I Use” section for core blocks (GitHub issue 294). With the status per core block about its accessibility. All input is appreciated.
Documentation we are working on to improve at the moment:
- Alt text for images in the content and in theme development.
- Headings in the content and in theme development.
- Introduction to WCAG.
- Accessibility for your business.
- Legislation.
All feedback on the documentation is very much welcome.