321634 - UAAG: provide an outline view of rendered content

Status: NEW

(Core :: Disability Access APIs, defect, P5)

Description

[Dan Kinnunen]

From UAAG specification, checkpoint 10.4:
- Make available to the user an "outline" view of rendered content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, and other labels that are part of the content).

The specific failing UAAG tests are listed below.  First, here are some recommended solutions:
1.  List important elements (forms, controls, links, headings, tables, lists) in the Page Info dialog and make the list items live so that a user can move the focus or caret to those important elements. Forms, form controls, and links are listed in Page Info but are not live.  

Failing UAAG checkpoints related to this bug:

UAAG Checkpoint 10.4: Provide outline view
- Test  200: Outline View of Headings
  test URL: http://cita.rehab.uiuc.edu/wai-eval/show-test/index.php?test_id=200

- Test  199: Outline View of the CAPTION attribute for TABLE elements
  test URL: http://cita.rehab.uiuc.edu/wai-eval/show-test/index.php?test_id=199

Comment 1

[Aaron Leventhal]

Mark, can you figure out the path of least resistance on this one? I've never heard a user ask for it.

Comment 2

[Mark Pilgrim (inactive)]

The Accessibility Extension does this (at least the header outline).

http://cita.rehab.uiuc.edu/software/mozilla/

Comment 3

[Mark Pilgrim (inactive)]

Charles Chen's CLC4TTS/FireVox extension also provides this: https://webspace.utexas.edu/chencl1/clc-4-tts/

Hans Hillen's NavAccess extension does it too.  I can't find a download link; I saw it (and him) at CSUN.  Here's a PDF that describes it: http://sigchi.nt4all.nl/documents/Hillen%20-%20NavAccess.pdf

Anyway, the path of *least* resistance is to tell users to go download one of these extensions.  Do we really want to put this into the core?