Writing a blog post on the 25th of December allows me to write about wishes. And one of them is to have better tools for accessibility auditing.
This post tries to describe what I would like to get from the tool. Realistically, noting too advanced.
Top of the site
Skip to content Skip to searchWriting a blog post on the 25th of December allows me to write about wishes. And one of them is to have better tools for accessibility auditing.
This post tries to describe what I would like to get from the tool. Realistically, noting too advanced.
It was not clear to me if WCAG 4.1.3 can be applied to native mobile applications. At least on both iOS and Android. So I did some research and came with the conclusion that we can and should or even must use status messages also on native mobile apps.
Minimum viable product that is not accessible is not really minimum. And then also the WCAG on level AA is the minimum, a baseline. When we reflect over those two facts – we must agree that MVP must at minimum conform to WCAG 2.1 on level AA. If this MVP will run in EU’s public sector even WCAG 2.1 on level AA alone is not the minimum.
Extremely valuable documentation that reveals some interesting points about future of Web Accessibility Directive monitoring methods, tools and also some less clarified reporting matters. The accessibility statement automatic analysis will most certainly also have a central role and it is worth following on the Accessibility Conformance Testing rules that are the engine of all automatic tools out there.
Beside content accessibility guidelines we must also be aware of authoring tool accessibility guidelines that your editor tools, for example content management system, should adhere to