Skip to content

Instantly share code, notes, and snippets.

@SteveBarnett

SteveBarnett/Accessibility-OKRs.md

Created June 14, 2023 23:20
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save SteveBarnett/09aa2aa3a661779d07af3ab5605241bd to your computer and use it in GitHub Desktop.
Save SteveBarnett/09aa2aa3a661779d07af3ab5605241bd to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Accessibility-OKRs.md

Accessibility OKRs

Process

  • Every design change or new item has been reviewed using the UX a11y summary.
  • Every code change or new component is "axe clean" (no errors when running the axe browser extension)
  • Updating the ACR is part of the release cycle (maybe as part of the changelog process?)
  • Create, gather, and report on metrics (have a dashboard?).
  • Write some new behat tests that cover keyboard usage, aria attributes, and more. (Note! Writing and running behat is slow and jest is fast. But! Behat tests the rendered HTML directly and is framework-independent.)
  • No tickets with WCAGFail label by [date]

Outreach

  • Write [number] Medium posts on accessibility.
  • Present on a11y at [number] events.
  • Create Global Accessibility Awareness Day campaign every year (Third Thursday of May)

Internal upskilling

  • Train [number] new individuals on WCAG 2.1 update before [date]
  • Establish rewards for improving accessibility for designers and developers
  • Create formal training program
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment