Accessibility Statement

Accessibility StatementFor this site, held to the standard we sell.

Our WCAG 2.2 AA conformance status for qatechxperts.com, how we test it, the gaps we know about, and how to tell us about one we have missed.

WCAG 2.2 AA target Tested every release Gaps published

Our conformance status

This site aims to conform to WCAG 2.2 Level AA. We believe it substantially conforms, with the known exceptions listed below.

This site aims to conform to WCAG 2.2 Level AA. We believe it substantially conforms, with the known exceptions listed below. We say 'substantially' rather than 'fully' deliberately: full conformance is a claim about every element on every page in every state, and the honest position is that we test comprehensively and continuously rather than that we have certified the result.

We sell accessibility Testing. Publishing a statement we cannot support would be the fastest way to lose the right to sell it.

How we test it, and how often

Two automated suites run against the built site before every release, and both block the release if they fail.

Two automated suites run against the built site before every release, and both block the release if they fail.

The first runs axe-core across fifteen representative routes against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets. It currently reports zero blocking violations. The second measures colour contrast from rendered pixels rather than from declared CSS, across twenty targets covering body copy, muted text, links, code panels and text over gradients — because automated contrast checking reads declared values and cannot resolve backdrop filters, stacked transparency or gradient text.

Automated tooling catches roughly a third of accessibility defects, which is why the Manual checks matter more: keyboard-only traversal of the primary journeys, screen-reader passes on the navigation and forms, and a check that every interactive target meets the 24-by-24-pixel minimum introduced in WCAG 2.2.

Known limitations

Animated headings. Several headings render one word per element so they can animate in. Those carry an aria-label with the clean sentence and the animated fragments are hidden from assistive technology, but the underlying markup is more complex than it would otherwise be.

Motion. The site uses entrance animation throughout. All of it respects prefers-reduced-motion; if you have that set at the operating-system level, the animation does not run.

Long-form sections on small screens. Narrative sections collapse into accordions below 768px. They are native <details> elements, so they work without JavaScript and are keyboard-operable, but the full text is present in the page for anyone reading with a screen reader regardless of the open state.

Third-party embeds. Where a scheduling or chat widget is embedded, its internal accessibility is outside our control. We are responsible for how it is labelled and reachable, not for its internals.

Colour-contrast tooling disagreement. Automated scanners flag our gradient headings as failing contrast because such text is technically transparent with a painted background. Measured against the actual rendered pixels those headings pass comfortably. We have chosen to keep the gradient and document the discrepancy rather than let a tool dictate a design decision it is misreading.

Reporting a barrier

If something on this site is difficult or impossible to use, tell us at info@qatechxperts.com.

If something on this site is difficult or impossible to use, tell us at info@qatechxperts.com. Describe the page and what happened; you do not need to know the standard or name the rule.

An Engineer reads it, not a support queue. We aim to respond within one business day, the same commitment we make on every other enquiry, and we will tell you honestly whether it is something we can fix quickly or something that needs a larger change.

Questions

Frequently Asked Questions

Straight answers, written the way we'd say them on a call.

Still curious? Talk to us

Start with a conversation

Need an Accessibility Audit of Your Own Product?

WCAG 2.2 AA against real assistive technology, with a prioritised remediation report rather than a scanner dump.

  • A Senior Engineer replies, not a sales layer
  • Within one business day, every time
  • NDA available before you share any details

16+

Years QA leadership

16

Testing disciplines

6

Markets served

1

Business day to reply

Tell us where quality hurts

Prefer to talk? Book a 30-minute call