Accessibility Statement

1. Commitment

Formgopher is built and maintained by a single independent developer. Accessibility is treated as an ongoing effort rather than a one-time checkbox: this site gets reviewed and improved over time as issues are found or reported, rather than fixed once and left alone.

2. Standards Formgopher Targets

This site is built and checked against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the most widely used benchmark for web accessibility. Full conformance hasn't been verified by an independent, third-party audit, but that standard is the bar this site aims to meet.

3. What's Already in Place

• Semantic structure. Pages use proper landmarks (header, nav, main, footer) and a logical heading order, so assistive technology can navigate the page structure directly instead of reading it as one flat block.
• Keyboard support. Every interactive control — links, buttons, the theme toggle, the mobile menu, the FAQ accordion — is a native, focusable element that works without a mouse, and none of the site's styling removes the browser's visible focus indicator.
• ARIA labeling on custom widgets. The mobile menu, theme toggle, and FAQ accordion expose their open/closed and selected/unselected state (aria-expanded, aria-selected, aria-controls) so screen readers announce them correctly.
• Alt text. Meaningful images (plan illustrations, the logo) have descriptive alt text; purely decorative images are marked so screen readers skip them instead of reading noise.
• Light and dark themes. Both are available and stay in sync across the site, for anyone who needs a specific contrast or brightness level to read comfortably.
• Responsive layout. Pages reflow for small screens and browser zoom rather than requiring horizontal scrolling or a fixed layout.

4. Known Limitations

No site is perfect, and this one hasn't had a full third-party accessibility audit. Known gaps being worked on include broader testing across different browser/assistive-technology combinations and verifying every color pairing against WCAG's exact contrast thresholds.

If a subscription to the paid plan is started, checkout happens on Stripe's own hosted payment page, not on formgopher.com. Formgopher doesn't control the accessibility of that page directly; it's governed by Stripe's own accessibility work, not this statement.

5. Feedback and Contact

Hitting a barrier anywhere on this site while using a keyboard, screen reader, or any other assistive technology is worth reporting — it'll get looked at. Reports can include the page, the browser/assistive-technology combination, and what happened, sent to roger@atroger.com. Every report gets read, even if not every fix happens immediately.