Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

edit steps to take.md #8365

Merged
merged 2 commits into from
Jan 24, 2025
Merged

edit steps to take.md #8365

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b826dd
edit steps to take.md
camillemorrow Jan 24, 2025
40c7dd7
Merge branch 'main' into cltm_update-accessibility-for-product-mgrs
ToniBonittoGSA Jan 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/guides/accessibility-for-teams/product-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Consider how everyone will use the product.
### Steps to take

1. **Don’t assume that your users don’t have accessibility needs.** Even if your product serves a small subset of users, any one individual may experience disabilities that are situational (working in a loud environment) or temporary (having an arm in a cast), or develop a permanent one.
2. **Consider inclusion in your research and usability testing with a range of people** across ages, races, locations, devices, interests, abilities, languages, English proficiency, gender identities, sexual orientations, and access to reliable internet.
2. **Engage with various perspectives** in your research and in usability testing, considering a range of experiences and abilities.
3. **Consider testing your product with people in their own context**, such as people who use alternative reading devices, have color blindness impairments, or motor impairments.
4. **Set a regular cadence** for testing accessibility scenarios.

Expand Down