Summary: Define and document clear accessibility goals and OKRs to align your team and leadership and ensure accessibility work gets prioritized.
Google’s committment
Accessibility is now included in our company-wide Google OKRs. It’s a good idea to review this OKR with your team:
Objective 6Build a Google that's extraordinary for Googlers and the world |
Key Result 1Advance product inclusion, equity, and accessibility with 40% of 1B+ MAU products using the Google Equity Rating (GER), and 100% of 25M+ MAU products achieving Google Accessibility Rating (GAR) 4 requirements. If a product meets or exceeds 90% of GAR 4 requirements, an Accessibility Usability Evaluation (AGUA) will be conducted and the product team will resolve 100% of identified AGUA issues. |
Set OKRs at a team level
You should also set accessibility OKRs at an organizational and team level. Here are some examples of OKRs you can set with your team:
- GAR2 for all dogfood launches
- GAR4 for all feature/product launches by [date]
- Implement an accessibility bit in Ariane to prevent accessibility regressions
- Establish expectations and responsibilities by role and dedicated allocation needs to execute accessibility work by [date]
- Define process for GAR testing at scale (e.g. outsource, train QA) by [date]
- Get top five Critical User Journeys (CUJs) to “healthy status” for four accessibility user groups by [date].
- Complete the Alphabet Accessibility Academy’s Foundational Accessibility Knowledge Certificate (FAKC) training program by 100% leadership by [date]
- Increase product compliance