Accessibility statement

sbTix is designed to be usable by everyone

sbTix aims to meet WCAG 2.1 Level AA — the standard the U.S. Department of Justice and the European Accessibility Act 2019/882 both reference for commercial websites. If you encounter a barrier that prevents you from using any part of the platform, we want to hear about it and fix it.

How we comply

Keyboard navigation. Every button, link, form field, and modal on sbTix is reachable and operable using only a keyboard. Test it yourself: unplug your mouse and try buying a ticket.
Screen reader support. All form inputs have programmatic labels. Every image has meaningful alt text. Custom widgets (modals, dropdowns, tabs) expose their role and state via ARIA attributes.
Color contrast. Body text meets a 4.5:1 contrast ratio against its background; large text meets 3:1. Verified against WebAIM's contrast checker on every theme.
Visible focus. Keyboard focus is always visible via a clear outline on any interactive element.
Reflow at 320px. The site works at 320px wide without horizontal scrolling on the page body. Wide content (tables, code) scrolls inside its own container.
No orientation lock. Content adapts to portrait and landscape.
Reduced motion. Animations respect prefers-reduced-motion.
Semantic HTML. Native <button>, <a>, <input> throughout — no fake buttons built from <div onclick>.

How to report a barrier

If something on sbTix doesn't work for you, email [email protected] with:

The URL where you hit the barrier
What you were trying to do
What assistive technology you use (screen reader name + version, keyboard-only, magnifier, etc.)
What happened vs. what you expected

We aim to acknowledge every accessibility report within 2 business days and prioritize barriers that block a user from completing a core flow (buying tickets, managing an event, checking in).

Known limitations. The scanner PWA at sbtix.net/scanner/ uses camera capture and QR code decoding — it may not work with all assistive technologies. Door staff who need an alternative can enter a ticket ID manually in the same interface.

The standards we reference

WCAG 2.1 — W3C Web Content Accessibility Guidelines, Level AA target
ADA Title III — U.S. Department of Justice web guidance (2022)
European Accessibility Act 2019/882 — applies to services offered to EU consumers after 28 June 2025
Section 508 (29 U.S.C. § 794d) — federal ICT; met via WCAG 2.1 AA harmonization

Continuous improvement

Accessibility isn't a one-time audit — it's a build habit. Every new feature ships with an accessibility review as part of our compliance-by-construction workflow. The audit process is documented internally and applies to every code commit.

Last reviewed: 2026-08-06 · Owner: [email protected] · Related: Security · Privacy · Trust