Accessibility
What has been tested, and what has not
WCAG 2.1 Level AA is the target this site is built to. It is a target rather than a claim of conformance, because parts of it have been verified and parts have not — and this page says which is which.
Last updated 26 August 2026
Where things stand
A target, stated honestly
Plenty of accessibility statements assert conformance that has never been tested. That is worse than saying nothing: the reader finds out it was untrue at the exact moment they are relying on it.
So this page separates the two. Below is what was actually measured during the build, and after it, what has not been done yet. If you use assistive technology, the second list is the one worth reading.
Verified
What has been checked
- One main heading per page, in a logical order
- Every page has exactly one <h1> and no skipped heading levels. Checked in the rendered page on each build, not in the source.
- Every form field has a visible, associated label
- Checked programmatically across all forms. No placeholder-only fields, and no duplicate element IDs that would break the association.
- Visible keyboard focus everywhere
- A two-pixel focus ring on every interactive element, in a color that changes with the background so it stays visible on both the dark and light sections.
- Text contrast meets AA by construction
- Color is applied through a token system rather than chosen per element, and a build step fails if any text color is set outside it. The brand orange is replaced with a darker shade on light backgrounds, where the original does not pass.
- The page reflows without horizontal scrolling
- Checked at 375 and 1440 pixels wide on every page. Dense tables scroll inside their own labeled, keyboard-reachable region rather than pushing the page sideways.
- Motion preferences are respected
- Animation and transitions are reduced to nothing when the browser reports a preference for reduced motion.
- A skip link to the main content
- The first thing reachable by keyboard on every page.
- The site works without JavaScript
- No page ships any. Nothing here depends on scripting to be read or navigated, which also means nothing breaks on a filtered network that blocks it.
Not yet done
Known gaps
These are outstanding. They are listed rather than omitted because a gap you can see is one you can work around, and a gap you cannot see just wastes your time.
-
Testing with actual screen readers
No page has been driven end to end with NVDA, JAWS, or VoiceOver by someone who uses one. This is the largest gap in the list and automated checks do not substitute for it.
-
A full automated audit
Individual criteria have been checked as pages were built. A complete pass with an auditing tool across every page has not been run.
-
Zoom and text resizing to 200%
Layouts use relative units throughout, but this has not been verified page by page.
-
Color vision deficiency simulation
Color is never the only way information is conveyed, but this has not been checked under simulation.
-
Cognitive and plain-language review
Some pages carry dense regulatory and contracting language by necessity. No formal readability review has been done.
Unresolved — not published
A full WCAG 2.1 AA audit, including testing with real screen readers, before launch
Until this is done the page states a target rather than conformance, which is the honest position. Screen reader testing is the item that matters most and the one automated tooling cannot stand in for.
Tell us
If something does not work
Email info@intel-analysis.com with [ACCESSIBILITY] in the subject line. It reaches a principal directly — this is a small firm and there is no ticket queue in between.
Useful things to include, if you have them: the page, what you were trying to do, and the browser or assistive technology you were using. None of it is required. A message saying "the contract vehicles table is unusable for me" is enough to act on.
If you need information from this site in a different format, ask for it that way and it will be sent to you.