USWDS-Site - Accessibility tests: Publish Prose checklist page

[mahoneycm]

Summary

Created Prose accessibility checklist following the provided guidance (🔒)

Important

We should update the changelog dates before merge.

Note

We don't currently provide guidance on how to adjust text spacing. Until we do, we've opted to remove item 1.4.12 from the site testing checklist and rely on 1.4.4 to cover this test.
Additional information can be found in this comment thread

Related issue

Closes #2531

Preview link

Prose component page →

Prose accessibility checklist →

Major changes

• Prose accessibility page published.
• Prose sidenav updated.
• Accessibility section added to Prose component page add testing alert.
• WCAG details created for 3.1.5 AAA criterion

Accessibility guidance section

I added a comment to the usa-prose/guidance/accessibility.md file so that it doesn’t render as null and it properly adds the testing alert.

Is this a pattern we want to follow for pages without other accessibility guidance?

Testing and review

1. Confirm links to testing page work and follow the correct path pattern
2. Confirm content in checklist matches critical checklist spreadsheet
   • The item for text-spacing had content as it's test type. Confirm using general is appropriate here
3. Confirm WCAG links take users to correct WCAG criterion
4. Confirm accessibility checklist markdown follows existing pattern
5. Confirm we want the newly generated accessibility guidance section on the component page without any additional accessibility guidance

[amyleadem]

Looking good! I had some questions and comments below. Let me know if you have an questions.

[sarah-sch]

The page looks good to me.

[amycole501]

The page reads well, I didn't find any errors or issues. Looks good!

[amyleadem]

Looks good to me! I confirmed the following:

• Confirm that both the main component page and the accessibility tests page have the correct compliance tag at the top.
• Confirm that the main component page links to the accessibility tests page in the side navigation.
• Check that accessibility tests page provides the correct counts for each test status type.
• Confirm the test checklist summaries and data are accurate.
• Confirm there is an appropriate changelog entry on both the main component page and the accessibility tests page.
• Confirm the note in the accessibility guidance section of the main component page uses the correct component name

[mejiaj]

Pages good, aside from changelog dates.

[thisisdano]

Updating changelog dates...

[thisisdano]

Merging over pa11y crashes