Difference between revisions of "Accessibility Wishlist"
From Dreamwidth Notes
Jadelennox (Talk | contribs) (re-organizing and adding a few more links based on what was already in the community) |
Jadelennox (Talk | contribs) m (slight reorganization for readability) |
||
Line 1: | Line 1: | ||
+ | {{TOC}} | ||
+ | |||
+ | == general wishlist == | ||
* 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. | ||
Line 9: | Line 12: | ||
* Make sure all forms on the site follow [http://www.webaim.org/techniques/forms/screen_reader.php these accessibility guidelines for screenreaders]. These guidelines also provide layout advice for high usability. | * Make sure all forms on the site follow [http://www.webaim.org/techniques/forms/screen_reader.php these accessibility guidelines for screenreaders]. These guidelines also provide layout advice for high usability. | ||
− | + | == 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]] | ||
[[Category: Wishlists]] [[Category:Accessibility]] | [[Category: Wishlists]] [[Category:Accessibility]] |
Revision as of 19:56, 22 August 2009
general wishlist
- 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.
-
For extra shininess, if somebody uses the audio version of the captcha select this option automatically.(with invite codes, we've removed the captcha)
-
Clear and accessible instructions on signup page on what to do if you can't complete the captcha for journal creation.(with invite codes, we've removed the captcha)
- On all styles, have alt text for all images.
- Make sure all forms on the site follow these accessibility guidelines for screenreaders. These guidelines also provide layout advice for high usability.
documentation wishlist
Put together documentation and make it publicly accessible and broadly disseminated from all the usual documentation places:
- for dreamwidth users
- 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