Fix A & AA accessibility issues throughout Backoffice

[nielslyngsoe]

There are currently a large number of accessibility issues throughout the Backoffice.
We have decided to collect the issues on a separate tracker to provide an overview of the current state.

Issues:
https://github.com/umbraco/Umbraco-CMS.Accessibility.Issues/issues

Status board:
Umbraco-CMS Accessibility Issues (view)

How to grab a task

• Have a look through the table above and pick an issue you'd like to fix.
• Write a comment that you are looking into it
• Fix the issue 😄
• Submit a PR on the CMS repository with a reference to the issue from the Accessibility repository by writing Fixes umbraco/Umbraco-CMS.Accessibility.Issues#1234 somewhere in the PR comment.

Fixing an issue

Here are some links to various tools and reference materiel should you require any help 🙂

Websites & Articles
Web Content Accessibility Guidelines (WCAG) Overview
Getting Comfortable with WCAG
Accessibility according to actual people with disabilities
Colorblind Accessibility on the Web – Fail and Success Cases
AngularJS guide to accessibility

Tools
Accessibility Insights - Chrome Extension
Axe: Accessibility for web development
Color Contrast Checker

Activate built in screen reader
Mac - toggle Voice Over by pressing Command-F5
PC- toggle Narrator by pressing Ctrl + Winkey +Enter

If you have any questions you can reach out either here or on one of the Umbraco Community #accessibility channels:
Slack or Discord

Big thanks to the wonderful Danny Lancaster who has created the accessibility audit report which the Accessibility issues originate from.

Ps. If you find something that is not mentioned please report it, thanks

[nul800sebastiaan]

Pro tip, in your commit message, on a new line, writing the same notation works too:

Fixes umbraco/Umbraco-CMS.Accessibility.Issues#1234