Accessibility
Accessibility statement
Standing Proof is built against WCAG 2.1 AA as its design target. This page says what that means concretely: what has actually been measured, what is practiced but not yet independently audited, and what we know is not right yet.
What has been measured
Every route in the product and on this site, sixty-eight screens, is walked by an instrumented audit at phone widths (320px and 375px) that fails the build path on two hard rules: no page may scroll horizontally, and every interactive control must meet WCAG 2.5.8’s minimum target size of 24×24 CSS pixels. Both currently pass everywhere, and the audit is a script we re-run, not a one-time review.
What is practiced throughout
Semantic HTML with a heading hierarchy; a skip-to-content link on application screens; visible labels on form fields rather than placeholder-only inputs; text alternatives on images written to describe what is in the frame; icon-only controls carrying accessible names; and horizontally scrolling regions (wide tables) that are keyboard-focusable with a visible cue that more content exists. The 320px measurement above doubles as reflow evidence: content that lays out without horizontal scrolling at 320 CSS pixels is what WCAG’s reflow criterion asks of a desktop page at 400% zoom. Status indicators pair color with a text label rather than relying on color alone.
Known limitations
Exported PDFs are tagged. Résumé exports to PDF carry a real structure tree — headings, lists and paragraphs a screen reader can navigate rather than one undifferentiated block of text — and declare a document language. The same résumé also exports as DOCX and plain text. Every design in the library is structurally a single reading column with real text and real headings: no tables, text boxes, or images.
No third-party audit has been performed yet. The measurements above are our own instrumentation. An independent audit producing a VPAT/ACR sits on our institutional readiness roadmap, triggered by the first engagement that requires one, and until it exists we will not imply otherwise.
Tell us what is in your way
If something here does not work with your screen reader, switch access, keyboard, or anything else, write to hello@standingproof.com with the page and what happened. Reports like that get fixed as defects, not filed as feedback.