Components

Prose accessibility tests

Any USWDS prose component should pass these manual accessibility tests.

Passed WCAG 2.1 AA

Prose accessibility status

The USWDS team did 4 tests based on WCAG 2.1 AA success criteria.

Overview of recent accessibility test results:

Total tests	Passed	Passed with exceptions	Conditional	Failed
4	2	0	2	0

Overview of recent accessibility test results:

• Passed: 2
• Passed with exceptions: 0
• Conditional: 2
• Failed: 0

Test the prose in your project

USWDS tests components in isolation. You need to test the prose component in the context of your own site to ensure compliance with Section 508 accessibility standards.

Use the checklist below.

Follow the "how to test" instructions for each type of assistive technology.

Anyone can test for accessibility.

These quick manual tests don't require special equipment.

Prose accessibility checklist

• General tests
• Zoom magnification tests
• Keyboard navigation tests
• Screen reader tests

General tests

Select passing tests

Content is written in plain language. Content is easy to understand. It is written at the appropriate grade level. Complex words are defined by a glossary or other method.

This can only be tested in your implementation of the component. Be sure to test this in your project.

• WCAG AAA
• 3.1.5 Reading level
• USWDS test status: Conditional
• Last test: v3.7.1

• USWDS test status:
  Conditional
• Last test: v3.7.1

Zoom magnification tests

USWDS performed these tests to check prose accessibility and usability for zoom magnification. For help performing your own zoom magnification tests, check out the resources in the expandable section below.

1. Navigate to a page on your website where the prose component is used.
2. Enlarge the view of your screen to 200%.
3. Once zoomed, use a mouse to complete the tests in the checklist.

---

Use one of the following methods to control screen magnification in your browser:

1. Windows OS: Click ctrl while using the scroll wheel on your mouse until you see "200%" appear in the top right of your screen. Or, click ctrl + + until you see "200%" appear in the top right of your screen. (To reset the zoom to the original value, click ctrl + 0.)
2. Mac OS: Click command + + until you see "200%" appear in the top right of your screen. (To reset the zoom to the original value, click command + 0.)
3. Browser settings: Customize your browser settings to display pages at 200%.

Select passing tests

Text retains functionality when screen is magnified. When you zoom in to 200%, text and tables with text retain all of their functionality.

• WCAG AA
• 1.4.4 Resize text
• USWDS test status: Passed
• Last test: v3.7.1

• USWDS test status:
  Passed
• Last test: v3.7.1

Keyboard navigation tests

USWDS performed these tests to check prose accessibility and usability for keyboard navigation. For help performing your own keyboard navigation tests, check out the resources in the expandable section below.

1. Navigate to a page on your website where the prose component is used.
2. Using only your keyboard, press tab to navigate forward or shift + tab to navigate backwards until focus is on the prose.
3. Use the testing checklist to make sure all functionality works with keyboard navigation.

---

For instruction for using keyboard navigation, use this resource from WebAIM.

Select passing tests

Users can navigate between sections using only a keyboard. You can navigate easily among headings, text sections, and links, even without a mouse.

• WCAG A
• 2.1.1 Keyboard
• USWDS test status: Passed
• Last test: v3.7.1

• USWDS test status:
  Passed
• Last test: v3.7.1

Screen reader tests

USWDS performed these tests to check prose accessibility and usability for screen readers. For help performing your own screen reader tests, check out the resources in the expandable section below.

1. Navigate to a page on your website where the prose component is used.
2. Open a dedicated screen reading app or your operating system screen reader.
3. Test with both a keyboard and a mouse to complete the tests in the checklist.

---

Instructions for setting up the screen reader on your operating system:

1. VoiceOver for Mac: Getting started guide
2. Narrator for Windows: Complete guide to Narrator

Select passing tests

Heading levels are logical. All header tags contain appropriate heading text that describes the content nested below it. Headings are nested appropriately. For example, there is only one h1 per page, and no heading levels get skipped (e.g., no h4s nested directly under h2s without an h3 between them).

This can only be tested in your implementation of the component. Be sure to test this in your project.

• WCAG AA
• 2.4.6 Headings and labels
• USWDS test status: Conditional
• Last test: v3.7.1

• USWDS test status:
  Conditional
• Last test: v3.7.1

Share your feedback

• Propose a new test
• Report an error

Latest updates

Meaningful code and guidance updates are listed in the following table:

Date	USWDS version	Affects	Breaking	Description
2024-04-18	N/A	Guidance	No	Added accessibility tests page. More information: uswds-site#2613