W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

Re: Current suggestion for subheading isn't accessible

From: Ian Yang <ian@invigoreight.com>
Date: Wed, 8 May 2013 16:19:08 +0800
Message-ID: <CABr1FsfO852yc7owKmnxtwg2uYupNDxrR9AKUZTmi5h43WQHOQ@mail.gmail.com>
To: Olaf Drümmer <olaf@druemmer.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
On Wed, May 8, 2013 at 3:46 PM, Olaf Drümmer <olaf@druemmer.com> wrote:
> How does a sighted know it's definitely a heading plus a subheading, as opposed to a heading happening to have a colon inside it, and being spread over two lines (or more)?

Yes. That can be another reason that the first two examples in spec
are problematic.

> If a non-sighted users really wanted to get at it, he would have to pick up additional information, like differences in font size or face, color. This is technically feasible.

But unworkable? Relying on CSS to indicate semantics is not a good
choice as developers may wrap heading text with <span>s and style them
in any way.

> (snip) taking into account that once subheading is introduced there would be many other potential new tags that might have to be introduced (snip)
> All in all I can't see a reason why this needs to be addressed by adding a specific tag.
> Olaf

Yes. Introducing a new element might lead to introductions of other
potential new elements, and that sometimes can affect the credibility
and many other respects of HTML5. So for marking up
subheading/subtitle, could you please advise?

Ian Yang
Received on Wednesday, 8 May 2013 08:19:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC