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

Re: Action-352 Write IER for 3.1.4 (modify 3.1.2)

From: Greg Lowney <gcl-0039@access-research.org>
Date: Thu, 29 Apr 2010 22:17:26 -0800
Message-ID: <4BDA75F6.2020408@access-research.org>
CC: 'WAI-UA list' <w3c-wai-ua@w3.org>
1. In addition to the alternative content (such as those listed) include 
things like image file name, or would that be considered repair content? 
If the latter, should the user be able to prioritize repair content 
along with the different forms of alternative content?

2. Similarly, would the primary (non-alternative) content be in this 
list? For example, might a user want to prioritize presentation of an 
image as the alt text, if that's not available the title text, and if 
not available the image itself, and if that's not available the file 
name? A more reasonable example, given a technology that supported it, 
would be to choose the low-resolution preview image first, if none is 
available the full size image, and if that's not available the alt text, 

3. Don't forget to use the language we adopted for 3.1.2 "and, in cases 
where the alternative content has different dimensions than the original 
content, how the layout/reflow of the document should be handled."

4. Typo in "Mona Lisa".

5. In the first example, it might be useful to give more details of a 
sample user interface, such as having a list box containing name of the 
supported attributes (image, alt text, long desc, file name, etc.), and 
controls that let the user rearrange the order by moving selected items 
up or down in the list.

6. Also in the first example, might change "and that the document should 
reflow..." to "and a check box allowing the user to choose whether the 
document should reflow to accommodate the alternative content or be 
truncated to preserve the original layout."

7. The definitions of repair content and text content refer to WCAG10; 
should that be updated to WCAG20?

-------- Original Message  --------
Subject: Action-352 Write IER for 3.1.4 (modify 3.1.2)
From: Jim Allan <jimallan@tsbvi.edu>
To: 'WAI-UA list' <w3c-wai-ua@w3.org>
Date: 4/22/2010 8:45 AM
> 3.1.4 Rendering Alternative (Enhanced): Provide the user with the global
> option to configure a cascade of types of alternatives to render by default,
> in case a preferred type is unavailable. If the alternative content has a
> different height or width, then the user agent will reflow the viewport.
> (Level AA)
> #  Intent of Success Criterion 3.1.4:
> This is an enhancement of 3.1.2 Configure Default Rendering. The author may
> provide several pieces of alternative content. For example, an image of the
> Mona Liza may have some combination of the following alternative content: a
> low resolution image, a high resolution image, a title using the title
> attribute, a short description using the alt attribute, a detailed longer
> description using the longdesc attribute. This SC allows the user to
> globally set not only a default rendering for the image, but to also specify
> if choice 1 is not provided by the author the choice 2 is rendered and so
> forth down the list of user selected options for rendering. This is a global
> option because it would be an unreasonable burden for the user to have to
> change the rendering options every time they visit a new page.
> # Examples of Success Criterion 3.1.4:
>      * In the browser's preferences dialog box, a user specifies that they
> want alternatives rendered in the following order of preference, if the
> selected alternative is not available choose the next item on the list until
> all options have been exhausted
> 1. Alt text displayed in place of images
> 2. title text displayed in place of images
> 3. longdesc link is displayed in place of image
> 4. high resolution image
> and that the document should reflow to allow the displayed alternative to be
> displayed rather than truncated. Note: Item 1 would be the default and
> satisfy 3.1.2
>      * In the browser's preferences dialog box, a user assigns a number to
> the available alternatives supported by the user agent, and thus establishes
> the cascade of alternative ("fallback") content to display the for embedded
> objects, such as videos. The first item in the cascade would be the default.
> Jim Allan, Accessibility Coordinator&  Webmaster
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Friday, 30 April 2010 05:18:04 UTC

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