Re: accessibility support for nested h1 in sections?

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.

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>

Received on Sunday, 24 January 2016 12:45:53 UTC