Accessibility
From Dreamwidth Notes
Revision as of 12:48, 4 February 2009 by Rickybuchanan (Talk | contribs)
Contents
Goal
To make the Dreamwidth site and features more accessible.
Background
We need to figure out which parts/features of the site are causing trouble for disabled users, and which features don't cause any problems but can be /improved/ (and how), and which features work great. Fix the problematic features, tweak the things that can be improved, document the good ones so that people will know where to find them/how to use them.
Note that making a site accessible is not the same as making it mobile friendly (and vice versa). While the two goals have some similarities, they are not always compatible.
Biggest Needs
Someone with experience in accessibility concerns needs to go over the site with a fine-tooth comb, and say what is good and what is bad.
Possible Items to Consider
Alt text
- userpics Bugzilla
- site images
Dyslexic Users
- Text/background contrasts which are too high can be a problem for dyslexic users as much as low contrast can be a problem for those with low vision. Suggest using Black Widow Alternative Color Contrast Analyzer on things so it marks high as well as low contrast.
Keyboard-friendly
- tab-order
- offer alternatives to functions that are triggered on mouse-over? (90% sure that everything is trim has a non-fancy way to get to it, but can't hurt to check)
Some styles can make text unreadable for some users
- check sticky style=mine behavior Bugzilla
- can ?format=light be made sticky, too?
Screen readers
- JAWS windows screen reader
- WindowEyes windows screen reader
- VoiceOver os x screen reader
- Fangs Firefox extension could help simulate?