How to Test a Small-Business Website’s Important Tasks for Accessibility
How can a small business test its most important website tasks for accessibility?
List the customer tasks the website must support. For each task, inspect content and structure, complete it using only a keyboard, review enlarged text and a narrow viewport, exercise forms and errors, and check required media or documents. Record the setup, expected outcome, observed result, exact barrier, evidence, impact, priority, owner, remediation and retest result. Use a competent reviewer for relevant screen-reader testing, and escalate custom controls, complex transactions, uncertain findings or formal conformance claims. The worksheet documents a bounded practical review; it is not certification.
Choose the customer tasks that matter most
Accessible.org recommends WCAG 2.1 AA conformance, or 2.2, together with an accessibility statement containing contact information for support. Use the business’s agreed WCAG Level AA version as the benchmark, then start with customer tasks that directly affect access to services, contact, forms, documents, bookings or transactions.
Sources: ADA Website Compliance Guide: Accessibility and the Law | Accessible.org.
Use a lead-form design guide when selecting form journeys so the scope includes the decisions, fields, validation and submission interactions a customer must complete. For every selected task, list the entry page, all pages and components involved, any third-party service and the expected customer outcome.
Create another task record when a different template, form type, document format or interactive component changes what must be checked; do not imply that one sample represents the whole website.
- Choose tasks with a direct customer outcome.
- Include every page and component needed to finish the journey.
- Use the agreed WCAG benchmark to frame the review.
Run a defined set of manual checks
For each journey, create applicable check rows for content and structure, keyboard operation, enlarged text and a narrow viewport, forms and errors, media and documents, and competent assistive-technology review where relevant. A check row should identify one customer task and one check category so its setup, result, barrier, owner and retest remain connected.
Inspect headings, labels, instructions, link purpose, image alternatives and information that may depend on visual appearance, then record missing or unclear content. Complete the entire task without a mouse and observe whether every required control can be reached and operated, focus is visible and logically ordered, and no component traps the user.
Review enlarged text and a narrow viewport for lost, overlapping or unreachable content, then exercise forms with valid, missing and mistaken information to inspect labels, instructions, messages and recovery. Check required media and documents for usable alternatives, and refer formats or requirements the team cannot assess confidently to a competent reviewer.
Use someone competent with the selected screen reader when that interaction method is relevant; merely opening assistive technology without knowing how it is normally operated is not a reliable assessment. A website validation process provides a related method for defining checks, recording unresolved issues and preventing changes from being approved without review.
For every row, record the method and setup, expected outcome, observed result, exact barrier, affected step and a concise evidence reference such as the page address, component name or screenshot location. Avoid collecting personal information that is not needed to understand or reproduce the barrier.
- Apply the same named check categories to every relevant journey.
- Keep one row per task and check combination.
- Record setup, expected outcome, observed result and evidence.
Prioritise barriers and apply the specialist stop conditions
The Hanover Insurance Group recommends evaluating a website’s current accessibility state and determining what can be done to increase accessibility and bring it into compliance. Use that current-state review to prioritise barriers that prevent completion of an important task while retaining lower-priority or deferred barriers in the same visible backlog.
Use a website task-allocation guide to decide whether remediation belongs with internal staff, a supplier, automation or a technical care provider. Record the affected task and step, customer or business impact, priority, responsible owner, proposed remediation, decision status and target review point for every barrier.
Stop the internal review and obtain qualified accessibility help for custom interactive controls, complex authentication or payment flows, uncertain findings, unfamiliar media or document requirements, or assistive-technology checks the team cannot perform competently. A formal conformance claim requires a suitably qualified criterion-by-criterion assessment, while a specific legal complaint or dispute requires appropriate legal advice.
- Address blockers in important journeys first.
- Keep deferred barriers visible.
- Escalate checks and decisions beyond internal competence.
Retest fixes and schedule another review
Retest a completed fix by repeating the original check on the original customer task and observing whether the barrier is resolved without breaking the surrounding journey. Close an item only after the worksheet records the remediation decision, responsible owner and retest result; a code or content change alone is not a completed customer-task check.
A WordPress staging workflow offers a related method for checking changes before they affect the live website. Repeat relevant reviews when material templates, navigation, forms, documents, customer journeys or third-party components change.
Keep unresolved and deferred rows visible with an owner and review point, and use recurring barriers to decide where a broader specialist assessment is warranted.
- Repeat the same check after remediation.
- Check adjacent steps for regression.
- Record the result before closing the item.
Task-based accessibility test and remediation worksheet
Create one row for each applicable check on each important customer task. Name the task, its scope and the check category; record the setup and expected outcome; capture the result and evidence; describe any barrier and its impact; then assign ownership, remediation and retesting.
| Task, scope and check | Setup and expected outcome | Observed result and evidence | Barrier, impact and priority | Owner, decision and retest |
|---|---|---|---|---|
| Find a service and contact the business; service page, navigation, contact form and supplied form service; keyboard operation | Browser and input method; customer should reach the service information, operate every required control and submit an enquiry without a mouse | Observed result, affected step, page or component, keys used and screenshot or page reference | Exact barrier, customer or business impact and priority | Named owner, remediation decision, status, target review point and later retest result |
| Submit the contact form; contact form and confirmation step; forms and errors | Valid, missing and mistaken input; labels, instructions, messages and recovery should make the outcome understandable | Observed submission or error behaviour, affected field or step, message and evidence reference | Exact barrier, customer or business impact and priority | Named owner, remediation decision, status, target review point and later retest result |
| Access a key document; document page, download control, document and external host; media and documents | Document format and required use; customer should locate, open and use the information or its available alternative | Observed result, affected page or document element and evidence reference | Exact barrier, customer or business impact and priority | Named owner, remediation decision, status, target review point and later retest result |
Use the named check categories below for each relevant journey: content and structure, keyboard operation, enlarged text and narrow viewport, forms and errors, media and documents, and competent assistive-technology review where relevant. Escalate custom controls, complex transactions, uncertainty and formal conformance claims. This worksheet is not certification or legal advice.
When this is not the right approach: Do not use this worksheet as a substitute for a formal conformance assessment or specialist evaluation when the website, customer risk or technical environment exceeds the team’s competence. It is not a legal opinion or certification method.
Related guidance
What follow-up questions matter most?
- Which website tasks should I test first?
- Start with tasks that directly affect a customer’s ability to obtain information, contact the business, submit a form, access a document, make a booking or complete a transaction. Include every page, component and third-party service needed to finish the task.
- Which accessibility checks should I perform on each task?
- Inspect content and structure, complete the journey using only a keyboard, review it with enlarged text and a narrow viewport, exercise valid and invalid form submissions, and check any media or documents required by the task. Use a competent reviewer for relevant screen-reader testing.
- What should an accessibility testing worksheet record?
- Record the task scope, check method and setup, expected outcome, observed result, exact barrier, affected step, evidence reference, impact, priority, owner, remediation decision and retest result. The worksheet groups these fields into five columns while keeping one row per task and check.
- How should I prioritise accessibility barriers?
- Give first attention to barriers that stop a customer completing an important task, then retain other identified barriers in a visible backlog. Deferral is a prioritisation decision, not evidence that the barrier has been resolved.
- When should a small business use an accessibility specialist?
- Use a qualified accessibility specialist for custom interactive controls, complex authentication or payment journeys, uncertain results, screen-reader testing beyond the team’s competence and any formal conformance claim. Seek appropriate legal advice for a specific complaint or dispute.
What steps does this workflow follow?
How to run a task-based accessibility check
- List important tasks: Choose the customer journeys the website must support and identify every page, form, document, component and third-party service involved in each one.
- Create the check rows: Create a separate worksheet row for every applicable check on each task: content and structure, keyboard operation, enlarged text and narrow viewport, forms and errors, media and documents, and competent assistive-technology testing where relevant.
- Define the expected outcome: Record the check method and setup, the customer outcome and the behaviour expected from the page or component before performing the check.
- Perform and observe the check: Run the named check through the complete task, then record the observed result, exact barrier, affected step and concise evidence reference.
- Assess and assign the barrier: Record the impact, priority, owner and remediation decision while keeping deferred items visible in the worksheet.
- Apply the specialist stop conditions: Escalate custom controls, complex transactions, uncertain findings, assistive-technology checks beyond team competence and any intended formal conformance claim.
- Retest the repair: Repeat the same check on the original task after remediation, inspect adjacent steps and record the retest result before closing the item.