See also: IRC log
<trackbot> Date: 06 June 2013
<MichaelC> meeting: HTML5 and WAI-ARIA WCAG Techniques Task Force
http://pauljadam.com/demos/aria-alert-validation.html
<jamesn_> https://www.w3.org/2002/09/wbs/35422/aria060613/results
http://www.w3.org/WAI/GL/wiki/Using_ARIA_Live_Regions_or_role%3Dalert_to_Identify_Errors#Examples
<jamesn_> scribe:pauljadam
<jamesn_> https://www.w3.org/2002/09/wbs/35422/aria060613/results#xlabel
<jamesn_> F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML
<adam_solomon> edit done
discussion about adding tabindex to F59
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
MIchaelC: have a separate failure for lack of tab index rather than combining F59
<jamesn_> http://www.w3.org/TR/WCAG20-TECHS/failures.html#F54
jamesn_: can we put the tabindex into F54?
discussion that tabindex should not be added to F59, consensus is that we can make this change
<jamesn_> Detlev to edit F59 to remove tab index disussion. Either find a new failure for tabindex or roll into F54 or F42.
discussion that tabindex=0 will make an element focusable
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
... sometimes it's more complicated to make the visual user
interface accessible than to just provide an accessible
alternative that works the same
... 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
discussion to change failure to say unless an alternative user interface is provided
MichaelC: need to make sure failures cannot be overridden
<jamesn_> 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.
adam_solomon: edited the test procedure step 2 to allow use of alternative user interface for the inaccessible control
jamesn_: also remove the test procedure step 3 to eliminate tabindex as a check
discussion on whether to remove tabindex check in test procedure step 3
adam_solomon: will revisit removing the tabindex check from test procedure step 3
<jamesn_> ACTION: adam to revisit removing the tabindex check from test procedure step 3 in F59 [recorded in http://www.w3.org/2013/06/06-html-techs-tf-minutes.html#action01]
<trackbot> 'adam' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., padam2, asolomon).
<jamesn_> ACTION: asolomon to revisit removing the tabindex check from test procedure step 3 in F59 [recorded in http://www.w3.org/2013/06/06-html-techs-tf-minutes.html#action02]
<trackbot> Created ACTION-203 - Revisit removing the tabindex check from test procedure step 3 in F59 [on Adam Solomon - due 2013-06-13].
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
adam_solomon: example 3, is it saying this is a failure?
discussion about definition list support in screen readers
discussion about yes you can have 2 <dd> per <dt>
adam_solomon: does at support relationship between <dt> and <dd>?
discussion that this should work but not sure if screen readers support <dt><dd>
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS/H48.html
discussion that we all think <dt><dd> should work but screen readers have bad support for definition lists
discussion about link purpose and headings
discussion about navigating via links list with 3 click here links and how do you determine link purpose
jamesn_: prepared to leave definition list example in the failure F63
discussion about removing failure example of using definition lists in F63
adam_solomon: implementing MichaelC's comment suggestion in F63
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: pauljadam Inferring ScribeNick: pauljadam WARNING: No "Topic:" lines found. Default Present: James_Nurthen, Cooper, Paul_Adam, Adam_Solomon, Marc_Johlic Present: James_Nurthen Cooper Paul_Adam Adam_Solomon Marc_Johlic Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2013AprJun/0075.html Found Date: 06 Jun 2013 Guessing minutes URL: http://www.w3.org/2013/06/06-html-techs-tf-minutes.html People with action items: adam asolomon 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[End of scribe.perl diagnostic output]