keybase / keybase/keybase-issues
Screen reader support (eg: JAWS, etc)
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
For accessibility, some guidelines should be followed to ensure screen-reader clarity and ease of navigation. This ties in #14.
Tools such as [Fangs](https://addons.mozilla.org/en-us/firefox/addon/fangs-screen-reader-emulator/) can help with ensuring screen-reader users will be able to access the site effectively.
[Browsing habits of screen reader users](http://www.standards-schmandards.com/2005/browsing-habits/) provides some (possibly a little dated since the article is from 2005) detail on what the implications are in terms of markup.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the accessibility guidance in the issue and use the linked Fangs tool to inspect the site's screen-reader output. Define the affected pages and markup changes, then confirm that navigation and content are clear for screen-reader users across the identified areas.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100