# Link and button label worksheet

Good Work Atlas · Worksheet version 2026-09-07
Guide: https://goodworkatlas.com/guides/review-a-link-or-button-label
Resource Atlas: https://goodworkatlas.com/tools/resource-atlas

An original content-review aid prepared with AI-assisted drafting. This file does not inspect a site or certify accessibility. Use appropriate sample data and remove private information before sharing a completed copy.

## 1. Record

- Page and component:
- Version or date of page reviewed:
- Review date:
- Page state and starting conditions:
- Reader's task:
- Browser and any assistive technology actually used:

## 2. Promise

- Expected destination or action:
- Immediate result:
- Work that remains pending:
- Actual behavior checked, or not checked:
- Does the exposed role fit the action? Observation and any follow-up:

## 3. Visible wording

- Exact visible text:
- Icon or image meaning, if present:
- Surrounding explanation:
- Screenshot or other evidence reference:

## 4. Programmatic wording

- Exposed role:
- Computed accessible name:
- Description, kept separate from the name:
- How the role/name/description were checked:
- Does the name include the visible text, where that criterion applies?
- Any field not checked and why:

## 5. Context and alternatives

- Destination URL, for a link:
- Sentence, list item, or other context relied on:
- How the association was established:
- Similar or repeated controls and their destinations/actions:
- Can the reader distinguish the choices? Observation or open question:

## 6. Proposed change

- Existing wording:
- Proposed visible wording:
- Proposed accessible name:
- Reason for the change:
- Required behavior or markup repairs, if any:
- Questions to validate with readers:

## 7. Verification and follow-through

- Original task repeated:
- Observed result and evidence:
- Updated computed name checked:
- Other states or layouts checked:
- Remaining unchecked behavior:
- Follow-up owner or issue:
- Decision and review date:

## Fictional example — no actual test results

- Page: an invented schedule editor.
- Reader task: keep a draft without sending it.
- Promise in the fictional design: Save stores the draft; Send delivers the schedule to a sample team.
- Initial visible label: Save.
- Initial accessible name: Store schedule.
- Nearby action: Send.
- Proposed visible label and accessible name: Save draft.
- Separate proposed label for the other action: Send schedule.
- Reason: distinguish the two actions and include the visible wording in the accessible name.
- Behavior checked: Not checked. The example supplies no test evidence.
- Next verification: examine the implemented role and computed name, repeat saving with fictional data in a test environment, and record the actual outcome. Review sending separately.
- Status: proposal only; no successful test or improvement in measured usability is claimed.

## Primary references

- Button pattern: https://www.w3.org/WAI/ARIA/apg/patterns/button/
- Link pattern: https://www.w3.org/WAI/ARIA/apg/patterns/link/
- Link purpose in context: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html
- Names and descriptions: https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/
- Label in name: https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html
- Headings and labels: https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html

## Use and privacy

Reuse permissions and resource limitations: https://goodworkatlas.com/terms

How the publication handles website visits and tool inputs: https://goodworkatlas.com/privacy