Accessibility

Our commitment

StatusForge is built on the belief that every person is worth knowing accurately. That belief includes people who use screen readers, who navigate by keyboard, who need higher contrast, who avoid motion, who use the site on small screens or with limited bandwidth. The product fails its mission if any of those people cannot use it.

We target conformance with WCAG 2.1 Level AA across the public-facing site. We are not yet fully there. This page lists what we have already done, what we are working on, and how to tell us about something we missed.

What we have already done

• Skip-to-main-content link on every page so keyboard users can jump past the navigation.
• Reduced-motion support. If your operating system is set to prefer reduced motion, the timed narrative on /intro skips straight to the call-to-action.
• Decorative elements are labeled as such. The 3D brain visualization is marked decorative for screen readers and conveys no information needed to use the site.
• Real labels on form fields alongside placeholder text where required.
• Semantic HTML — headings, lists, sections, footers, navigation landmarks.
• Schema.org structured data on profile pages so assistive technologies can recognize the content type.
• No autoplay audio anywhere on the site.
• Donations and intake do not require JavaScript for the legal disclosures and CTAs to be readable. (The form submission itself uses JavaScript for security and validation.)

What we are still working on

We are honest about the gaps. As of this date, the following items are known and tracked internally for resolution:

• Color-contrast verification for the lowest-emphasis text styles (small captions, footer labels) against the dark background.
• Keyboard-navigation testing across the burger menu, intake form sequences, and dashboard interactions.
• The dashboard’s social-verification flow currently uses a browser prompt and alert dialog for the verification step. We are replacing this with a proper modal that is fully keyboard- and screen-reader-friendly.
• Captions and transcripts for any future video content.
• Independent third-party audit (planned for the year after launch).

If something is broken for you

Email [email protected] with the subject line “Accessibility Issue”. Tell us what you were trying to do, what assistive technology you were using, and what went wrong. We respond within 5 business days. If your issue prevents you from completing a critical task on the site (signing up, deleting your data, contacting support), tell us that explicitly — we will treat it as urgent.

If we cannot solve your issue inside the product, we will help you complete it manually. No accessibility-related contact will ever be ignored.

Standards and references

We aim for WCAG 2.1 Level AA. Where state or federal law (including the Americans with Disabilities Act, Section 508, and California Unruh Act) sets a higher standard, we comply with the higher standard.

This page itself will be updated whenever we discover a new gap or close an existing one. The most recent update date appears at the top.