How it works
Six steps, from your first message to a documented result. You decide what we look at and what we change.
Step 1: You request help
Submitting the form does not start any scan. It only tells us you are interested. We reply by email to talk through what you need.
Step 2: We confirm permission and scope
We record who approved the review, which pages are included and whether we may suggest or make changes. We never test a site without this record.
Step 3: We evaluate the agreed pages
Automated tools catch only part of what matters, so a person also checks keyboard use, focus, alt text, forms, reading order and zoom. Up to five pages per organization to start.
Step 4: We explain what we found
Each finding lists the page, the element, the WCAG reference, who it affects and how to fix it. You can download it as a PDF or a spreadsheet.
Step 5: We help you fix it
We write fix guides for WordPress, Wix, Squarespace and custom sites. We only change your site if you give explicit permission, and we keep a change log with rollback steps.
Step 6: We check the result
A barrier counts as resolved only when a person confirms the fix. A later scan that no longer detects it is noted, but is not enough on its own.
What automated testing can and cannot do
The Curb Cut Project uses axe-core, an open-source testing engine, against WCAG 2.2 Level AA. Each finding in a report names the rule that produced it and the WCAG success criteria that rule maps to. Rules axe-core cannot decide on its own are listed separately as needing human review.
Automated tests cannot judge whether alt text is meaningful, whether the reading order makes sense, or whether a form is usable with a screen reader. A person checks those. A report is not a complete audit and is not a legal compliance certification.