[Bug 25003] modify required heading mappings to reflect reality

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

--- Comment #3 from Michael[tm] Smith <mike@w3.org> ---
(In reply to Dominic Mazzoni from comment #2)
> I agree, let's change it to match implementations.

Is that because you believe there's no potential benefit to it? No problem that
it solves? Or just because pragmatically speaking you don't think vendors are
going to implement it? Or you don't think the spec is clear enough about the
requirements? Or something else?

Considering a document that does something like:

  <section><h1>Top-level section</h1>
  ...
      <section><h1>Nested Subsection</h1>
      ...
          <section><h1>Deeply nested sub-subsection</h1>

On the face of it, it seems to me that if AT handles those nested H1s as if
they were at the same level (aria-level) as that top-level H1, that's not good
UX.

Or am I mistaken and it's not actually a problem in practice for AT users if
those H1s all get handled as being of the same heading level (aria-level)?

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

Received on Wednesday, 12 March 2014 04:59:01 UTC