At this moment there are 13 issues open with the label Merge Proposal: Accessibility
These are the most complex issues with high priority. That doesn’t mean that the other 70 open issues are trivial, they also need to be addressed to make 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.
https://wordpress.org/gutenberg/ work for everyone.
If you want to help out, please select one of the “Issues that need work, review, feedback, discussion”. Andrea Fercia (@afercia) is the lead for the Gutenberg 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). (https://en.wikipedia.org/wiki/Accessibility) issues, contact him in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ with the issues if you need more information.
Issues that have an owner and are actively worked on:
- 5983 – List block and screen readers: greatly inconsistent behavior
- 4187 – Publishing Flow accessibility
- 1311 – react-datepicker is not accessible
Issues that need work, review, feedback, discussion:
- 5242 – Constrain tabbing within popovers and similar components, the PR needs a review
- 2146 – Switches should always show On/Off label
- 6002 – JAWS (screen reader) doesn’t read out the editable areas content
- 7246 – The ChromePicker (Custom color picker) is not accessible
- 5694 – Simplify and streamline keyboard navigation through blocks
- 3218 – Consider a mechanism to customize shortcuts, e.g. Ctrl + backtick
- 3217 – Components and features should be logically placed within the main regions
- 1934 – Unexpected reverse-tab behavior
Issues to do just before merge or after the feature freeze: