Nexus Eclipse

Services

Accessibility Testing Services

WCAG-oriented accessibility testing of the journeys you name: keyboard, structure, names, and contrast — not a certificate or a VPAT mill.

The problem

A product can pass a functional case and still be unusable with a keyboard, a screen reader, or a visible focus. Teams then discover the gap in a customer complaint or a procurement questionnaire — not in QA.

Accessibility testing services are structured checks against the WCAG success criteria you care about, on the journeys you name. We are not a certification body. We do not issue a conformance badge, a legal opinion, or a completed VPAT unless that artefact is separately scoped and honestly limited to what we tested.

What’s at risk without it

  • Keyboard traps and missing focus
  • Controls with no accessible name
  • Contrast and text that fails the criteria you claim
  • Dynamic content that never reaches assistive tech
  • A procurement question you cannot answer with evidence

What we test

  • Keyboard access on in-scope journeys
  • Structure: headings, landmarks, labels, errors
  • Names, roles, and states on custom controls
  • Contrast on the screens in scope (sampled, not every hex in the design system)
  • Basic screen-reader smoke on a named combination (for example NVDA + Chrome, or VoiceOver + Safari) when scoped

We do not claim every WCAG criterion on every page. A useful report says which criteria, which URLs, which date.

UK buyers often arrive on this page for an accessibility audit-style engagement. The UK geo page is accessibility testing services UK. The work is the same; the geography is offshore QA if that is how you want to staff it.

Our approach

  1. Agree the standard (for example WCAG 2.2 AA) and the journey list
  2. Combine automated helpers with manual checks — automation alone is not accessibility testing
  3. Log failures with the criterion, the URL, and how to reproduce
  4. Re-test fixes on the same journeys

Related: usability testing for task friction that is not a WCAG failure. Functional testing still has to pass or accessibility testing is noise.

Deliverables

  • Findings mapped to success criteria and URLs
  • What was not tested
  • A re-test pass on the items you fix

No invented “score out of 100.” No badge.

Suitable for

Product teams who need evidence on real screens before a launch or a buyer questionnaire — not a poster that says “we are accessible.”

FAQs

Are you a certified accessibility auditor?

We do not sell a personal certification as the product. We test the journeys you name against the criteria you name and report what we found.

Will this make us WCAG conformant?

Only for the pages and criteria in the report, as of the test date. Conformance is a claim you make; we provide evidence, not a stamp.

Do you write a VPAT?

Only if scoped, and only covering what we actually tested. We will not sign a form that implies the whole product was evaluated.

Talk to our QA team

Ready to discuss your testing needs?

Tell us about your product and where quality matters most. We will help you decide the right testing approach.