ATAG requirements on accessible authoring interfaces

As promised some time ago, I have updated the worksheet comparing UAAG 
with the ISO doc and Sect 508 with indicators to show which requirements 
we might want to use (along with our existing accessible authoring 
interface requirements) instead of pointing to the ISO doc. This is 
attached.

As a summary, the full set of accessible authoring interface 
requirements for (non-Web based tools) might read as follows:

ATAG's existing requirements:
1.3 Allow the display preferences of the authoring interface to be 
changed without affecting the document markup.
1.4 Ensure that the authoring interface enables the author to navigate 
the structure and perform structure-based edits.
1.5 Ensure that the authoring interface allows the author to search 
within the editing views.


Then, the subset of UAAG:

1.1 Full keyboard access
     + 1.2 Activate event handlers
     + 9.1 Provide content focus
     + 9.2 Provide user interface focus
     + 9.3 Move content focus
     + 9.7 Move content focus in reverse
1.3 Provide text messages
2.4 Allow time-independent interaction
     + 3.2 Toggle audio, video, animated images
     + 3.3 Toggle animated or blinking text
     + 4.4 Slow multimedia
     + 4.5 Start, stop, pause, and navigate multimedia
2.5 Make captions, transcripts, audio descriptions available
4.1 Configure text scale
4.2 Configure font family
4.3 Configure text colors
4.14 Choose style sheets
5.1 No automatic content focus change
6.5 Programmatic operation of user agent user interface
7.1 Respect focus and selection conventions
     + 7.2 Respect input configuration conventions
     + 7.3 Respect operating environment conventions
     + 7.4 Provide input configuration indications
9.5 No events on focus change
9.6 Show event handlers
10.1 Associate table cells and headers
10.2 Highlight selection, content focus, enabled elements, visited links
10.7 Indicate viewport position
11.1 Current user input configuration
11.3 Allow override of bindings
11.6 User profiles
12.1 Provide accessible documentation
12.2 Provide documentation of accessibility feature
12.3 Provide documentation of default binding
12.5 Provide dedicated accessibility section

Then a few other things:
- Must be an undo
- User must be able to control "always top "windows with the keyboard.

---

The area of UAAG that I was most unsure about when I was doing the 
subset is Guideline 6. What are the feelings of others in the group 
about which of the following requirements are transferable from UAAG to 
ATAG?

6.1 Programmatic access to HTML/XML infoset (P1)
6.2 DOM access to HTML/XML content (P1)
6.3 Programmatic access to non-HTML/XML content (P1)
6.4 Programmatic access to information about rendered content (P1)
6.5 Programmatic operation of user agent user interface (P1)
6.6 Programmatic notification of changes (P1)
6.7 Conventional keyboard APIs (P1)
6.8 API character encodings (P1)
6.9 DOM access to CSS style sheets (P2)
6.10 Timely exchanges through APIs (P2)

---

Cheers,
Jan

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC), University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896