Difference between revisions of "Accessibility Wishlist"
From Dreamwidth Notes
(Added wish related to form usability) |
(→General wishlist: s/Bugzilla/GHI/) |
||
| (15 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | == General wishlist == | ||
| + | |||
| + | At this point, pretty much everything in the wishlist should be a bug ticket -- put them here if there is still some question over whether or not they need to be in the [[Github Issues|bug tracking system]]. | ||
| + | |||
* Have a question/option at signup which can funnel people into an area that asks about accessibility needs and shows them what's available for different accessibility needs. | * Have a question/option at signup which can funnel people into an area that asks about accessibility needs and shows them what's available for different accessibility needs. | ||
| − | + | == Documentation wishlist == | |
| + | |||
| + | Put together documentation and make it publicly accessible and broadly disseminated from all the usual documentation places: | ||
| + | |||
| + | === For Dreamwidth users === | ||
| − | * | + | * [[Accessibility features in dreamwidth]] |
| + | * [[Keeping your layout accessible when you customize it]] | ||
| + | * [[How to write userpic descriptions]] | ||
| + | * [[Links for end-users to ask for more help or make suggestions]] | ||
| − | + | === For Dreamwidth developers, designers, and documentation producers === | |
| − | * | + | * Style creators: [[Creating an accessible style]] |
| + | * Developers, style creators, designers: [[Principles of universal design]] | ||
| + | * Developers: [[Resources for creating accessible HTML and AJAX]] | ||
| + | * Site copy, FAQ, documentation, and support people: [[Avoiding language that assumes able-bodied users]] | ||
| + | * Everyone: [[Accessibility Testing]] | ||
| − | + | === Useful resources to document === | |
| + | * Our in-house list of [[Accessible technology]] | ||
| + | * WebAIM (Web accessibility in mind) if a treasure trove of useful resources | ||
| + | ** [http://www.webaim.org/ Main site] and [http://www.webaim.org/intro/ introduction] | ||
| + | ** [http://www.webaim.org/discussion/ Mailing list] (low/medium volume, very good signal-to-noise ratio, beginner friendly) | ||
| + | ** [http://www.webaim.org/projects/screenreadersurvey/ Screen reader users survey] and [http://webaim.org/projects/screenreadersurvey2/ second screenreader survey] | ||
| + | ** [http://www.webaim.org/simulations/screenreader/ Screenreader simulation]: learn what it's like to use a screen reader | ||
| + | * Accessibility validation tools. Note that no tool can do anything more than point out to you something you might look at. No "validated" site is guaranteed to be perfect. [http://www.w3.org/WAI/eval/selectingtools.html The w3c explains the limitations of validation tools and how to choose one]. | ||
| + | * [http://www.accessfirefox.org/ Access Firefox]: Mozilla's resource list | ||
| − | [[Category: Wishlists]] [[Category:Accessibility]] | + | [[Category: Wishlists]] [[Category:Accessibility]] [[Category:Documentation]] |
Latest revision as of 13:14, 1 August 2014
Contents
General wishlist
At this point, pretty much everything in the wishlist should be a bug ticket -- put them here if there is still some question over whether or not they need to be in the bug tracking system.
- Have a question/option at signup which can funnel people into an area that asks about accessibility needs and shows them what's available for different accessibility needs.
Documentation wishlist
Put together documentation and make it publicly accessible and broadly disseminated from all the usual documentation places:
For Dreamwidth users
- Accessibility features in dreamwidth
- Keeping your layout accessible when you customize it
- How to write userpic descriptions
- Links for end-users to ask for more help or make suggestions
For Dreamwidth developers, designers, and documentation producers
- Style creators: Creating an accessible style
- Developers, style creators, designers: Principles of universal design
- Developers: Resources for creating accessible HTML and AJAX
- Site copy, FAQ, documentation, and support people: Avoiding language that assumes able-bodied users
- Everyone: Accessibility Testing
Useful resources to document
- Our in-house list of Accessible technology
- WebAIM (Web accessibility in mind) if a treasure trove of useful resources
- Main site and introduction
- Mailing list (low/medium volume, very good signal-to-noise ratio, beginner friendly)
- Screen reader users survey and second screenreader survey
- Screenreader simulation: learn what it's like to use a screen reader
- Accessibility validation tools. Note that no tool can do anything more than point out to you something you might look at. No "validated" site is guaranteed to be perfect. The w3c explains the limitations of validation tools and how to choose one.
- Access Firefox: Mozilla's resource list
