We didn't invent our own accessibility rules. Orbit is built on axe-core, the
same engine used by major
testing tools industry-wide, and pairs it with WCAG 2.x contrast math and The A11y Project's
community-maintained checklist, so what you see in Orbit reflects established, peer-reviewed
accessibility guidance.
Orbit automates what can be reliably automated, and is transparent about the rest. Automated tools like
axe-core are excellent at catching objective, rule-based violations, but a meaningful share of WCAG success
criteria require human judgment.
What's Automated
Missing or empty alt attributes
Insufficient color contrast ratios
Missing form labels
Invalid or misused ARIA attributes
Missing document landmarks
Duplicate IDs
Missing page language attributes
Heading structure issues (ex. skipped levels)
What Needs a Human Touch
Alt text accuracy and meaning, not just presence
Logical reading order for screen reader users
True keyboard operability of custom widgets
Clarity of error messages
Content that makes sense out of visual context
Intuitive interactions for screen reader and switch device users
No automated scanner, including Orbit, can verify these.