When accessibility is instantly implemented it is also instantly available to the customer and doesn’t require additional tasks or resource planning.
So when you have fixed your tools to meet the basic accessibility standards, you don’t want to do it again for future solutions. You rather want it to be an integrated part of your development process.
First step was to include the accessibility to our definition of done (DoD). This is how it looks like:
- Avoid creating own components, rather try to keep to the standard as much as possible
- Tabbing order is intuitive (e.g. the first thing you’d see on the screen, should be the first to be tabbed)
- All basic function of the web site should be readable with screen reader (e.g. JAWS)
- If functions cannot be used without shortcuts, you need to support them
- Take care of accessibility for every functionality even if you think, a blind person cannot use it
- Conform colour-contrasts
- Run automatic check (e.g. with Accessibility Insights)
Read more about the importance of accessibility and how immediately take care of it in this LinkedIn article.