PRDs and planning
Summary: Ensure that Product and Program Managers prioritize and account for
accessibility in scoping and planning of the work to set the team up for success
later.
Consider accessibility in scoping
- Learn about the GAR process at go/gar
- Document clear accessibility requirements, use cases, edge cases, and OKRs
- Bake time for accessibility work into UX and Eng schedules
- Document an accessibility plan and points of contact within the team
- Include an accessibility section in the PRD
Additional resources
description
Accessibility PRD
Visit go/new-a11y-prd, a template created by Googler,
Lane Kuhlman, to help your team define how you will account for
accessibility in your product.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-04-03 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-04-03 UTC."],[],[]]