Commitment
AuthTally (a product of AR Development) is used at real events by organizers, voters, and entry submitters of all abilities, so accessibility matters to how AuthTally is built, not just the marketing site. AuthTally aims to meet WCAG 2.1 Level AA as its ongoing standard across the site and the app. This is a goal being actively worked toward, not a certified or audited conformance claim.
What's Built In Today
Some of the accessibility practices already in place across AuthTally:
- Semantic HTML structure with proper headings, landmarks, and native interactive elements (buttons, links, details/summary) instead of custom widgets where possible
- Descriptive alt text on meaningful images, with purely decorative images hidden from screen readers
aria-labelandaria-expandedattributes on icon-only controls like the theme toggle and mobile menu- A light and dark theme with sufficient color contrast for text and interactive elements in both modes
- Keyboard-operable navigation, menus, and expandable content, since voters are often tapping through on a phone with a screen reader
- A voting experience that doesn't require creating an account or installing an app, reducing friction for assistive technology users
- Respect for the
prefers-reduced-motionsetting, disabling non-essential animations for users who request it
Known Limitations
AuthTally hasn't been through a formal, independent accessibility audit. As AuthTally continues to be built, some areas may not yet fully meet WCAG 2.1 AA, particularly newer features, uploaded organizer content (like entry photos and descriptions, which aren't controlled by AuthTally), and third-party services embedded in AuthTally (such as Google Sign-In). These gaps are being actively worked on over time.
Feedback
If you encounter an accessibility barrier anywhere on this site or in the AuthTally app, please reach out. Include the page or feature involved and a description of the issue, and it'll be looked into.
Contact: roger@atroger.com