Accessibility

We design and build FRA aiming to align with the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. This is a design goal we work toward, not a certification — we have not undergone a formal third-party accessibility audit, and we won't claim a conformance level we haven't verified.

• Semantic HTML and heading structure, rather than div soup, for pages and the components they're built from.
• Interactive elements (buttons, links, form fields) built as real, focusable, keyboard-operable elements rather than click handlers on non-interactive divs.
• Text and background color pairings drawn from our documented brand palette, chosen with contrast in mind.
• Form fields on this site (like the data-request form on our Privacy Policy page) use associated <label> elements rather than placeholder-only labeling.

This list describes engineering practices we build against, not a completed, audited inventory — parts of the site are still being built out, and we treat accessibility gaps we become aware of as bugs to fix, not as acceptable permanently.

We have not run a comprehensive accessibility audit against this site, so we are not in a position to list every gap with confidence. If something doesn't work well with a screen reader, keyboard-only navigation, or other assistive technology, we would genuinely like to know — see below.

If you run into an accessibility barrier anywhere on this site, please tell us through the Contact page, including the page you were on and what happened. We read every report that comes in through that channel.