What it is
Annotations that document accessibility requirements on designs, heading structure, reading and focus order, alt text, ARIA roles, labels, and states, so engineers implement accessibility correctly from the start.
When to use it
During Prototype and at Implement handoff.
Why (value)
Accessibility is far cheaper and better when designed in; annotations prevent it from being lost between design and code.
How to run it
- Define heading and landmark structure.
- Specify reading and focus order.
- Annotate alt text, labels, and roles.
- Note focus states and keyboard behavior.
- Hand off with the design and verify in build.
Inputs and outputs
- Inputs: Designs and knowledge of WCAG/508 requirements.
- Outputs: Accessibility-annotated designs for handoff.
Time and effort
Low. Incremental with design.
Evidence and limitations
Represents accessibility intent/expert judgment; it is not a substitute for testing with assistive technology and users with disabilities. See Evidence and limitations.
Tips and pitfalls
- Specify focus order and headings explicitly.
- Do not rely on color alone.
- Verify with real assistive-tech testing.
Variations
A11y annotation kits, ARIA specs.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Design annotations — Add notes to designs that explain behavior, logic, and intent for accurate implementation.
- Accessibility evaluation — Assess whether a product can be used by people with disabilities, against standards and with assistive tech.
- Standards compliance review — Check a design against required standards, platform guidelines, and internal policies.
