Re: Making "recognized" a high level condition in UAAG2

list of SC effected by Jan's proposal
the SC need to be reworded.

1.1.1
1.1.x
1.1.3 b c
1.1.5
1.3.1 c
2.2.1
2.3.2
2.3.5
2.6.1
2.9.1
2.10.1
2.10.2
gl 2.11
2.11.2
3.1.2
3.2.1
3.2.2
3.2.4
def of caption
def of script

jim


On Thu, Feb 7, 2013 at 11:19 AM, Jim Allan <jimallan@tsbvi.edu> wrote:

> Jan,
> Thanks for this. I like it. I will provide a list of SC to fix in a few
> minutes
>
> Jim
>
>
> On Thu, Feb 7, 2013 at 9:03 AM, Richards, Jan <jrichards@ocadu.ca> wrote:
>
>> Hi all,
>>
>> On the Jan 31 call, Jim took this action:
>> ACTION-798: Review 'recognized' in SC to make a top level statement
>> similar to device independence at the beginning of the document - perhaps
>> an applicability note and something in a conformance claim..(
>> https://www.w3.org/WAI/UA/tracker/actions/798)
>>
>> And Eric's excellent review also highlights the repetition of
>> "recognized".
>>
>> I'd like to suggest the following "ported" ATAG2 wording along with a few
>> other relevant high level conditions:
>>
>> 1. Unrecognizable content: Any success criteria that refer to semantic
>> features of web content  (e.g., text alternatives to non-text content,
>> headings, keyboard commands, time limits, etc.) will only apply when those
>> features are implemented according to standard semantics for the web
>> content technology. When those features are implemented via other means
>> (e.g., custom scripting), the content features are not considered
>> recognizable and the success criteria do not apply.
>>
>> 2. User agent  systems: As per the UAAG 2.0 definition of user agent,
>> several software tools (identified in any conformance claim) can be used in
>> conjunction to meet the requirements. For example, a base user agent could
>> make use of plug-in to provide certain functionality and a web-based user
>> agent may rely on base user agent features (e.g., keyboard navigation, find
>> functions, etc.).
>>
>> 3. Developer control: The success criteria only apply to the user agent
>> user interface as it is provided by the developer. They do not apply to any
>> subsequent modifications by parties other than the developer (e.g., user
>> modifications of default settings, third-party plug-ins).
>>
>> Cheers,
>> Jan
>>
>>
>> (MR) JAN RICHARDS
>> PROJECT MANAGER
>> INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
>> OCAD UNIVERSITY
>>
>> T 416 977 6000 x3957
>> F 416 977 9844
>> E jrichards@ocadu.ca
>>
>>
>>
>>
>
>
> --
> 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
>



-- 
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 Thursday, 7 February 2013 17:29:59 UTC