Difference between revisions of "Accessibility"

From Dreamwidth Notes
Jump to: navigation, search
(removing things which are already bugs or are reproduced elsewhere in the accessibility category)
Line 1: Line 1:
−
= Goal =
+
== Goal ==
 
To make the Dreamwidth site and features more accessible.
 
To make the Dreamwidth site and features more accessible.
  
−
= Background =
+
== 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.
+
We need to figure out which parts and features of the site are causing trouble for disabled users, which features don't cause any problems but can be '''improved''' (and how), and which features work great. Then, we need to fix the problematic features, tweak the things that can be improved, and document the good ones so that people will know where to find them and 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.
  
 
* [http://bugs.dwscoalition.org/buglist.cgi?query_format=advancedkeywords_type=allwords&keywords=why-accessibility&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Open Bugzilla items tagged why-accessibility]
 
* [http://bugs.dwscoalition.org/buglist.cgi?query_format=advancedkeywords_type=allwords&keywords=why-accessibility&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Open Bugzilla items tagged why-accessibility]
 
* [http://bugs.dwscoalition.org/buglist.cgi?query_format=advancedkeywords_type=allwords&keywords=why-accessibility All Bugzilla items tagged why-accessibility]
 
* [http://bugs.dwscoalition.org/buglist.cgi?query_format=advancedkeywords_type=allwords&keywords=why-accessibility All Bugzilla items tagged why-accessibility]
  
−
= Communication =
+
== Communication ==
  
−
The accessibility team communicates on the [http://lists.dwscoalition.org/mailman/listinfo/dw-accessibility DW Accessibility mailing list]
+
The accessibility team communicates on the [http://lists.dwscoalition.org/mailman/listinfo/dw-accessibility DW Accessibility mailing list].
  
−
= Biggest Needs =
+
== 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 =
+
Someone with experience in accessibility concerns needs to go over the site with a fine-tooth comb, and document what is good and what could be improved. New concerns should be listed in the [[Accessibility Wishlist]] page -- or better yet, turned into [[Bugzilla|bugs]].
  
−
== Alt text ==
+
== Possible Items to Consider ==
−
* site images
+
  
−
== Dyslexic Users ==
+
=== Alt text ===
−
* 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 ==  
+
* Determine the working definition of "relevant site images" -- spacer images probably don't need alt text.
−
* tab-order
+
* Check all relevant site images for alt text.
−
* 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)
+
* Question: alt text versus title text?
−
* 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]]
+
=== Dyslexic Users ===
 +
 
 +
* Text/background contrasts which are ''too high'' can be a problem for dyslexic users, just like low contrast can be a problem for those with low vision.
 +
 
 +
== Keyboard-friendly ==
 +
 
 +
* Check the tab order of pages, as some users don't like to use the mouse.
 +
* Offer alternatives to functions that are triggered on mouse-over. Most items that are fancy likely have a non-fancy way to get to it, but it can't hurt to check.
 +
* Offer simple alternatives to places where you need to control-click to select multiple elements of a list. For example, choosing tags, where the current keyboard alternative is to remember the names of your tags and type them in.
 +
* [[WAI-ARIA]].
 +
 
 +
=== Style readability ===
  
−
== Some styles can make text unreadable for some users ==
+
* Can <code>format=light</code> be made sticky, too?
  
−
* can ?format=light be made sticky, too?
+
=== Compatible with known adaptive technology ===
  
−
== compatible with known adaptive technology ==
+
We maintain a list of [[Adaptive technology]] programs with which Dreamwidth needs to interact.
  
−
We maintain a list of [Adaptive technology] programs with which dreamwidth needs to interact.
+
== Emerging technology ==
  
−
= emerging technology =
 
 
* [[WAI-ARIA]]
 
* [[WAI-ARIA]]
−
* HTML 5 -- years away, but we should keep an eye on it
+
* [[http://www.w3.org/TR/html5/ HTML5]] -- years away, but we should keep an eye on it.
  
 
[[Category:Brainstorming]] [[Category:Accessibility]]
 
[[Category:Brainstorming]] [[Category:Accessibility]]

Revision as of 19:58, 8 December 2010

Goal

To make the Dreamwidth site and features more accessible.

Background

We need to figure out which parts and features of the site are causing trouble for disabled users, which features don't cause any problems but can be improved (and how), and which features work great. Then, we need to fix the problematic features, tweak the things that can be improved, and document the good ones so that people will know where to find them and 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 document what is good and what could be improved. New concerns should be listed in the Accessibility Wishlist page -- or better yet, turned into bugs.

Possible Items to Consider

Alt text

  • Determine the working definition of "relevant site images" -- spacer images probably don't need alt text.
  • Check all relevant site images for alt text.
  • Question: alt text versus title text?

Dyslexic Users

  • Text/background contrasts which are too high can be a problem for dyslexic users, just like low contrast can be a problem for those with low vision.

Keyboard-friendly

  • Check the tab order of pages, as some users don't like to use the mouse.
  • Offer alternatives to functions that are triggered on mouse-over. Most items that are fancy likely have a non-fancy way to get to it, but it can't hurt to check.
  • Offer simple alternatives to places where you need to control-click to select multiple elements of a list. For example, choosing tags, where the current keyboard alternative is to remember the names of your tags and type them in.
  • WAI-ARIA.

Style readability

  • 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
  • [HTML5] -- years away, but we should keep an eye on it.
Retrieved from "http://wiki.dreamwidth.net/wiki/index.php?title=Accessibility&oldid=9343"