[Bug 25003] modify required heading mappings to reflect reality

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003

Michael Curran <mick@nvaccess.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mick@nvaccess.org

--- Comment #17 from Michael Curran <mick@nvaccess.org> ---
NV Access at this time has no plans to implement this. I tend to agree with
pretty much all comments in favor of bringing things back to reality. The
difference between outline and explicit level is just too big. To add to Dom's
point about articles and pages pulling from various sources, Wordpress is a
killer for this one. Especially with the way a lot of plugins and themes work.
In absolute theoretical terms though I do quite strongly support the outline
idea. There are obviously benefits  not just to screen reader navigation but to
document parsing, transforming and table of contents generation. But, we must
live with the past. We'll need some very strict rules around where this can
safely be used. I.e. new elements or manditory attributes at the top of any
subtree in a page that wishes to use the outline levels.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 22 April 2014 10:28:01 UTC