A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

Difference between revisions of "Change Proposal for not including longdesc="""

From WHATWG Wiki
Jump to navigation Jump to search
(Created page with '== Summary == The longdesc="" attribute does not improve accessibility in practice and should not be included in the language. == Rationale == Several studies (listed in the r...')
 
Line 6: Line 6:


Several studies (listed in the references) have been performed. They have shown that:
Several studies (listed in the references) have been performed. They have shown that:
* longdesc is extremely rarely used (on the order of 0.1% in one study). [1]
* longdesc is extremely rarely used (on the order of 0.1% in one study). [http://blog.whatwg.org/the-longdesc-lottery]
* when used, longdesc is extremely rarely used correctly (on the order of 1% in a study that only excluded obvious errors; below the threshold of statistical significance on one that examined each longdesc="" by hand). [1] [2]
* when used, longdesc is extremely rarely used correctly (on the order of 1% in a study that only excluded obvious errors; below the threshold of statistical significance on one that examined each longdesc="" by hand). [http://blog.whatwg.org/the-longdesc-lottery] [http://wiki.whatwg.org/wiki/Longdesc_usage]
* AT users don't know that longdesc="" exists. [3]
* AT users don't know that longdesc="" exists. [http://www.cfit.ie/html5_video/]
* most users (more than 90%) don't want the interaction model that longdesc="" implies. [4]
* most users (more than 90%) don't want the interaction model that longdesc="" implies. [http://webaim.org/projects/screenreadersurvey2/#images]


== Details ==
== Details ==
Line 30: Line 30:


No change to spec.
No change to spec.
This would not affect existing ATs and user agents, as they can continue to support longdesc="" if compatibility with some set of documents where it is used correctly is desired. In practice, removing support is likely to either not be noticed (some users don't know the feature exists) or actually improve matters (given how poorly the feature is used in practice on the Web).


=== Risks ===
=== Risks ===
Line 37: Line 39:
== References ==
== References ==


* [1] http://blog.whatwg.org/the-longdesc-lottery
Links included inline.
* [2] http://wiki.whatwg.org/wiki/Longdesc_usage
* [3] http://www.cfit.ie/html5_video/ as interpreted by [1]
* [4] http://webaim.org/projects/screenreadersurvey2/#images

Revision as of 01:27, 11 February 2010

Summary

The longdesc="" attribute does not improve accessibility in practice and should not be included in the language.

Rationale

Several studies (listed in the references) have been performed. They have shown that:

  • longdesc is extremely rarely used (on the order of 0.1% in one study). [1]
  • when used, longdesc is extremely rarely used correctly (on the order of 1% in a study that only excluded obvious errors; below the threshold of statistical significance on one that examined each longdesc="" by hand). [2] [3]
  • AT users don't know that longdesc="" exists. [4]
  • most users (more than 90%) don't want the interaction model that longdesc="" implies. [5]

Details

No change to the spec.

Impact

Positive Effects

  • Stops authors from spending time trying to use a feature that they don't understand and that users don't want.
  • Encourages authors to include suitable information in an alternative form that is more likely to be accurate.
  • Results in better overall accessibility on the long term.

Negative Effects

  • ?

Conformance Classes Changes

No change to spec.

This would not affect existing ATs and user agents, as they can continue to support longdesc="" if compatibility with some set of documents where it is used correctly is desired. In practice, removing support is likely to either not be noticed (some users don't know the feature exists) or actually improve matters (given how poorly the feature is used in practice on the Web).

Risks

  • ?

References

Links included inline.