Loading lesson…
Prototype contrast, keyboard flow, labels, responsive width, and reduced motion early so accessibility is not a cleanup chore. Write the smallest useful scope the agent can finish.
Prototype contrast, keyboard flow, labels, responsive width, and reduced motion early so accessibility is not a cleanup chore.
Audit the prototype for contrast, focus states, keyboard path, text overflow at 320px, and motion reduction. Return fixes as design requirements.Use this as the working prompt or checklist for the lesson.15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-design-accessibility-creators
What does the principle 'name the job before naming the tool' mean when working with AI agents?
Why should accessibility features be included during the prototype phase rather than added later?
Which accessibility consideration involves ensuring users can navigate without a mouse?
What is the main reason to write the 'smallest useful scope' when working with an AI agent?
What does it mean to 'run the result as a user, not as a fan of the tool'?
Before sharing an AI-generated prototype, what three things should you inspect?
When prototyping with AI, what question should you ask about data?
What does 'observable' mean in the context of making AI prototypes safe for others to use?
What does 'reversible' mean when evaluating AI-generated outputs?
Why is testing the 'failure path' important when prototyping with AI?
Why is reduced motion an important accessibility consideration to address early?
What does 'responsive width' mean in the context of accessibility?
What is 'keyboard flow' in accessibility?
Why is contrast important to address in early prototypes?
What should a rollback path provide in an AI-assisted project?