LLMReview.ai is built to be usable by everyone, including people who rely on keyboards, screen readers, or reduced-motion and high-contrast settings. Our target is WCAG 2.1 Level AA across the product. This page describes what is implemented today, what we know still falls short, and how to reach us when something gets in your way.
Keyboard & focus
Every interactive control is reachable and operable by keyboard, with a visible focus ring.
A skip link jumps past the navigation to the main content on every page.
The command palette (Ctrl/⌘ + K) and dialogs close on Escape, trap Tab focus while open, and return focus to where you were when they close.
Touch targets meet the 44px minimum on mobile.
Screen readers
Long-running analyses announce their progress: job stage transitions are narrated through a polite live region, so you are never waiting in silence.
Icons are decorative (hidden from assistive tech) unless they carry meaning, in which case they are labelled.
Form fields have programmatic labels; validation errors are announced inline.
Vision & motion
The public product uses one calibrated light theme with high-contrast carbon text and semantic analytical colors that are never the only differentiator.
prefers-reduced-motion is respected — animations and transitions are suppressed when your system asks for less motion.
High-contrast mode preferences are honored in the design tokens.
Data tables scroll within their own container instead of stretching the page, and key numbers use tabular numerals for alignment.
Known limitations
Some dense analytical charts do not yet have full non-visual equivalents. Every chart's underlying numbers are available in the accompanying tables or downloadable exports (CSV/Excel), and we are working on richer chart descriptions.
Generated downloads (PPTX decks, PDF reports) follow presentation-document conventions and are not yet audited against PDF/UA.
Feedback
If you hit an accessibility barrier anywhere in the product, email support@llmreview.ai with the page URL and what happened. Accessibility reports are triaged with the same priority as functional bugs.