W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2008

WCAG 2.0 at a Glance - Make info adaptable & available to assistive technologies

From: Shawn Henry <shawn@w3.org>
Date: Thu, 12 Jun 2008 19:17:13 -0500
Message-ID: <4851BC89.2080707@w3.org>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>, Judy Brewer <jbrewer@w3.org>
Cc: Jeanne Spellman <jeanne@w3.org>


Below is some information for discussion on the list and at the 13 June teleconference.

Current wording in question: "Make information adaptable and available to assistive technologies."
>From "WCAG 2.0 at a Glance" draft: http://www.w3.org/WAI/WCAG20/glance/
Background analysis/requirements/changelog: http://www.w3.org/WAI/EO/changelogs/cl-quicktips

Relevant guideline & success criteria (SC):
Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout ) without losing information or structure
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)
See also "How to Meet"/Quick Reference which lists techniques: http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation

A concern with current wording "adaptable and available to assistive technologies": Developers who haven't studied accessibility think that is such a daunting task that it is too big to do. I was trying to put it in terms that they already know, so they could see that it was a reachable goal.

Some options and thoughts on other wording:

"Use correct valid code that adapts to different screen sizes."
- doesn't really cover the guidelines & SC

"Use semantic code that adapts to different input/output devices"
- 'semantic code' probably too jargony for this audience.
- think 'input/output devices' is too limiting. what about people using plain browsers with CSS turned off? also, browsers, screen readers, etc. are software, and "devices" means hardware to some people.
- doesn't cover 1.3.3.

"The content is browser-, software-, and device-independent."
- doesn't directly address 1.3.3 but there's room for a few more words
- seems more daunting than current wording

"Make content adaptable, and separate content from structure"
- 'separate content from structure' is idea that many people know
- not sure this covers the SC sufficiently

Note about word count and line length:
- "Make info adaptable & available to assistive technologies" probably will fit on one line of a business card.
- "Make information adaptable and available to assistive technologies." probably will not.
- All the others in the current wording should fit on one line. Image of draft layouts are at <http://www.w3.org/WAI/EO/changelogs/cl-quicktips#glance_layout>

Other ideas?


Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
about: http://www.w3.org/People/Shawn/
phone: +1-617-395-7664
e-mail: shawn@w3.org
Received on Friday, 13 June 2008 00:18:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:57 UTC