Add comprehensive accessibility testing tools section to accessibility guidelines - #562
Conversation
…y guidelines Co-authored-by: nonprofittechy <7645641+nonprofittechy@users.noreply.github.com>
nonprofittechy
left a comment
nonprofittechy
left a comment
There was a problem hiding this comment.
Reviewed the links and these seem both accurate and very helpful. This is good compilation of resources.
BryceStevenWilley
left a comment
BryceStevenWilley
left a comment
There was a problem hiding this comment.
Going to make a follow up PR to fix some of these comments. In general I think that fewer tools with a bit more context on how to use them when testing interviews is better than a dozen tools, where ~1/2 don't really apply, but I'll keep things mostly the same.
|
|
||
| * **[TalkBack](https://support.google.com/accessibility/android/answer/6283677)** - Android's built-in screen reader. | ||
| * **[Switch Access](https://support.google.com/accessibility/android/answer/6122836)** - Android feature for users with motor disabilities. | ||
| * **[Voice Control](https://support.apple.com/en-us/HT210417)** - iOS voice navigation feature. |
There was a problem hiding this comment.
Same with Dragon, I don't think that Voice Control is going to really help people with testing accessibility: if it gets picked up with Voice Over, it'll work with Voice Control. I'd probably link Voice Over down here again, just to emphasize that it's the same tool, both on Macs and iPhones.
Address late comments in #562. * Moves to the bottom of the page, to emphasize the other accessibility concerns over specific custom tools and screen readers. * Removes voice command technology, which is less helpful for testing. * Adds some clarifications on how to best use screen readers
This PR adds a comprehensive list of popular accessibility software tools to the accessibility guidelines page to help developers test their docassemble interviews for accessibility compliance.
Changes Made
Added a new "Accessibility testing tools" section to
docs/coding_style/accessibility.mdthat includes:Screen readers
Browser accessibility checkers
Manual testing tools
Mobile accessibility testing
Automated testing integration
Implementation Details
The new section is strategically placed after the introduction but before the specific accessibility guidelines. Each tool includes a direct link and brief description of its purpose. The section integrates seamlessly with the existing table of contents and maintains consistency with the documentation's style and structure.
This enhancement provides developers with practical resources for testing interview accessibility, with special emphasis on screen readers as requested in the original issue.
Fixes #429.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.