the ‘official’ WCAG methodology is https://www.w3.org/TR/WCAG-EM/ (also most time intensive); automated tests are useful, but cover only a subset. This is also a useful resource on accessibility testing: https://www.gov.uk/service-manual/helping-people-to-use-your-service/testing-for-accessibility … A pragmatic checklist: https://a11yproject.com/checklist/
-
-
-
Thanks!
Kraj razgovora
Novi razgovor -
-
-
For automated tests, I recommend - WAVE (https://wave.webaim.org/extension/ ) - axe (https://www.deque.com/axe/ ) - ARC Toolkit (https://www.paciellogroup.com/toolkit/ ) - Chrome Audits (built-in on Chrome Dev Tools) - tota11y (https://khan.github.io/tota11y/ ) Also, axe Pro is designed to guide manual testing
- Još 1 odgovor
Novi razgovor -
-
IMHO there’s no one right or best way to approach this. I’d suggest different testing methods depending on the size of the site and on the interactive features available to users. W3C released a methodology that you might want to look into.
-
Thanks! This is what you're referring to, correct?https://www.w3.org/WAI/test-evaluate/conformance/ …
- Još 1 odgovor
Novi razgovor -
-
-
Have a look at https://accessibilityinsights.io - not a perfect solution, but a good start for sure.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.