The playbook
Web Accessibility: Template and Field Guide
This web accessibility template turns a broad task into a record another person can use. It captures component, barrier, test, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
A visible field label, a specific error message, and a clearly visible keyboard focus can materially improve a form journey. Check the order of focus and whether controls have understandable names. Automated testing can identify some issues but does not replace trying the task.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| component | Record the component associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| barrier | Record the barrier associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| test | Record the test associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| repair | Record the repair associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with component. Use the same reference throughout the record so notes are not attached to the wrong item. Then check keyboard access focus and meaningful labels. This establishes the information required before the worksheet becomes a request for action.
Next, provide text alternatives and readable contrast. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as assuming an automated score proves every interaction is accessible, rather than a broad instruction to “improve performance.”
Finally, test forms errors and complete user journeys. Put combine automated checks with manual keyboard and assistive-technology testing in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Assuming an automated score proves every interaction is accessible |
| Action | Combine automated checks with manual keyboard and assistive-technology testing |
| First check | Check keyboard access focus and meaningful labels |
| Follow-up check | Test forms errors and complete user journeys |
| Outcome to define | resolved barriers in critical journeys |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If barrier changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep resolved barriers in critical journeys connected to the item so the team can later assess whether the action was useful.
Treat visual changes and functional changes separately in the change log. A clearer label may improve comprehension, but a broken submission destination still prevents completion. Confirm both understanding and successful delivery.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now