17:59:27 RRSAgent has joined #ua 17:59:27 logging to http://www.w3.org/2012/12/05-ua-irc 17:59:29 RRSAgent, make logs public 17:59:29 Zakim has joined #ua 17:59:31 Zakim, this will be WAI_UAWG 17:59:31 I do not see a conference matching that name scheduled within the next hour, trackbot 17:59:32 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 17:59:32 Date: 05 December 2012 18:13:54 KimPatch has joined #ua 18:13:58 JAllan has joined #ua 18:18:19 level A are those that serve that are completely or serious blocked from accessing information and is technically feasible to do. 18:18:42 level AA - go to wcag 1 definition 18:19:46 what is difference between technically feasible versus undue burden 18:21:04 kf: are we going to define undue burden...more than one developer, x% of cost based on market conditions, ??? 18:21:28 kp: get real world examples from companies. 18:22:55 from wcag 18:23:01 trackbot start meeting 18:23:13 trackbot, start meeting 18:23:15 RRSAgent, make logs public 18:23:17 Zakim, this will be WAI_UAWG 18:23:17 I do not see a conference matching that name scheduled within the next hour, trackbot 18:23:18 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 18:23:18 Date: 05 December 2012 18:23:37 rrsagent, set logs public 18:23:49 [Priority 1] 18:23:50 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. 18:23:52 [Priority 2] 18:23:53 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. 18:23:55 [Priority 3] 18:23:56 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. 18:24:59 kf: need to have some level of thought behind our definitions. 18:25:22 kp: to many...undue burden is anything I don't want to do. 18:25:39 kp: not testable, not normative 18:26:59 ... anonymous realworld examples. 18:30:26 A levels reasonable amount of time. hours to days, AA level days to weeks, AAA level weeks to months to year 18:32:15 graduate student projects to write extensions - keep track of hours for eamples 18:33:17 js: want something that is easy to explain and is understandable 18:35:49 zakim, who is here? 18:35:49 sorry, jeanne, I don't know what conference this is 18:35:50 On IRC I see JAllan, KimPatch, Zakim, RRSAgent, jeanne, trackbot 18:35:55 zakim, this is UA 18:35:55 ok, jeanne; that matches Team_(ua)18:00Z 18:36:16 zakim, who is here? 18:36:16 On the phone I see Jeanne, Jim_Allan, Kim_Patch, [Microsoft] 18:36:17 On IRC I see JAllan, KimPatch, Zakim, RRSAgent, jeanne, trackbot 18:36:31 zakim, Microsoft is Kelly 18:36:31 +Kelly; got it 18:36:52 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 18:37:03 rrsagent, make minutes 18:37:03 I have made the request to generate http://www.w3.org/2012/12/05-ua-minutes.html JAllan 18:39:10 things we need to work on 18:39:32 levels, @@, action items. 18:40:28 conformance, definition levels 18:41:59 Level A are those that serve that are completely or serious blocked from accessing information and is technically feasible to do. 18:43:00 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. 18:44:47 Level A success criteria address accessibility problems that block people with disabilities from accessing information and is technically feasible for the vendor to implement. 18:45:10 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. 18:48:16 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. 18:51:22 Success criteria address accessibility problems that 18:51:24 - completely or seriously block people with disabilities from accessing and interacting with content or the interface and 18:51:26 - is technically feasible for the vendor to implement 18:52:56 Level AA success criteria provide broad accessibility to many people with disabilities and are technically feasible. 18:54:04 Level AAA success criteria address accessibility for specific groups of people with disabilities or are technically challenging to implement. 18:55:57 Level AA success criteria provide accessibility solutions to people with diverse disabilities and are technically feasible. 18:56:18 Level AAA success criteria address accessibility for specific groups of people with disabilities and are technically challenging to implement. 18:57:15 Level A Success criteria address accessibility problems that 18:57:17 - completely or seriously block people with disabilities from accessing and interacting with content or the interface and 18:57:18 - are technically feasible for the vendor to implement 18:57:20 Level AA success criteria provide accessibility solutions to people with diverse disabilities and are technically feasible. 18:57:21 Level AAA success criteria address accessibility for specific groups of people with disabilities and are technically challenging to implement. 18:59:58 Level A Success criteria address accessibility problems that 19:00:00 - completely or seriously block people with disabilities from accessing and interacting with content or the interface and 19:00:01 - are technically feasible for the vendor to implement 19:00:03 Level AA success criteria provide accessibility solutions to people with diverse disabilities and are feasible to implement. 19:00:04 Level AAA success criteria address accessibility for specific groups of people with disabilities and are challenging to implement. 19:00:17 -Kelly 19:01:13 Level A Success criteria address accessibility problems that block people with disabilities from accessing or interacting with interface or content and 19:01:14 are technically feasible for the vendor to implement 19:02:04 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 19:02:06 Level AA success criteria provide accessibility solutions to people with diverse disabilities and are feasible to implement. 19:02:07 Level AAA success criteria address accessibility for specific groups of people with disabilities and are challenging to implement. 19:09:39 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 19:10:47 rrsagent, make minutes 19:10:47 I have made the request to generate http://www.w3.org/2012/12/05-ua-minutes.html JAllan 19:12:27 -Kim_Patch 19:13:03 zakim, please part 19:13:03 leaving. As of this point the attendees were Jeanne, Jim_Allan, Kim_Patch, Kelly 19:13:03 Zakim has left #ua 19:13:37 rrsagent, make minutes 19:13:37 I have made the request to generate http://www.w3.org/2012/12/05-ua-minutes.html JAllan 19:14:20 title: UAWG editors call 19:14:23 rrsagent, make minutes 19:14:23 I have made the request to generate http://www.w3.org/2012/12/05-ua-minutes.html JAllan 19:15:02 rrsagent, please part 19:15:02 I see no action items