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

Re: 48-Hour Consensus Call: Issue-204 Change Proposal

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Wed, 25 Apr 2012 07:48:14 +0100
Message-ID: <CAEhSh3fd-H5qvwsEMV8Qyc=m=i24L4NHtnnssB=EzgpSbW4mhw@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
On Wed, Apr 25, 2012 at 5:44 AM, Janina Sajka <janina@rednote.net> wrote:
> Colleagues:
> On 26 April next the HTML-A11Y Task Force teleconference meeting
> will consider consensus support of the Issue-204 Change Proposal at:
> http://www.w3.org/html/wg/wiki/Correct_Hidden_Attribute_Section_v2
> As usual, if there is objection in the Task Force to such a consensus
> position, please respond by replying to this message no later than close
> of business, Boston Time, on Friday 27 April.

Yes, I object to a CP that makes it conforming to hide labels and
short descriptions with @hidden, as I don't believe a persuasive case
has been made that this helps users or authors. In fact, not one
example has been produced that anyone claims wouldn't be better
addressed with a label or description capable of being made visible by
changing user agent preferences.

In addition, even if I agreed that hiding labels and short
descriptions with @hidden should be made conforming, I'd have to
object on details of the proposed spec text as it currently stands,

   * It contradicts normative requirements of the HTML specification,
e.g. with respect to what happens when a link to hidden content is

   * It contradicts normative requirements of the WAI-ARIA
specification, e.g. with respect to how accessible names and
descriptions are calculated.

   * It fails to specify what user agents should do when @hidden and
@aria-hidden="true" are set on an element.

   * It introduces new conformance requirements about not using
@hidden for structured content with vague and confusing language.

Even if I had no problems with the spec text, I'd be inclined to
object on the basis of the rationale. I think it's important to
provide the wider working group with persuasive rationales in our
Change Proposals, but the examples provided do not have good usability
characteristics for users or maintainability characteristics for
authors, and so they undermine the rationale.

Benjamin Hawkes-Lewis
Received on Wednesday, 25 April 2012 06:49:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:28 UTC