Difference between revisions of "Accessibility Wishlist"

Revision as of 22:35, 12 October 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

• 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
  • 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