Supplemental Guidance Template

Page Title: Supplemental Guidance: [couple word description]

Summary

[Clear, short statement of what is needed. Somewhat like success criteria wording, except plain language, doesn't need to include all exceptions, etc,]

Important

...boilerplate wording: @@ This is informative. Other than SCs from WCAG, not a requirement...

User Experience

This quote from a persona (fictional person) helps you understand some aspects of this guidance.

Persona: Parent with low vision – 20/400 [Can change this. For examples, see What's New in 2.1]

Problem: "[...]"

Works Well: "[...]"

What To Do

[what designers, developers, others need to do]

Intent

[briefly explain the user experience -- why this is needed]

Benefits

• [how it makes content accessible for people with disabilities]
• [can include additional benefits beyond accessibility (e.g., using phone in bright sunlight)]

Examples

[Examples of barriers. Examples of solutions.]

Support

[how which technologies support it or not]

Related Resources

• [only list here if particularly useful]

Techniques

• [can point to existing WCAG techniques, or list new ones]

Failures

• [can point to existing WCAG failure techniques, or list new ones]

Key Terms

• [only list here if needed. can use WCAG termsor add new one if needed]

Editorial Notes

These notes are not for the published document — just for us working through ideas.

[notes here :-]