<trackbot> Date: 05 December 2012

level A are those that serve that are completely or serious blocked from accessing information and is technically feasible to do.

level AA - go to wcag 1 definition

what is difference between technically feasible versus undue burden

kf: are we going to define undue burden...more than one developer, x% of cost based on market conditions, ???

kp: get real world examples from companies.

from wcag

trackbot start meeting

trackbot, start meeting

<trackbot> Meeting: User Agent Accessibility Guidelines Working Group Teleconference

<trackbot> Date: 05 December 2012

[Priority 1]

A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.

[Priority 2]

A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.

[Priority 3]

A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.

kf: need to have some level of thought behind our definitions.

kp: to many...undue burden is anything I don't want to do.
... not testable, not normative
... anonymous realworld examples.

A levels reasonable amount of time. hours to days, AA level days to weeks, AAA level weeks to months to year

graduate student projects to write extensions - keep track of hours for eamples

js: want something that is easy to explain and is understandable

a company has x amount of developer hours available in a year. they have set as a policy to dedicate 5% of their time to accessibility. and have divided up the task to include several things that can be completed this year (before the next release) and work on some longer term items iteratively improving the accessibility of thier browser

things we need to work on

levels, @@, action items.

<jeanne> conformance, definition levels

Level A are those that serve that are completely or serious blocked from accessing information and is technically feasible to do.

wcag - A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.

<jeanne> Level A success criteria address accessibility problems that block people with disabilities from accessing information and is technically feasible for the vendor to implement.

A browser developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access web content. This checkpoint is technically feasible to do in a timely fashion.

Level A success criteria address accessibility problems that completely or seriously block people with disabilities from accessing and interacting with content or interface and is technically feasible for the vendor to implement.

<KimPatch> Success criteria address accessibility problems that

<KimPatch> - completely or seriously block people with disabilities from accessing and interacting with content or the interface and

<KimPatch> - is technically feasible for the vendor to implement

<jeanne> Level AA success criteria provide broad accessibility to many people with disabilities and are technically feasible.

<jeanne> Level AAA success criteria address accessibility for specific groups of people with disabilities or are technically challenging to implement.

<jeanne> Level AA success criteria provide accessibility solutions to people with diverse disabilities and are technically feasible.

<jeanne> Level AAA success criteria address accessibility for specific groups of people with disabilities and are technically challenging to implement.

Level A Success criteria address accessibility problems that

- completely or seriously block people with disabilities from accessing and interacting with content or the interface and

- are technically feasible for the vendor to implement

Level AA success criteria provide accessibility solutions to people with diverse disabilities and are technically feasible.

Level AAA success criteria address accessibility for specific groups of people with disabilities and are technically challenging to implement.

Level A Success criteria address accessibility problems that

- completely or seriously block people with disabilities from accessing and interacting with content or the interface and

- are technically feasible for the vendor to implement

Level AA success criteria provide accessibility solutions to people with diverse disabilities and are feasible to implement.

Level AAA success criteria address accessibility for specific groups of people with disabilities and are challenging to implement.

<KimPatch> Level A Success criteria address accessibility problems that block people with disabilities from accessing or interacting with interface or content and

<KimPatch> are technically feasible for the vendor to implement

Level A Success criteria address accessibility problems that block people with disabilities from interacting with the interface or content and are technically feasible for the vendor to implement

Level AA success criteria provide accessibility solutions to people with diverse disabilities and are feasible to implement.

Level AAA success criteria address accessibility for specific groups of people with disabilities and are challenging to implement.

a company has x amount of developer hours available in a year. they have set as a policy to dedicate 5% of their time to accessibility. and have divided up the task to include several things that can be completed this year (before the next release) and work on some longer term items iteratively improving the accessibility of thier browser

title: UAWG editors call

This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: JAllan
Inferring Scribes: JAllan

WARNING: No "Topic:" lines found.

Default Present: Jeanne, Jim_Allan, Kim_Patch, Kelly
Present: Jeanne Jim_Allan Kim_Patch Kelly

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 05 Dec 2012
Guessing minutes URL: http://www.w3.org/2012/12/05-ua-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report