W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > October 2013

Re: If there is a focusable element inside a div then the onkeypress works ( LC-2849)

From: <akirkpat@adobe.com>
Date: Tue, 08 Oct 2013 18:45:58 +0000
Message-Id: <E1VTcIA-0007Vu-A9@jessica.w3.org>
To: David MacDonald <david100@sympatico.ca>
Cc: public-comments-wcag20@w3.org
 Dear David MacDonald ,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the Techniques
for WCAG 2.0 published on 5 Sep 2013. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org if you agree with it or not before 22 October
2013. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1. http://www.w3.org/mid/E1VGIrD-0000Ar-3y@crusher.w3.org
 2. http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/


=====

Your comment on F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to
using scripting e...:
> an example is http://www.ottawapolice.ca
> there is a search form in the top left. The input tag is inside a div.
> The input gets focus... and when someone hits the enter key from there
> the containing div fires the go button and does the search. It
> technically fails because it is an onkeypress on a non focusable
> element... but it didn't seem to fail ... it accepted tab focus, showed
> up as a form, and responded to a keypress
> <div id="ctl00_Header1_Panel1" onkeypress="javascript:return
> WebForm_FireDefaultButton(event, 'ctl00_Header1_ib_go')">
> <input name="ctl00$Header1$queryText" type="text" value="search"
> id="ctl00_Header1_queryText" class="sf_searchText"
> onFocus="clearSearchBox(this)" />
>                 <input type="image" name="ctl00$Header1$ib_go"
> id="ctl00_Header1_ib_go" title="Go button for Search field"
> Text="Search" alt="Search" class="sf_searchSubmit"
> src="/App_Images/navigation/primary/go_en.png" style="border-width:0px;"
> />
>             
> </div>
> 
> Proposed Change:
> Recommend, amend the language of example number 4.
> 
> In the body of the technique insert a line that says. 
> "If there is a focusable element inside a div that has an onkeypress,
> such as an input, which is recognized by Assistive technology, then it
> would NOT be a failure because the containing DIV will respond to the
> focusable, recognized element.
> 
> Add the following example or something like it to SCR35:
> 
> <div id="ctl00_Header1_Panel1" onkeypress="javascript:return
> WebForm_FireDefaultButton(event, 'ctl00_Header1_ib_go')">
> <input name="ctl00$Header1$queryText" type="text" value="search"
> id="ctl00_Header1_queryText" class="sf_searchText"
> onFocus="clearSearchBox(this)" />
>  <input type="image" name="ctl00$Header1$ib_go" id="ctl00_Header1_ib_go"
> title="Go button for Search field" Text="Search" alt="Search"
> class="sf_searchSubmit" src="/App_Images/navigation/primary/go_en.png"
> style="border-width:0px;" />        
> </div>


Working Group Resolution (LC-2849):
Thanks for your comment and suggest example/code. 

The example you cite is a form control, not a link and the failure refers
to emulating links using scripting.  As a result, this failure would not
apply in the situation discussed in the comment so we will leave the
failure as written.


----
Received on Tuesday, 8 October 2013 18:46:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:17 UTC