cds-snc / notification-planning

Project planning for GC Notify Team
5 stars 0 forks source link

Triage OCADU a11y audit #1385

Closed amazingphilippe closed 8 months ago

amazingphilippe commented 11 months ago

Description

As a Notify contributor, I need to be able to pick up detailed a11y issues so that I can fix them.

WHY are we building? We got back a detailed a11y audit

WHAT are we building? Making sure the issues are part of our backlog, documented, refined, and ready to pick up at any time.

VALUE created by our solution Continuously improving a11y is easy.

Documentation and Artifacts

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

yaelberger-commits commented 11 months ago

Hey team! Please add your planning poker estimate with Zenhub @adriannelee @amazingphilippe

yaelberger-commits commented 11 months ago

Please add your planning poker estimate with Zenhub @andrewleith

amazingphilippe commented 10 months ago

Audit is ready to review: https://docs.google.com/document/d/1XKh6TMGYFcHMM_iL4DyUs4j67MsJjQOP/edit

adriannelee commented 10 months ago

Up for dev-design review today.

adriannelee commented 9 months ago

Phil is working on this today.

amazingphilippe commented 9 months ago

Linking a11y issues with current stories done. Looking over issues that were less clear, and questions we had so far during the audit playback, we could meetup with OCADU and know more about:

Moving this to "review" so that we can brainstorm other topics and book some time with OCADU

amazingphilippe commented 8 months ago

Andrew and Phil will meet with OCADU and discuss techniques and strategy for a11y. Should happen on the week of February 5.

amazingphilippe commented 8 months ago

Notes from OCADU follow up sync: https://docs.google.com/document/d/1QiG9MuM_GVQVISu5Ge8PmP8KyS2eJ4YTEHSvX_JHbFM/edit