Make your business website easier for people with disabilities to use by checking the tasks that matter: finding information, navigating, reading content and completing forms. Start with the existing barriers and test the improvements.
Accessibility should be part of writing, design, development and maintenance. It is not established by adding a badge or running one automated scan.
Start with the important journeys
Choose representative tasks such as finding a service, requesting a quote, reading an admission requirement or completing an application. Include different page types and the steps after submission.
People use websites in different ways, including keyboards, screen readers, magnification and captions. The review should consider how the content and controls work with those methods rather than assuming everyone uses a mouse and sees the same layout.
Use an appropriate assessment framework
W3C‘s Web Content Accessibility Guidelines provide criteria for assessing accessible web content. Its WCAG 2.2 quick reference helps reviewers find the relevant requirements and techniques. Reference: https://www.w3.org/WAI/WCAG22/quickref/.
Agree the assessment scope and intended level with a competent reviewer. A practical improvement checklist can identify barriers, but it is not by itself a declaration that the whole website conforms.
Review the common barriers
| Area | Practical question | Useful check |
|---|---|---|
| Keyboard use | Can people reach and operate controls? | Complete the main task without a mouse |
| Text and layout | Is information readable and structured? | Check contrast, headings and resizing |
| Forms | Are labels and errors understandable? | Test valid and invalid submissions |
| Images | Is important meaning available in text? | Review image purpose and alternatives |
| Media | Can people access spoken information? | Review captions and suitable transcripts |
Make navigation and focus understandable
Check whether keyboard users can move through the page in a sensible order and see which control is active. Menus, dialogs and embedded tools need attention as well as ordinary links.
Use descriptive link and button labels. Several identical “click here” links can be difficult to understand outside their surrounding paragraph. A label such as “View admission requirements” communicates the destination more clearly.
Keep headings in a useful hierarchy so the page’s structure can be understood. Visual size alone is not a substitute for appropriate heading markup.
Write forms people can complete
Give fields visible labels and explain the requested information. Identify required fields clearly and provide errors that tell the visitor what needs correcting.
Do not use colour as the only indication of an error. Check that error information is available to the relevant assistive technology and that focus behaviour helps the visitor continue.
A hypothetical application form might reject a date without explaining its required format. A clearer label, suitable input and specific error message can address that barrier. This example illustrates a review task, not a measured result from a client project.
Review visual content and media
Check text against its background, including buttons, cards and text placed over images. Review enlargement and narrow screens so content remains usable. Avoid requiring visitors to read essential instructions from a decorative image alone.
Write image alternatives according to purpose. An informative image may need a concise description; a purely decorative one may be handled differently. A complex visual may need an explanation in the surrounding content.
For video and audio, plan suitable captions, transcripts and other alternatives according to the material. Check accuracy rather than assuming automatic text is ready to publish.
Combine tools with human review
Automated tools can identify some issues, such as selected markup or contrast problems. They cannot fully determine whether the language is useful, the image description makes sense or a complete application journey is understandable.
Include manual checks and, where possible, feedback from people with relevant access needs. Record the task, barrier and proposed correction so the team can retest it.
- Choose representative pages and tasks.
- Record barriers with reproducible examples.
- Prioritise problems that block essential actions.
- Correct the underlying content or implementation.
- Retest the affected journey.
- Include accessibility in future content and development checks.
Make improvements part of ongoing work
A new plugin, uploaded document or redesigned form can introduce fresh barriers. Give editors guidance and keep review responsibilities in the maintenance process.
My UI/UX and interface planning support, website development and technical care can help scope practical improvements and any specialist assessment needed.
Be precise about claims. State what was reviewed, which framework was used and what remains outside the assessment.
Frequently asked questions
Will an accessibility plugin solve everything?
No. The website’s content, structure and behaviour still need review. Assess the actual user journeys.
Should we wait for a redesign?
Not necessarily. Clear labels, better content and corrections to blocking issues can often be addressed as defined improvements.
Can we claim compliance after a quick check?
Use claims supported by the assessment. A limited checklist or scan should not be presented as a complete conformance review.
Discuss your next step
For help applying this to your organisation, share a short description of your situation and the decision you need to make.





