An accessible site means that people with visual, hearing, motor or cognitive disabilities can also find information, fill in forms and buy. We audit your site against WCAG 2.2 AA with an automated scan and manual testing, report the findings by severity, fix them in the code and retest. In Türkiye Circular 2025/10, and in Europe the European Accessibility Act, have made this mandatory for many organisations and businesses.
Automated tools find only some of the problems. We test each page type by hand using only the keyboard, with screen readers such as NVDA and VoiceOver, at 200% zoom and with colour contrast measurements; forms and the checkout step are tested separately.
For each finding we record the WCAG criterion, the affected page and element, a screenshot, who is affected and how, and how to fix it. Problems that stop users from completing a task, such as a form that cannot be submitted or a menu that cannot be opened with the keyboard, come first.
Our own development team makes the fixes in the theme and the code; we do not recommend accessibility overlays. We then retest and prepare the accessibility statement for your site: the conformance status, known limitations and a feedback channel.
The scan shows where to look, manual testing proves the problem; the fix is made in the code and confirmed by a retest.
We clarify the scope, deliverables and acceptance criteria together in the first meeting. The written quote lists that scope item by item; if the scope changes, the quote is updated as a new version.
Each step ends with something concrete in your hands; we move on with your approval.
We scan all page types with automated tools and map where the problems concentrate.
We test each page type with the keyboard, a screen reader, zoom and colour contrast checks, and record the findings with screenshots.
We fix the findings in order of severity in the theme and the code; for problems that come from content, such as alt texts, we give your team guidelines.
We retest the fixes and write the result and any known limitations into the accessibility statement.
What is included, what we need from you, timing and payment, all in one place. The exact scope and price are set in the written quote.
Tell us what you need; we will define the scope together.
Tell us about your projectNo. An audit records the state of the tested pages on that day; the result can change as new pages, content or features are added. Official monitoring and enforcement are the job of the relevant authorities. We document the scope we tested, the findings and the fixes we made in a report.
No. Toolbars added on top of a page offer settings such as text size or colours, but they do not fix the problems in the source code: an unlabelled field, a nameless button or a menu that cannot be opened with the keyboard stays as it is. WCAG conformance is achieved in the page itself, which is why we fix the problems in the code.
We pick representative samples of each page type: the home page, a product or service page, listings and search, forms and the checkout step. Pages built from the same template usually share the same problems, so fixing the template fixes all of them. The list of pages is agreed together in the scoping call.
Tell us what you need; we will define the scope together.