Accessibility
We build this site to WCAG 2.2 Level AA, and we treat that as a launch condition rather than a backlog item.
What that means in practice
- Every non-decorative image has alternative text. The content model will not publish one without it.
- Every color pair is contrast-tested and the measured ratio is recorded in our design tokens.
- Everything is operable by keyboard, with a visible focus indicator that is never obscured.
- Interactive targets are at least 44 by 44 pixels.
- Headings follow a real hierarchy — one
h1per page, no skipped levels. - Link text is descriptive. Our build rejects “click here”, “learn more” and “read more” as accessible names.
- Form errors are associated with their fields and summarized at the top of the form on a failed submit.
prefers-reduced-motionremoves transforms and parallax and renders our animated elements in their final static state.- Search results, filter counts and form status are announced through live regions, debounced so they report the settled result rather than every keystroke.
- The site works at 200% zoom and at 320px width without horizontal scrolling.
- Nothing important is conveyed by animation, color or a visualization alone — there is always a text equivalent.
How we test
- Automated accessibility checks run on every route in our build pipeline, and a violation fails the build.
- Keyboard paths through the header, mega menu, search palette, filters and forms are covered by automated tests.
- A manual screen-reader pass is part of our pre-launch checklist.
Where we know we are not there yet
This statement will name any known issue, with a date by which we expect to fix it, once the pre-launch audit is complete. We would rather list a known gap than claim conformance we have not measured.
Tell us if something does not work
If any part of this site is difficult or impossible for you to use, please write to info@resiliencesol.com and describe what you were trying to do. We will respond, and we will tell you what we are going to do about it.