The standard we aim for
We build this site to target the Web Content Accessibility Guidelines, WCAG 2.2, Level AA, across the public pages and the workflows that matter: reading the practice pages, sending an enquiry, and applying for a role.
We describe that as a target rather than a declaration of conformance, because conformance is a judgement that requires testing with real assistive technology and expert review. See the assessment status below.
What is built in
- Semantic landmarks and headings, in a single logical order per page, with one first-level heading each.
- A skip link to the main content as the first focusable element on every page.
- Visible focus outlines on every interactive element, and focus is scrolled clear of the fixed header.
- Interactive targets sized to at least 24 by 24 pixels.
- Text and interface colours checked against their actual background at every surface elevation.
- Fluid type with nothing below twelve pixels, and layouts that hold up under browser zoom and larger text.
- Form fields with real labels, grouped into named sections, with help text tied to each input.
- Errors announced in text, never by colour alone, and a confirmation that explains what happens next.
- Alternative text on meaningful images and diagrams; decorative shapes hidden from assistive technology.
- Credibility evidence is static; the public pages contain no continuously moving content.
- A reduced-motion preference disables entry and instrument motion, and instruments render at their final value.
- Content never depends on animation. Entry states are applied by script, so if scripting fails everything is visible.
What we measured
Automated source checks cover heading structure, form labels, narrow-layout table labels, minimum type and target rules, and known overflow patterns. The Astro compiler and production build run with no diagnostics.
Colour contrast is computed from the design tokens for each ink and surface pairing rather than judged by eye. Content is visible by default if the optional motion script does not run.
Known limitations
- The security verification challenge on our forms is a third-party component. We configure it for a dark theme and a flexible size, but its internal behaviour is outside our control.
- Two technical diagrams are dense by nature. Each carries a text description, and the delivery sequence has been rebuilt as ordinary markup so it reflows and scales with your font size, but a complex architecture drawing is still harder to read than prose.
- The administration console is an internal tool. It follows the same design system but has not been through the same measurement as the public pages.
Assessment status
The checks above were carried out by the development team. The site has not yet had an independent accessibility audit or a complete test pass with screen readers, voice control, and switch access, so we make no formal conformance claim or accessibility conformance report.
Tell us about a barrier
If something here gets in your way, we want to know, and we will give you the information another way while we fix it. Email info@jpginfotech.com or call+1 703-208-0530.
It helps if you can tell us the page address, what you were trying to do, and what browser or assistive technology you were using. We will acknowledge your message and tell you what we intend to do about it.