WCAG 2.2 AA audit
Review with axe, Lighthouse and manual testing, with each issue linked to the WCAG criterion it fails.
Services
Web accessibility following WCAG 2.2 AA
Markish Tech audits and fixes websites and web applications so people with visual, motor, hearing or cognitive disabilities can use them, following WCAG 2.2 level AA. We combine automated tools such as axe and Lighthouse with manual keyboard, zoom and screen reader testing, because a perfect automated score doesn't guarantee an accessible site.
Problems it solves
- Low-contrast text, or text that gets cut off when zooming in.
- Menus, modals or forms that can't be used with a keyboard alone.
- Buttons and icons without an accessible name that a screen reader can't announce.
- Form errors indicated only by color.
Who it's for
- Organizations that want everyone to be able to use their site.
- Companies that must meet accessibility requirements in tenders or contracts.
- Digital products that don't want to lose users to usability barriers.
- Teams who already built a site and need an expert review.
What's included
Code fixes
Semantic HTML, ARIA roles and states only where needed, accessible names and a logical focus order.
Keyboard and focus
Visible focus, skip links, menus and dialogs that trap and return focus correctly.
Contrast and themes
Contrast checks in light and dark themes and support for high contrast mode.
Forms
Real labels, descriptive errors tied to each field and announced status messages.
Motion and zoom
Respect for the reduced motion preference and layouts that work at 200% and 400% zoom.
How we implement it
Scoping
We pick representative pages and flows (home, forms, navigation, content).
Automated testing
axe-core and Lighthouse on every template and in both themes.
Manual testing
Full keyboard navigation, zoom, reflow at 320 px and screen reader checks.
Fixes
We implement the changes or document them for your team.
Regression
We leave automated tests so accessibility doesn't break with the next change.
Technologies
When it makes sense
- You want to reach everyone, including people who use assistive technology.
- You have critical forms or processes (contact, checkout, sign-up).
- You need to prove compliance with evidence.
When it doesn't
- You're looking for a one-script automatic fix that promises full accessibility: it doesn't exist.
- There's no way to change the site's code or content.
Frequently asked questions
What is WCAG 2.2 AA?
WCAG (Web Content Accessibility Guidelines) is the W3C's international web accessibility standard. Version 2.2 was published in 2023 and level AA is what regulations and contracts usually require: minimum contrast, keyboard use, visible focus, text alternatives and understandable forms, among other criteria.
Does a Lighthouse accessibility score of 100 mean the site is accessible?
No. Automated tools only catch part of the problems. Things like a logical focus order, whether alt text actually describes the image or whether a flow makes sense with a screen reader need manual testing.
Do accessibility overlay widgets work?
Generally they don't fix the underlying problems, which live in the HTML and the design, and they sometimes interfere with the assistive technology people already use. We recommend fixing the code.
Want to know if this service fits your case?
Tell us what you need and we'll reply with an initial proposal and next steps.