W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2012

RE: FORMAL OBJECTION (was RE: Working Group Decision on ISSUE-204 aria-hidden)

From: John Foliot <john@foliot.ca>
Date: Mon, 13 Aug 2012 21:01:07 -0700
To: "'Sam Ruby'" <rubys@intertwingly.net>
Cc: <public-html@w3.org>, "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>
Message-ID: <025001cd79d1$708bfa80$51a3ef80$@ca>
Thank you. Please note that currently that page reads: "ISSUE-204 poster-alt
#" (1st cell in the row).

JF


> -----Original Message-----
> From: Sam Ruby [mailto:rubys@intertwingly.net]
> Sent: Monday, August 13, 2012 8:04 PM
> To: John Foliot
> Cc: public-html@w3.org; 'HTML Accessibility Task Force'
> Subject: Re: FORMAL OBJECTION (was RE: Working Group Decision on ISSUE-
> 204 aria-hidden)
> 
> Duly recorded:
> 
> http://dev.w3.org/html5/status/formal-objection-status.html#ISSUE-204
> 
> - Sam Ruby
> 
> On 08/13/2012 10:28 PM, John Foliot wrote:
> > Sam Ruby wrote:
> >>
> >>     * Assertion of "harmful behaviors" is also not sufficiently
> >> supported
> >>       by evidence.  In particular, it makes a claim that has
> previously
> >>       been disputed, and without a single example of such markup.
> >
> > It is impossible to demonstrate harmful behaviors in a technology
> that has
> > yet to surface - this is a ludicrous statement.
> >
> > Placing a <a href>Link</a> inside an @hidden container MUST still
> take tab
> > focus for a non-sighted user and their Assistive Technology to
> interact with
> > it, yet at the same time hides that focus from the sighted user: this
> is
> > simple logic. Proving the harm of this is currently impossible due to
> lack
> > of implementation anywhere: conversely however no one has been able
> to prove
> > that this is NOT harmful.
> >
> > Allowing tab-focusable content to reside inside of a container that
> is
> > specifically hidden to any other user, including a sighted, key-board
> only
> > user, is harmful because that sighted user will lose track of their
> tab
> > focus, with no other means of knowing where their cursor is.
> >
> > This is a direct contravention of a WCAG 2 AA Requirement:
> >
> > 	"2.4.7 Focus Visible: Any keyboard operable user interface has a
> > mode of operation where the keyboard focus indicator is visible."
> > http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-mechanisms-
> focus-v
> > isible
> >
> > Therefore, implementation of this Change Proposal is a Direct and
> Willful
> > Violation of the existing WCAG Specification, and the basis of My
> Formal
> > Objection. I do not believe that the HTML5 WG should be violating
> such an
> > important W3C Recommendation (one which countless countries and
> industries
> > have based their entire on-line accessibility requirements - whether
> > policies or legislation - upon).
> >
> >
> > John Foliot
> >
Received on Tuesday, 14 August 2012 04:01:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 August 2012 04:01:47 GMT