Closed Katherine-Osos closed 6 months ago
Update on my progress on this ticket:
I've started a draft accessibility plan outline pulling in information I've found in the Google Drive and GitHub repo. I have formulated many questions based on the information I've gathered so far and will be reaching out to the team to help bridge some gaps so we can fill in more of the plan together.
I've also started a draft survey to send out to the team to gather baseline quantitative and qualitative data on everyone's familiarity with Section 508 and the tools included in the PR checklist. I've sent the survey to Katherine and Alysia for feedback and plan on attending Monday's engineering huddle to give an overview of what an accessibility plan is and introduce the survey. This will help us identify what our ideal process should be and identify opportunities for areas of growth with unfamiliar tools.
The accessibility plan is in its nearly finalized state waiting on feedback from a couple open comments. Moving it into the 'In review' status as a result.
The open comments have been resolved and the plan is finalized! I will share it during today's product huddle, but my work for this ticket is complete.
I also linked it in the .gov project onboarding document so folks rolling onto the project can familiarize themselves with it as they're getting set up.
Issue description
An accessibility plan will provide a source-of-truth outlining our team's expectations and processes for incorporating accessibility in the design + development process. Doing the activity of putting together an accessibility plan at this stage of the project provides a way to document existing processes while revisiting them to see if they're working for the team or if adjustments should be made.
Some elements that could go in an accessibility plan include:
Acceptance criteria
Additional context
Links to other issues
Related to: #1707