Note · 4 min read
For charity websites, accessibility is the mission
If someone cannot request support, a welcoming homepage has not done its job. Start with the task that connects people to the service.
In this note
A charity website may be where someone asks for support, checks eligibility, volunteers or makes a donation. If the required form cannot be completed with a keyboard, the service has a barrier at its front door. A welcoming mission statement does not remove it.
That makes accessibility an operational question as well as a design one. Which tasks must people be able to complete? What happens when a task fails? Who receives an access request, and can they act on it? Begin there, with the people your charity serves, rather than guessing their needs from a demographic label.
The gap between values and markup
A page can read as inclusive and still contain barriers that a screenshot will not reveal. W3C's introductory accessibility checks cover areas such as headings, contrast, keyboard access, forms and media. Use them to begin a review, then investigate the relevant interactions:
- Do links and icon buttons have names that explain their action?
- Do image alternatives convey meaning without announcing decorative clutter?
- Does the heading structure describe the page's sections?
- Does text meet the relevant contrast requirement?
- Can people pause moving content where required?
- Do form fields have persistent labels and errors that explain the correction?
- Are captions and other media alternatives available where needed?
Record what was tested and what happened. An unlabelled control needs a specific repair; a suspected screen-reader problem needs a test. The cost of either depends on the implementation, so estimate it with the person who will do the work.
Make the review boundary explicit
“Accessibility included” is too vague to accept. Name the pages, complete journeys, account states, documents and third-party steps in scope. Agree the WCAG version and conformance level, test methods, and how findings will be reported. Ask what will remain untested.
W3C recommends using the latest version of WCAG, currently 2.2. An existing review scoped to WCAG 2.1 AA should say so; it does not establish coverage of the additional 2.2 criteria. A review of selected pages also cannot establish conformance across the whole site.
Why it slips, even on new sites
A rebuild can change the appearance while preserving the same barriers. That happens when the brief names inclusion as a value but never defines what the team must demonstrate. Assign acceptance checks to real tasks: completing an enquiry, choosing a donation amount, recovering from an error.
Combine automated checks with manual evaluation by people who know the relevant methods. Involve disabled people in research and testing where possible, with suitable support and compensation. Keep usability findings alongside technical failures; a technically conforming interaction may still need work to serve its audience well.
Where to start with limited time
Choose a complete journey, from its entry page to its confirmation or recovery state. Work through it with the keyboard, look for visible focus, and check labels and errors. Run an automated scan as another source of findings. Evaluation tools cannot determine accessibility on their own; a clean scan leaves manual checks to do.
Prioritise barriers to obtaining support, completing required steps and recovering from failure. Show severity and repair effort separately so a difficult fix is not quietly treated as unimportant. Publish a usable contact route for access problems, give it an owner, and track unresolved barriers after the first review.
Ask about a review
Our fixed-fee UX audit includes a WCAG 2.1 AA review within an agreed scope. Registered charities in Wales can ask about a pro-bono review; availability is confirmed after enquiry and requires permission to publish the audit as a case study. There is no obligation to hire us for the repairs. Send us the URL and tell us which service journey needs attention.
Have a product decision to make?
Tell us what needs deciding and what constrains it. We can discuss whether definition, a build or a reset fits.