During the development of digital content and tools, a user story provides a general explanation of a feature from the end user or customer viewpoint. User stories are essential in the development of Section 508 conformant information and communication technology (ICT) because they ensure the needs of users with disabilities are considered during design, development, and testing. They help development teams understand how end users interact with digital content using assistive technologies like screen readers or keyboard navigation. By embedding ICT accessibility requirements into everyday practices, user stories support compliance with Section 508 standards and reduce the risk of costly retrofits or remediation. Most importantly, they help teams build products that are well designed and usable by everyone.
Tip: User stories define the “what and how” to address Section 508 conformance during design, development, and testing and when writing backlog items.
How to Write User Stories
To write effective ICT accessibility-related user stories, start with the format: As a [user type or user need], I want [goal, action, or function] so that [benefit or achievement].
- User type or need: Clearly identify a user with a specific accessibility need such as a keyboard-only user.
- Goal, action, function: State what they want to do such as tab through a form logically.
- Benefit or Achievement: Explain why it matters, such as to complete a task independently.
- Acceptance criteria: Defines when the story is complete; this might involve meeting contrast requirements, supporting screen readers, or ensuring keyboard functionality.
Write with clarity and alignment to Section 508 Standards so that user stories are actionable and meaningful.
For example: As a user who relies on high contrast, I want to view text with sufficient contrast against backgrounds so I can read content easily.
Acceptance Criteria: All text meets Web Content Accessibility Guidelines (WCAG) 1.4.3 contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (text that is 14 point and bold or larger, or 18 point or larger).
Example User Stories
The following user stories illustrate how accessibility needs can be captured during the development of digital content and tools. These examples are not exhaustive; development teams should tailor user stories to reflect the specific users, features, and technologies relevant to their own product or project.
User Stories:
- Define specific functionality or needs
- Are task-specific with a focus on goals or interactions
- Are short and focused on functionality and goals
| User Story | Description | Applicable ICT |
|---|---|---|
| As a keyboard user, I want to be able to access and activate all interactive content such as form fields, buttons, and links so that I can successfully complete forms. |
|
Documents, Software, Web |
| As a keyboard user, I want to be able to navigate content in the correct reading order so that I can understand content in a way that makes sense. | If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. [WCAG SC 2.4.3] | Documents, Software, Web |
| As a keyboard user, I want to be able to easily use hotkeys to navigate the page by headings so that I can understand relevant information to me. |
|
Documents, Software, Web |
| As a screenreader user, I want to be able to complete form fields including fixing any errors so that I can independently accomplish tasks. |
|
Documents, Software, Web |
| As a screenreader user, I want to know the column and row headers for each table cell so that I can understand the meaning of data tables. |
|
Documents, Software, Web |
| As a screenreader user, I want to hear the text equivalent for each meaningful image so that I don’t miss any information on the page. | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations. [WCAG SC 1.1.1] | Documents, Software, Web |
| As a screenreader user, I want to know the page language so that my assistive technology presents the content accurately. | The default human language of each web page can be programmatically determined. [WCAG SC 3.1.1] | Documents, Software, Web |
| As a screenreader user, I want to know when words are in a different language on the page and what language is used so that my assistive technology presents the content accurately. | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. [WCAG SC 3.1.2] | Documents, Software, Web |
| As a screenreader user, I want to be able to read content in a meaningful sequence so that I understand the meaning of content in context. | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. [WCAG SC 1.3.2] | Documents, Software, Web |
| As a screenreader user, I want to hear a presentation of visual content in a video so that I have access to the visual content as well. | Audio description is provided for all prerecorded video content in synchronized media. [WCAG SC 1.2.5] | Documents, Software, Web |
| As a screenreader user, I want consistency between multiple web pages in a website so that I can more easily navigate. |
|
Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user with limited vision, I want to be able to zoom without losing content so that I can read text at a comfortable size. | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. [WCAG SC 1.4.4] | Documents, Software, Web |
| As a user with limited vision, I want to be able to complete a CAPTCHA so that I can complete forms and log-ins independently. | If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. [WCAG SC 1.1.1] | Documents, Software, Web |
| As a user who sees better with high contrast, I want to be able to customize images of text so that it is easier for me to read. | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: [WCAG SC 1.4.5] The image can be visually customized. A particular presentation of text is essential. | Documents, Software, Web |
| As a user who sees better with high contrast, I want sufficient contrast between text and its background so that I can easily read text. | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:[WCAG 1SC .4.3] Large text Incidental text Logotypes | Documents, Software, Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user who is colorblind, I want to understand charts that use color to glean the information presented. | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. [WCAG SC 1.4.1] | Documents, Software, Web |
| As a user who is red-green colorblind, I want to be able to correct errors that are shown in red so that I can successfully submit forms. | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. [WCAG SC 1.4.1] | Documents, Software, Web |
| As a user who is colorblind, I want links to be distinguishable on the page so that I can find them. | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. [WCAG SC 1.4.1] | Documents, Software, Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user without hearing, I want captions on multimedia so that I can fully understand what is happening in the media. | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. [WCAG SC 1.2.2] | Documents, Software, Web |
| As a user without hearing, I want accurate captions during live meetings so that I can keep up with what is happening. | Captions are provided for all live audio content in synchronized media. [WCAG SC 1.2.4] | Documents, Software, Web |
| As a user without hearing, I want to be able to solve a CAPTCHA independently so that I don’t have to ask someone else for help. | Alternative forms of CAPTCHA are provided for users without hearing. [WCAG SC 1.1.1] | Documents, Software, Web |
| As a user without hearing, I want to be able to read a transcript of audio-only content so that I have a complete and accurate understanding of the audio. | Audio-only content provides a transcript that is an accurate and complete representation of the audio-only content and includes relevant sounds in addition to dialogue, such as doors banging, sirens wailing, identification of speakers in dialogue, etc. [WCAG SC 1.2.1] | Documents, Software, Web |
| As a user without hearing, I want accurate captions so that I have an equivalent experience while watching media with audio. | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. [WCAG SC 1.2.2] | Documents, Software, Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user with very limited hearing in my left ear, I want text notifications in addition to audible alerts, so that I am informed when a form has not been completed accurately. | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as sound. [WCAG SC 1.3.3] | Documents, Software, Web |
| As a user with limited hearing, I want to be able to easily turn off audio that plays automatically so that I am not distracting others. | If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. [WCAG SC 1.4.2] | Documents, Software, Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user without speech, I want multiple methods of user identification so that I can independently perform tasks. | Where provided, biometrics shall not be the only means for user identification or control.[Section 508 403.1] | Hardware |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a user with limited ability to control a mouse, I want interactive elements to be accessible by keyboard so that I can easily navigate and interact with them. | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.[WCAG SC 2.1.1] | Documents, Software, Web |
| As a user with limited ability to use a keyboard and mouse, I want time outs to allow me sufficient time to extend or disable so that I can complete long forms. | For each time limit that is set by the content, at least one of the following is true: [WCAG SC 2.2.1] Turn off: The user is allowed to turn off the time limit before encountering it. Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting. Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times. | Documents, Software, Web |
| As a keyboard only user, I want to be able to navigate content without getting stuck or trapped in a section on the page so that I can interact with all content I want. | If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. [WCAG SC 2.1.2] | Documents, Software, Web |
| As a keyboard only user, I want to be able to see where my focus is so that I know what is on the page and what actions I can perform. | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. [WCAG SC 2.4.7] | Documents, Software, Web |
| As a keyboard only user, I want to be able to focus on a submit button without actually submitting the form so that I can review my information first. | When any user interface component receives focus, it does not initiate a change of context. [WCAG SC 3.2.1] | Documents, Software, Web |
| As a user with limited ability to use my hands, I want to be able to skip repeated navigation menus at the top of each page so that I can get to the body of the content faster. | A mechanism is available to bypass blocks of content that are repeated on multiple web pages. [WCAG SC 2.4.1] | Web |
| User Story | Description | Applicable ICT |
|---|---|---|
| As a voice input user, I want to be able to use my dictation software to complete all interactive activities so that I do not need to rely on others for help. |
| Documents, Software, Web |
| As a user who cannot use their arms, I want the software application to interoperate with voice control technologies so that I can perform my job duties using technology I know how to use. | Software shall interoperate with assistive technology and shall conform to 502. [Section 508 502.1] EXCEPTION: ICT conforming to 402 shall not be required to conform to 502. | Software |
| As a voice input user, I want to be able to see if my input has been received and action has been taken so that I know I have completed the task. | Software must expose the role, state, and name of UI elements to assistive technologies. [Section 508 502.3.1] | Software |