19:59:39 RRSAgent has joined #html-techs-tf 19:59:39 logging to http://www.w3.org/2013/06/06-html-techs-tf-irc 19:59:41 RRSAgent, make logs public 19:59:43 Zakim, this will be WAI_WCAG 19:59:43 ok, trackbot; I see WAI_WCAG()4:00PM scheduled to start in 1 minute 19:59:44 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 19:59:44 Date: 06 June 2013 20:00:37 WAI_WCAG()4:00PM has now started 20:00:44 +James_Nurthen 20:01:15 -James_Nurthen 20:01:15 +James_Nurthen 20:01:15 +Cooper 20:02:18 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2013AprJun/0075.html 20:02:18 chair: James_Nurthen 20:02:51 jamesn_ has joined #html-techs-tf 20:03:05 +Paul_Adam 20:03:18 pauljadam has joined #html-techs-tf 20:03:18 meeting: HTML5 and WAI-ARIA WCAG Techniques Task Force 20:03:34 http://pauljadam.com/demos/aria-alert-validation.html 20:03:47 https://www.w3.org/2002/09/wbs/35422/aria060613/results 20:04:08 http://www.w3.org/WAI/GL/wiki/Using_ARIA_Live_Regions_or_role%3Dalert_to_Identify_Errors#Examples 20:06:31 adam_solomon has joined #html-techs-tf 20:07:00 +[IPcaller] 20:07:28 zakim, IPcaller is Adam_Solomon 20:07:28 +Adam_Solomon; got it 20:10:02 scribe:pauljadam 20:10:17 https://www.w3.org/2002/09/wbs/35422/aria060613/results#xlabel 20:10:29 F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML 20:15:10 marcjohlic has joined #html-techs-tf 20:15:33 +Marc_Johlic 20:16:37 edit done 20:18:19 discussion about adding tabindex to F59 20:21:03 jamesn_ if F59 is changed to include tab index then lack of role fails 4.1.2, lack of tab index fails 2.1.1 20:22:02 MIchaelC: have a separate failure for lack of tab index rather than combining F59 20:23:28 http://www.w3.org/TR/WCAG20-TECHS/failures.html#F54 20:23:47 jamesn_: can we put the tabindex into F54? 20:25:38 discussion that tabindex should not be added to F59, consensus is that we can make this change 20:27:18 Detlev to edit F59 to remove tab index disussion. Either find a new failure for tabindex or roll into F54 or F42. 20:28:57 discussion that tabindex=0 will make an element focusable 20:30:43 jamesn_: discussion about a map page where keyboard user would use a select input to choose a state but a sighted user might click on the actual map of the state 20:32:07 jamesn_: sometimes it's more complicated to make the visual user interface accessible than to just provide an accessible alternative that works the same 20:33:03 jamesn_: want to make sure that this technique does not outlaw use of alternative accessible interfaces to a visual interface that would be very difficult to make accessible 20:34:15 discussion to change failure to say unless an alternative user interface is provided 20:35:03 MichaelC: need to make sure failures cannot be overridden 20:35:36 If those elements are acting as user interface controls, check that either the role of the control is defined or an alternative method is provided to provide the same functionality. 20:36:42 adam_solomon: edited the test procedure step 2 to allow use of alternative user interface for the inaccessible control 20:37:41 jamesn_: also remove the test procedure step 3 to eliminate tabindex as a check 20:40:20 discussion on whether to remove tabindex check in test procedure step 3 20:42:17 adam_solomon: will revisit removing the tabindex check from test procedure step 3 20:42:44 action: adam to revisit removing the tabindex check from test procedure step 3 in F59 20:42:44 'adam' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., padam2, asolomon). 20:42:58 action: asolomon to revisit removing the tabindex check from test procedure step 3 in F59 20:42:59 Created ACTION-203 - Revisit removing the tabindex check from test procedure step 3 in F59 [on Adam Solomon - due 2013-06-13]. 20:43:32 http://www.w3.org/WAI/GL/wiki/ARIA-edit:_F63:_Failure_of_Success_Criterion_2.4.4_due_to_providing_link_context_only_in_content_that_is_not_related_to_the_link 20:43:41 Moving on to F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link 20:44:37 adam_solomon: example 3, is it saying this is a failure? 20:45:55 discussion about definition list support in screen readers 20:47:22 discussion about yes you can have 2
per
20:48:12 adam_solomon: does at support relationship between
and
? 20:49:12 discussion that this should work but not sure if screen readers support
20:49:48 http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS/H48.html 20:51:21 discussion that we all think
should work but screen readers have bad support for definition lists 20:51:57 discussion about link purpose and headings 20:53:05 discussion about navigating via links list with 3 click here links and how do you determine link purpose 20:54:03 jamesn_: prepared to leave definition list example in the failure F63 20:56:47 discussion about removing failure example of using definition lists in F63 20:58:45 adam_solomon: implementing MichaelC's comment suggestion in F63 21:00:04 -Adam_Solomon 21:00:17 -Cooper 21:00:19 -Marc_Johlic 21:00:34 leaving. As of this point the attendees were James_Nurthen, Cooper, Paul_Adam, Adam_Solomon, Marc_Johlic 21:00:34 Zakim has left #html-techs-tf 21:00:53 rrsagent, make minutes 21:00:53 I have made the request to generate http://www.w3.org/2013/06/06-html-techs-tf-minutes.html pauljadam 21:04:11 http://www.w3.org/2013/06/06-html-techs-tf-minutes.html,text 21:06:18 rssagent, please part 21:06:35 rrsagent, please part 21:06:35 I see 2 open action items saved in http://www.w3.org/2013/06/06-html-techs-tf-actions.rdf : 21:06:35 ACTION: adam to revisit removing the tabindex check from test procedure step 3 in F59 [1] 21:06:35 recorded in http://www.w3.org/2013/06/06-html-techs-tf-irc#T20-42-44 21:06:35 ACTION: asolomon to revisit removing the tabindex check from test procedure step 3 in F59 [2] 21:06:35 recorded in http://www.w3.org/2013/06/06-html-techs-tf-irc#T20-42-58