I'll rephrase the question two ways.
First, what's a good experience for the user? To answer this, I'd like to
hear about real-world examples. Are we talking about a homogeneous
hierarchy, from chapters all the way down to sub-sub-sub-sub-sub-headings?
Or are there sometimes distinct regions of content, like a long embedded
article with its own internal headings? The harder problem to solve will be
cognitive load for anybody, trying to keep track of this much depth.
Second, what is technically correct for HTML, supported today, and
reasonably future-proof? It's a valid question, which I'll leave others to
answer.
On Thu, Apr 23, 2015 at 8:35 AM Wayne Dick <waynedick@knowbility.org> wrote:
> I think the role with new level is interesting, but a misuse of ARIA. The
> problem is with the scope of HTML. This is probably an ePUB issue.
> Publication and testing need more robust semantics than HTML has to offer.
>
> Wayne
>
>
>