Accessibility

Our goal

We want Eleven to be usable by as many people as possible, including people who use a keyboard, a screen reader, or other assistive technology. We’re working toward WCAG 2.2 AA as a practical target where reasonably achievable across the product.

Where we are today

Eleven is in Beta, and accessibility is an ongoing effort rather than a finished state. We do not claim certification, full compliance, or guaranteed accessibility — we audit and improve real issues as we find them, and we expect to keep finding more as the product grows.

Work completed so far includes, among other improvements:

• A skip-to-content link on every page.
• Semantic landmarks (header, nav, main) throughout the authenticated application and public pages.
• Visible focus states and keyboard-operable controls across interactive elements.
• Accessible names on icon-only controls that previously had none.
• Status/availability information conveyed through text and icons, not color alone.

Known limitations

Some data-dense surfaces (for example, the Team pitch and draft board) are visually complex, and we’re continuing to improve their experience for screen-reader and keyboard users specifically. We haven’t yet run a comprehensive assistive-technology testing pass across every screen.

Reporting a barrier

If you hit an accessibility barrier anywhere in Eleven, please tell us — it helps us prioritize real fixes over assumptions. Email robert@quinterodigital.com with what you were trying to do, what happened, and the device/assistive technology you were using, if applicable.