W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2008

Re: UAAG2: 10.2 Rewording ideas

From: Jan Richards <jan.richards@utoronto.ca>
Date: Thu, 31 Jan 2008 15:17:58 -0500
Message-ID: <47A22CF6.106@utoronto.ca>
To: w3c-wai-ua@w3.org

REVISED AFTER JAN 31 CALL

Please note:
1. I've moved back closer to the sense of the previous wording
2. After thinking about it, I think except "(when "recognized" as 
"content-controlled")" can better be handled in the definition of 
content focus.


10.2 Highlight selection, content focus, enabled elements, visited links

Level A

1. Highlighting options are provided for the following classes of 
information:
(a) selection
(b) content focus
(c) enabled elements
(d) recently visited links.

2. The highlighting options include both of the following:
(a) foreground colors (with the same configurable range as the 
platform's conventional color selection utility)
(b) background colors (with the same configurable range as the 
platform's conventional color selection utility)

2. The highlighting options includes at least one of the following:
(a) borders (with configurable color and width)
(b) text size (with the configurable range required for checkpoint 4.1)

Level AA

(what about a AA requirement for a user command to animate or otherwise 
highlight where the content focus currently is?)

Level AAA






Jan Richards wrote:
> 
> As per my action item from last week 
> (http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0022.html):
> 
> POTENTIAL NEW WORDING for 10.2:
> 
> 10.2 Highlight selection, content focus, enabled elements, visited links
> 
> Level A
> 
> 1. Highlighting options are provided for the following classes of 
> information:
> (a) selection
> (b) content focus (except when "recognized" as "content-controlled")
> (c) enabled elements (except when "recognized" as "content-controlled")
> (d) recently visited links.
> 
> 2. The highlighting options include:
> (a) For text: Platform standard ranges for:
> - Text foreground and background colors
> - Text size
> - Text decoration (e.g., underlining)
> - Border thickness
> - Border color
> (b) For non-text content: Platform standard ranges for:
> - Border thickness
> - Border color
> 
> Level AA
> 
> 3. The highlighting options include:
> (a) For text: Platform standard ranges for:
> - Font face
> - Font family
> (b) For  non-text content: Platform standard ranges for:
> - Foreground and background colors (if applicable)
> - Line width (if applicable)
> 
> Level AAA
> 
> N/A
> 
> 
> 
> 
> ==========================================================
> CURRENT WORDING:
> 
> 10.2 Highlight selection, content focus, enabled elements, visited links 
> (P1)
> 
> 1. Allow global configuration to highlight the following four classes of 
> information in each viewport: the selection, content focus, enabled 
> elements, and recently visited links.
> 
> 2. For graphical user interfaces, as part of satisfying provision one of 
> this checkpoint, allow at least one configuration where the highlight 
> mechanisms for the four classes of information:
> - differ from each other, and
> - do not rely on rendered text foreground and background colors alone.
> 
> 3. For graphical user interfaces, as part of satisfying provision one of 
> this checkpoint, if a highlight mechanism involves text size, font 
> family, rendered text foreground and background colors, or text 
> decorations, offer at least the following range of values:
> - for text size, the range required by provision three of checkpoint 4.1.
> - for font family, the range required by provision three of checkpoint 4.2.
> - for text foreground and background colors and decorations, the range 
> offered by the conventional utility available in the operating 
> environment for users to choose rendered text colors or decorations 
> (e.g., the standard font and color dialog box resources supported by the 
> operating system). If no such utility is available, the range supported 
> by the conventional APIs of the operating environment for specifying 
> text colors or drawing text.
> 
> 4. Highlight enabled elements according to the granularity specified in 
> the format. For example, an HTML user agent rendering a PNG image as 
> part of a client-side image map is only required to highlight the image 
> as a whole, not each enabled region. An SVG user agent rendering an SVG 
> image with embedded graphical links is required to highlight each 
> (enabled) link that may be rendered independently according to the SVG 
> specification.
> 

-- 
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
Received on Thursday, 31 January 2008 20:18:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:53 GMT