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

Re: UAWG Action item: Add title text to draft idea for splitting up the checkpoints.

From: Catherine Laws <claws@us.ibm.com>
Date: Thu, 17 May 2007 22:36:27 -0500
To: Jan Richards <jan.richards@utoronto.ca>, w3c-wai-ua@w3.org
Message-ID: <OF1C1C4EA7.3DBB456E-ON862572DF.000F9CE5-862572DF.0013D126@us.ibm.com>





I think you mean "clarify what requirements the "Chrome" has to
meet vs. what the user agent can do about the content it renders."

I like the split between chorme and the UA rendering content, but I think
there should not be a distinction between perceivable and understandable.
It seems like anything that is perceivable through a UA rendering must also
be understandable, that is aid in the end user's comprehension. Only 12.2,
12.4, and 12.5 fit under understandable and not really under perceivable.

Also, I think 10.1 Associate table cells and headers (P1) belongs under
perceivable and understandable, not operable.,

10.4 Provide outline view (P2)belongs under perceivable and understandable,
but when the outline view is navigable, it also belongs under operable.

8.1 Implement accessibility features (P1) fits under perceivable and
understandable - it goes hand in hand with 2.1 Render content according to
specification (P1, which is already under perceivable.

Should 8.2 Conform to specifications (P2) be converted into a baseline
statement for UAAG instead of being a single UAAG guideline?

Cathy Laws

Manager - IBM Software Group (SWG) Accessibility Architecture and
Development
11501 Burnet Road,  Bldg 902 Office 2C016, Austin, Texas 78758
Phone: (512) 838-4595  FAX: (512) 246-8502
E-mail: claws@us.ibm.com, Web: http://www.ibm.com/able

Faith is being sure of what we hope for and certain of what we do not see.


                                                                           
             Jan Richards                                                  
             <jan.richards@uto                                             
             ronto.ca>                                                  To 
             Sent by:                  w3c-wai-ua@w3.org                   
             w3c-wai-ua-reques                                          cc 
             t@w3.org                  Alfred.S.Gilman@IEEE.org            
                                                                   Subject 
                                       Re: UAWG Action item: Add title     
             05/11/2007 02:54          text to draft idea for splitting    
             PM                        up the  checkpoints.                
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





BTW Although I have given my two cents on how UAAG might break into just
4 categories I would like to remind people of the 2x4-part split that I
suggested a while back.
(http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0053.html)

PART A: Make the user agent user interface accessible. [ie. "Chrome"]
  A.1: User agent user interface must be perceivable
  A.2: User agent user interface must be operable
  A.3: User agent user interface must be understandable
  A.4: User agent user interface must be access system friendly

PART B: Enhance the accessibility of rendered content.
  B.1: Perceivability of rendered content must be enhanced
  B.2: Operability of rendered content must be enhanced.
  B.3: Understandability of rendered content must be enhanced.
  B.4: Access system friendliness of rendered content must be enhanced.

I think this would help clarify what requirements the "Chrome" has to
meet vs. what the user interface can do about the content it renders. I
also wonder whether this goes some way towards what Al was advocating,
though I realize the term "perceivable" remains (so I have CC'd him).

Thoughts?

Cheers,
Jan





Jan Richards wrote:
>
> PERCEIVABLE:
>
> 1.3 Provide text messages (P1)
> 2.1 Render content according to specification (P1) - COULD ALSO BE
OPERABLE
> 2.2 Provide text view (P1)
> 2.3 Render conditional content (P1)
> 2.4 Allow time-independent interaction (P1) - COULD ALSO BE OPERABLE
> 2.5 Make captions, transcripts, audio descriptions available (P1)
> 2.6 Respect synchronization cues (P1)
> 2.7 Repair missing content (P2)
> 2.9 Render conditional content automatically (P3)
> 2.10 Don't render text in unsupported writing systems (P3)
> 3.1 Toggle background images (P1)
> 3.2 Toggle audio, video, animated images (P1)
> 3.3 Toggle animated or blinking text (P1)
> 3.4 Toggle scripts (P1)
> 3.5 Toggle automatic content retrieval (P1)
> 3.6 Toggle images (P2)
> 4.1 Configure text scale (P1)
> 4.2 Configure font family (P1)
> 4.3 Configure text colors (P1)
> 4.6 Do not obscure captions (P1)
> 4.7 Global volume control (P1)
> 4.8 Independent volume control (P1)
> 4.9 Configure synthesized speech rate (P1)
> 4.10 Configure synthesized speech volume (P1)
> 4.11 Configure synthesized speech characteristics (P1)
> 4.12 Specific synthesized speech characteristics (P2)
> 4.13 Configure synthesized speech features (P2)
> 4.14 Choose style sheets (P1)
> 12.1 Provide accessible documentation (P1)
>
> OPERABLE:
>
> 1.1 Full keyboard access (P1)
> 1.2 Activate event handlers (P1)
> 5.1 No automatic content focus change (P2)
> 5.2 Keep viewport on top (P2)
> 5.3 Manual viewport open only (P2)
> 5.4 Selection and focus in viewport (P2)
> 7.1 Respect focus and selection conventions (P1)
> 7.2 Respect input configuration conventions (P1)
> 7.4 Provide input configuration indications (P2)
> 9.1 Provide content focus (P1)
> 9.2 Provide user interface focus (P1)
> 9.3 Move content focus (P1)
> 9.4 Restore viewport state history (P1)
> 9.5 No events on focus change (P2)
> 9.6 Show event handlers (P2)
> 9.7 Move content focus in reverse (P2)
> 9.8 Provide text search (P2)
> 9.9 Allow structured navigation (P2)
> 9.10 Configure important elements (P3)
> 10.1 Associate table cells and headers (P1)
> 10.2 Highlight selection, content focus, enabled elements, visited links
> (P1)
> 10.3 Single highlight configuration (P2)
> 10.4 Provide outline view (P2)
> 10.5 Provide link information (P3)
> 10.6 Highlight current viewport (P1)
> 10.7 Indicate viewport position (P3)
> 11.1 Current user input configuration (P1)
> 11.2 Current author input configuration (P2)
> 11.3 Allow override of bindings (P2)
> 11.4 Single-key access (P2)
> 11.5 Default input configuration (P2)
> 11.6 User profiles (P2)
> 11.7 Tool bar configuration (P3)
> 12.3 Provide documentation of default bindings (P1)
>
> UNDERSTANDABLE:
> 2.8 No repair text (P3)
> 4.4 Slow multimedia (P1) (could also be considered PERCEIVABLE)
> 4.5 Start, stop, pause, and navigate multimedia (P1) (could also be
> considered PERCEIVABLE)
> 5.5 Confirm form submission (P2)
> 7.3 Respect operating environment conventions (P2)
> 12.2 Provide documentation of accessibility features (P1)
> 12.4 Provide documentation of changes between versions (P2)
> 12.5 Provide dedicated accessibility section (P2)
>
> ASSISTIVE TECH FRIENDLY:
> 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)
> 8.1 Implement accessibility features (P1)
> 8.2 Conform to specifications (P2)
>
>

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

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








graycol.gif
(image/gif attachment: graycol.gif)

pic25313.gif
(image/gif attachment: pic25313.gif)

ecblank.gif
(image/gif attachment: ecblank.gif)

Received on Friday, 18 May 2007 03:36:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:35 UTC