Accessibility
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.
Communication
The accessibility team communicates on the DW Accessibility mailing list
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. New concerns should be listed in the Accessibility Wishlist -- or better, turned into bugs.
Possible Items to Consider
Alt text
- 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.
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)
- offer simple alternatives to places where you will do control-click to get multiple elements off a list (e.g. choosing tags, where the keyboard alternative currently is to remember the names of your tags and type them in)
- WAI-ARIA
Some styles can make text unreadable for some users
- can ?format=light be made sticky, too?
compatible with known adaptive technology
We maintain a list of [Adaptive technology] programs with which dreamwidth needs to interact.
emerging technology
- WAI-ARIA
- HTML 5 -- years away, but we should keep an eye on it
