Feedback on verbose descriptor requirements

Hi Gregory,

Sorry, but my minor tweaks of the requirements (at http://www.w3.org/WAI/PF/HTML/wiki/Verbose_desc_reqs) got carried away. What do you think?

1. Format requirement: A programmatic mechanism to reference a specific set of structured content (e.g., text, table, etc.) as a verbose descriptor to non-text content.

2. Format requirement: The verbose descriptor should be able to be stored internal (enhanced describedby model) or external (HTML4 longdesc model) to the document containing the described non-text content.

3. Format requirement: The mechanism should clearly define the start and end of the verbose description in case it is part of a larger document.

4. UA requirement: User option to indicate programmatically (e.g. via an AT) that a piece of non-text content has a verbose descriptor.

5. UA requirement: User option to indicate in the viewport (e.g. visually in a standard browser, aurally in an aural browser) that a piece of non-text content has a verbose descriptor.

6. UA requirement: Verbose descriptor must be available programmatically (e.g., via accessibility API to AT).

7. UA requirement: User option to display verbose descriptor and non-text content together (e.g., in the same viewport).

8. UA requirement: User option to display verbose descriptor separately (e.g., open in a new viewport). 

9. UA requirement: User must be able to return easily from the verbose description (whether internal, external, etc.) to the described non-text content.

Cheers,
Jan

-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University

Received on Thursday, 9 September 2010 18:21:33 UTC