fora is built to be usable by everyone, including people who browse with a screen reader, navigate by keyboard, or need larger text and higher contrast. This page describes where we are, what we have done, and how to tell us when we get it wrong.
1.Our target
- We aim to meet WCAG 2.2 Level AA, the standard most widely used to judge whether a website is accessible.
- We treat this as an ongoing commitment rather than a finished project. New pages and changes are checked against it.
2.What we have done
- Text alternatives. Meaningful images carry descriptive alternative text. Purely decorative images are marked so screen readers skip them instead of reading noise.
- Keyboard access. Every link and control can be reached and operated with a keyboard alone, with a visible focus indicator.
- Contrast. Body text is set to meet or exceed the 4.5:1 contrast ratio against its background.
- Structure. Pages use real headings in order, landmark regions, and semantic HTML rather than styled
divs, so assistive technology can navigate them. - Motion. The moving panel on the home page pauses on hover and is disabled entirely for anyone whose system is set to reduce motion.
- Zoom and reflow. The site reflows to a single column and remains usable at 200% zoom and on small screens.
3.Known limitations
- The home page hero is a large decorative wordmark with photography passing across it. It is presentational and is not announced to screen readers; the same information is stated in text immediately below it.
- We have not yet completed a formal third-party audit. Our checks to date are internal and automated.
4.Tell us about a barrier
We want to hear about it
If any part of this site is difficult or impossible for you to use, email support@withfora.com with the page and what went wrong. We aim to respond within five business days and to fix confirmed barriers as quickly as we reasonably can.