WCAG Accessibility
Accessibility work that audits web products against WCAG AA criteria, identifies usage barriers, and fixes them.
- WCAG AA Audit
- Screen Reader Support
- Keyboard Navigation
- Remediation & Verification Report
Click a screen to enlarge it; you can also hide the annotations and see just the photo.
An interface can be "working" and still be closed off to a large group of users: people who can't use a mouse, can't see the screen, can't tell a low-contrast button apart, or can't follow a complicated form flow. This isn't a small edge case — it's a broad group of people who use digital products every day with a visual, hearing, motor, or cognitive limitation.
We don't treat accessibility as a "compliance item" bolted on at the end of a project; we treat it as the first criterion in research, content, and interface decisions. This approach meets legal and enterprise expectations while also reaching a wider audience with fewer errors — because an interface that's keyboard-navigable, clearly labeled, and predictable is already a more usable interface for everyone.
What is WCAG?
WCAG (Web Content Accessibility Guidelines) is a guideline set published by the W3C and used worldwide as the reference standard for digital accessibility. Rather than a software standard, it's a set of concrete, testable answers to the question "who should be able to use an interface, and under what conditions."
Four principles: Perceivable, Operable, Understandable, Robust
Every WCAG rule rests on four core principles: content must be Perceivable (a visual cue can't rely on color alone — it needs alt text or structure too), Operable (every function must be reachable by keyboard, not just mouse), Understandable (form errors must be explained clearly, navigation must stay consistent), and Robust (it must work with assistive technologies like screen readers, using properly marked-up structure).
Conformance levels: A, AA, AAA
WCAG defines three conformance levels. A is the minimum and isn't considered sufficient on its own. AA is the level public institutions and most corporate regulations reference, and the level practically targeted. AAA is the highest level; since it isn't realistic to fully meet for some content types, it's usually targeted for specific criteria rather than imposed as a mandatory condition site-wide. AA is the core target in our audits.
Why now?
Accessibility is no longer a concern only for public institutions; public tenders, corporate procurement processes, and growing user expectations are making accessibility an increasingly decisive criterion in the private sector too. An accessible product also reaches a wider audience and generally produces fewer usage errors — because a clearly labeled, predictable interface is easier for everyone to understand.
Our audit process
The process moves through five steps: (1) automated scanning with the Accessibility Audit Bot — quickly catches detectable errors like missing alt text, low contrast, and unlabeled form fields; (2) manual keyboard-only navigation testing; (3) manual testing with a real screen reader; (4) a prioritized findings report with remediation recommendations; (5) a verification pass after fixes. Since automated scanning only catches a portion of the errors, steps 2 and 3 are never skipped.
Level A is the minimum, while AAA is the highest level and, for some content types, isn't practically achievable in full. Public institutions and most corporate regulations use AA as their reference; in our audits we also set AA as the target level and get as close to AAA as possible where we can.
