Charity sites carry more responsibility than most. People arrive with urgency, stress, or limited time. The site has to work for keyboard users, screen reader users, and everyone on slower devices Source 1 .
What we focus on
- Donate journeys. Forms, validation, payment handover, confirmation.
- Volunteer journeys. Long forms, attachments, and error handling.
- Adoption or referral journeys. Filters, listings, detail pages, and contact.
- Getting help. Contact routes, opening times, locations, and emergencies.
- Content access. Headings, reading order, contrast, and navigation.
What the audit includes
- Automated checks for common failures, then manual verification Source 2 .
- Keyboard testing for every key journey Source 1 .
- Screen reader spot checks on key templates and forms Source 2 .
- Mobile checks for tap targets, zoom, layout stability, and readability.
- Content checks for clarity, headings, and predictable structure.
What you get
- A prioritised list, ordered by user impact Source 3 .
- Evidence per issue, with steps to reproduce.
- Fix guidance written for developers and non-technical stakeholders.
- Optional fix work and retesting.
- Optional support for an accessibility statement and ongoing checks Source 4 .
Fix support
Audit only suits teams with development support in place. Audit plus fixes suits teams who want the work delivered end to end.
- Audit only. Report and priority list for your team.
- Audit plus fixes. Fix work scoped and delivered, then retested.
- Ongoing. Regular checks and small fixes to stop drift.
FAQs
What standards do you audit against?
Audits target WCAG 2.2 AA as the baseline. The report maps issues to criteria and explains impact in plain English.
Do you fix issues or only report them?
Both routes work. You get a clear priority list first. Fixes follow either on your side, my side, or shared.
What do you need from us?
A short list of key journeys, key pages, plus access details for any gated areas. If you use analytics or Search Console, read access helps prioritise.
How long does an audit take?
Most audits take days, not weeks. Timing depends on page count, journeys, and the level of manual testing.
Prefer the standard accessibility service page?
Same approach. More options and tiers.
Not sure where to start?
Get a free score and 3 priority fixes.
Sources
- [1] W3C. Web Content Accessibility Guidelines (WCAG) 2.2. Back to article
- [2] W3C WAI. Evaluating Web Accessibility Overview. Back to article
- [3] W3C. Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0. Back to article
- [4] GOV.UK. Make your website or app accessible and publish an accessibility statement. Back to article