search

samccone / a11yscore

0 stars 0 forks source link

Heuristics for testing a web page for a11y #1

Open samccone opened 8 years ago

samccone commented 8 years ago

q: What are some high level things that we can detect and warn people about on a given website.

cc @marcysutton @addyosmani

marcysutton commented 8 years ago

Just a few to get started: -Click events bound to non-interactive elements (check for native elements or [tabindex=0]) -Positive tabindex values, like tabindex="3" (possibly > 2 instances, since flagging only one is usually a false positive) -Color contrast -Missing form labels -Missing button/link text -Invalid ARIA attributes or values (aria-role, role="someRandomThing", etc.) -Multiple IDs with the same value

Rather than writing your own tests for all of this, you could run sites against aXe or Chrome A11y Developer Tools.

samccone commented 8 years ago

awww yes, I think we can just run these :)

https://github.com/GoogleChrome/accessibility-developer-tools https://github.com/dequelabs/axe-core