Edit ACTION-475: Create definition of 'benefit accessibility' or reword all SC in GL 3.3

Title:

State:

Person:

Due Date:

(accepts formats such as "2005-05-17", "+1 week", "14 August 2005" and "next Thursday")

Associated Issue:

Or Associated Product:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. Re: ACTION 475 - Benefits Accessibility (from simon.harper@manchester.ac.uk on 2010-12-09) (from simon.harper@manchester.ac.uk on 2010-12-09)
  2. Re: ACTION 475 - Benefits Accessibility (from gcl-0039@access-research.org on 2010-12-08) (from gcl-0039@access-research.org on 2010-12-08)
  3. ACTION 475 - Benefits Accessibility (from simon.harper@manchester.ac.uk on 2010-12-07) (from simon.harper@manchester.ac.uk on 2010-12-07)
  4. Minutes: UAAG 2 Dec 2010 (from jimallan@tsbvi.edu on 2010-12-02) (from jimallan@tsbvi.edu on 2010-12-02)

Related notes:

Suggested Features which benefit accessibility fall into two groups: (1) those features which have been explicitly created to aid accessibility, possibly in an attempt to follow guidelines such as these; or (2) those which assist accessibility but emerge from other functionality not originally created for accessibility purposes. Further, these accessibility benefits may be explicit such as the ability to control the User Agent from the keyboard; or implicit such as the ability to style a page based on a user supplied style sheet.

Simon Harper, 7 Dec 2010, 11:07:01


Jim Allan <jimallan@tsbvi.edu>, Kelly Ford <kelly.ford@microsoft.com>, Chairs, Jeanne F Spellman <jeanne@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $