SPIKE: Measure Outcomes for Drupal CMS Accessibility Backlog Epic - Githubissues

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.

https://prod.cms.va.gov

GNU General Public License v2.0

99 stars 69 forks source link

SPIKE: Measure Outcomes for Drupal CMS Accessibility Backlog Epic #19562

Open gracekretschmer-metrostar opened 3 weeks ago

gracekretschmer-metrostar commented 3 weeks ago

User Story or Problem Statement

As the accessibility specialist, I need to understand the best strategies for measuring success for the accessibility backlog epic.

As the CMS PO, I need to understand the measured progress toward reducing the accessibility debt and backlog for Drupal CMS.

Description or Additional Context

Now that we have created expanded the accessibility backlog for CMS, we want to explore how to we measure success with this work?

https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17936

The 2025 OCTO OKRs will be coming the week of 11/13 and should be taking in consideration.

The accessibility backlog's users impacted is focused on the editor experience.

Steps for Implementation

Acceptance Criteria

[ ] A recommendation on how to measure success with the Drupal CMS Accessibility Backlog.
[ ] A plan of action on how to implement the measurements into Drupal CMS and/or CMS sprint tracking.

gracekretschmer-metrostar commented 3 days ago

As possible steps: another spike to explore how to measure success with the editor support initiative.