Design for access, then verify the whole experience.

Our target

The public Clarient site is being built toward the Web Content Accessibility Guidelines 2.2 at Level AA. That target applies to the complete page and to the responsive variations people receive on different devices; it is not limited to a component library or an automated score.

This page is a pre-release accessibility statement. It is not a declaration that every route currently conforms. A dated statement will be published only after the manual and automated acceptance work is complete.

What is built into the public site

The implementation uses semantic document structure and aims to keep interaction understandable without relying on colour, motion or pointer use alone.

• A skip link and consistent landmark structure
• Visible keyboard focus and keyboard-operable navigation
• Responsive reflow down to 320 CSS pixels
• Labels, descriptions, error summaries and field-level recovery for forms
• Reduced-motion and forced-colour considerations
• Real text for essential explanations rather than text embedded in decorative images

How release testing is planned

The release review covers keyboard-only operation, focus order and visibility, zoom and reflow, text alternatives, form errors, colour contrast, reduced motion, forced colours and representative screen-reader checks. Automated analysis is used to find repeatable failures, not as a substitute for manual judgement.

The responsive matrix includes 320, 360, 390, 600, 768, 1024, 1280, 1440 and 1920 pixel viewports. Interactive states and content changes are tested as part of the same experience.

Known pre-release limitations

Product scenes contain dense operational information. Each scene has surrounding explanatory text, but screen-reader wording and high-zoom presentation still need final review. The legal, pricing, contact-owner and editorial-author surfaces are deliberately withheld from public release while their business inputs are unresolved.

The monitored accessibility feedback owner is also not yet approved. Until that route is configured and tested, this statement remains excluded from indexing.

Feedback and alternatives

The Contact page includes a specific accessibility route and asks only for the information needed to understand the barrier and reply. It will accept messages only after a monitored owner and secure delivery path are configured.

When that route is live, people will be able to request the same information in a more usable format. No telephone-support claim is made.