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: Tue, 7 May 2013 23:47:57 +0800
Message-ID: <CABr1Fsczp5VomyrjdOyLSLD9=xitaOzs-wHFxsn4ihObv95jsA@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
On Tue, May 7, 2013 at 11:35 PM, Steve Faulkner
<faulkner.steve@gmail.com> wrote:
> Hi Ian,
>> There still need to be an HTML element for subheading/subtitle,
>> otherwise screen readers will never have a chance to know the
>> subheading/subtitle.
> since there is no defined subtitle role in accessibility APIs i suggest a
> first step would be to see if there is interest in adding one.
> probably a good place to start would be in ARIA you can suggest it on the
> wai-xtech mailing list

Imho, introduce a new element is better than introduce a new ARIA role
because a new element covers for both HTML semantics and

>>>  in the second example the album name is also on a new line (which is
>>>  conveyed to screen reader users)
>> Could you please explain that? Do you mean screen reader users get
>> notified of line breaks in HTML code?
> screen readers discern line breaks in text on the page, also some browsers
> (e.g. firefox) indicate the semantics of an element with display:block style
> as IA2 role=paragraph.
> --
> Regards
> SteveF
> HTML 5.1

What if a paragraph is markup by a newbie developer as the following?
Will screen readers announce all line breaks?


Ian Yang
Received on Tuesday, 7 May 2013 15:48:28 UTC

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