W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23545] section should only map to region if the section has an accessible name

From: <bugzilla@jessica.w3.org>
Date: Thu, 17 Oct 2013 10:58:26 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23545-2486-yYsxSNx6dK@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23545

--- Comment #3 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to Joshue O Connor from comment #2)
> Currently, the specs mapping of <section> to region is resulting in a poor
> user experience. JAWS for example will announce each <section> element in a
> page as a 'Region'. Previously this had been reserved for ARIA landmark
> element IIRC.
> 
> A page may have a menu with 20 heading items, and if it has several
> <section> elements then this can bloat very quickly with each one being
> announced. Newer version of JAWS (> 13) may allow the user to navigate to
> them via the 'Landmark' quick keys, however this doesn't happen with JAWS 13
> for example. Meaning the user will have ~ 60 <section> elements announced to
> them as they navigate (I've seen this in my work). This is a poor
> implementation of semantics and if continues may devalue them. If nothing
> else it adds to the 'don't do this as its bad for a11y, even if semantically
> correct' kind of argument - which none of us really want to have.

Hi Josh, note that it may not be a semantically correct use of section: read
what the spec says about use of section:
http://www.w3.org/html/wg/drafts/html/master/sections.html#the-section-element

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 17 October 2013 10:58:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC