Conformance target
We target WCAG 2.1 Level AA for both draftgrade.com and the SaaS at app.draftgrade.com. That standard is the floor; we aim higher where the cost is reasonable.
What we have done
- Keyboard navigation works everywhere. Every interactive control is reachable by Tab, activatable by Enter or Space, and shows a visible focus ring. We use
focus-visibleso the ring appears for keyboard users without distracting mouse users. - Skip-to-content link at the top of every page. One Tab away from the address bar, you can jump past the header navigation.
- Semantic landmarks throughout. Every page uses
<header>,<nav>(witharia-labelfor primary vs. footer nav),<main>, and<footer>so screen-reader users can jump between regions. - Color is never the only signal. Verification status badges use text labels alongside color, so red/green color blindness doesn't hide whether a citation is verified or hallucinated.
- Live region for verification results. When the verifier finishes, screen readers announce the result automatically via
role="status" aria-live="polite"— no need to manually navigate to find the report. - Motion respects
prefers-reduced-motion. If your operating system requests reduced motion, our CSS shuts down transitions and animations. - Form labels are explicit. Every input has an associated
<label>; error messages are programmatically linked viaaria-describedby. - Adequate contrast. Our color palette targets the 4.5:1 contrast ratio for body text and 3:1 for large text required by WCAG AA. Dark mode mirrors the same ratios.
- Page titles are unique and meaningful. Browser tabs and screen-reader page lists differentiate every page.
Known gaps
We are committed to fixing these. None are blockers but we list them openly rather than wait until someone files a bug.
- The methodology renderer outputs long-form Markdown; we have not yet manually audited every heading order for skipped levels.
- The OG/social preview image carries the wordmark only and is generated programmatically. Production will replace it with a designed asset that survives high-contrast mode.
- We do not yet run automated WCAG checks (axe-core) in CI — planned for the next sprint.
Report an accessibility problem
If something doesn't work for you, we want to know. We treat accessibility bugs as first-class — same priority as a broken sign-in flow.
Email hello@josephfus.co with the subject "Accessibility issue." Tell us what page, what assistive technology (if any), and what you expected to happen. We respond within two business days and prioritize the fix accordingly.
The bigger picture
Roughly one in four U.S. adults lives with a disability. Among the population most likely to need DraftGrade — people who can't afford a lawyer — that rate is higher, not lower. An inaccessible access-to-justice tool is a contradiction in terms. If you ever find this page rings hollow because the rest of the site isn't living up to it, hold us accountable.