- From: Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
- Date: Thu, 23 Apr 2015 15:34:08 -0400
- To: Mitchell Evan <mtchllvn@gmail.com>, Wayne Dick <waynedick@knowbility.org>
- CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <C274A5503C851E43A8ED400AC86E028513CC105338@SOM-MB.wiley.com>
There more likely scenarios is a long embedded article or aside with its own internal headings. This is an EPUB issue, but I can attest that EPUB creators have the question (myself included). This question is relevant for HTML that does not go into the EPUB format as well. Thanks for your help. Tzviya Siegman Digital Book Standards & Capabilities Lead Wiley 201-748-6884 tsiegman@wiley.com<mailto:tsiegman@wiley.com> From: Mitchell Evan [mailto:mtchllvn@gmail.com] Sent: Thursday, April 23, 2015 12:15 PM To: Wayne Dick; Siegman, Tzviya - Hoboken Cc: w3c-wai-ig@w3.org Subject: Re: deeply nested headings 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<mailto: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
Received on Thursday, 23 April 2015 19:34:45 UTC