Keyboard navigation
Every interactive element is keyboard-accessible. Tab order is meaningful, focus rings are always visible, modal traps work cleanly. Power users can run the workbench keyboard-only.
Accessibility
Built to WCAG 2.1 AA. Working toward AAA.
OmniTakeoff is used by estimators with disabilities every day. Accessibility isn't a checkbox — it's a workflow constraint we treat as load-bearing as performance or security.
What we support
Features in production today
Screen reader support
All form inputs have associated labels, dynamic content uses aria-live regions, navigation landmarks let screen-reader users skip directly to main content. Tested with NVDA, JAWS, and VoiceOver.
Color contrast
All text meets WCAG AA contrast ratios (4.5:1 normal, 3:1 large). Brand orange (#FF6B00) on background passes 4.5:1. Status indicators don't rely on color alone — every colored element has an icon or text label.
Reduced motion + larger text
prefers-reduced-motion respected app-wide. Browser zoom up to 200% works without horizontal scroll. No fixed-position content blocks viewport at high zoom levels.
Standards
What we conform to
- WCAG 2.1 Level AA conformance — verified by automated + manual audit
- Section 508 (US Federal) compatibility for government customers
- EN 301 549 (EU) parity for European customers
- ARIA 1.2 best practices for custom components
Roadmap
What's next
- WCAG 2.2 Level AAQ3 2026
- Voice-control integration (VoiceOver Speech, Dragon)Q4 2026
- Third-party accessibility audit + VPAT publicationQ4 2026
- WCAG 2.2 Level AAA partial conformanceQ1 2027
Found a barrier?
Tell us. We'll fix it.
Response within 1 business day. Critical barriers triaged same day.
Phone (TTY)
+1 (555) 555-0199 ext. A11Y
TTY-supported line for users who prefer voice.
VPAT available
Voluntary Product Accessibility Template
Government + enterprise customers can request our latest VPAT (based on WCAG 2.1 AA + Section 508). Email accessibility@omnitakeoff.com.