W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2016

Re: accessibility support for nested h1 in sections?

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sun, 24 Jan 2016 12:44:45 +0000
Message-ID: <CA+ri+VkFofGOXG8u46EEr83Exhz4d=mNjjtpGn105SuPSYT6Aw@mail.gmail.com>
To: Mike Elledge <melledge@yahoo.com>
Cc: "Patrick H. Lauke" <redux@splintered.co.uk>, WAI Interest Group <w3c-wai-ig@w3.org>
On 23 January 2016 at 18:10, Mike Elledge <melledge@yahoo.com> wrote:

> So would the appropriate way for a screen reader to respond be to state
> "Section X" followed by "heading level one" in a flat H1 scenario?
> This doesn't seem like rocket science; why hasn't it been implemented by
> browsers?

Section elements are not reported unless that have an explicit accessible
name, as the unfettered announcement of <section> elements was found to
cause verbosity problems for users as developers overuse <section>
elements, often using them instead of <div>s.



Current Standards Work @W3C
Received on Sunday, 24 January 2016 12:45:53 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 January 2016 16:39:04 UTC