- From: Ivan Herman <ivan@w3.org>
- Date: Fri, 18 Dec 2015 21:20:23 +0100
- To: Deborah Kaplan <dkaplan@safaribooksonline.com>
- Cc: public-dpub-accessibility@w3.org
Deborah, I will look at it tomorrow, it is difficult to do anything sensible on an iPad mini. However... respec is very strict in the usage os section elements (including subsections). All logical units must be in a section with one single hx element per section. It can actually be any hx; respec transforms these into a hy element where y reflects the hierarchy of select elements. Does this help? Ivan --- Ivan Herman Tel:+31 641044153 http://www.ivan-herman.net (Written on mobile, sorry for brevity and misspellings...) > On 18 Dec 2015, at 20:36, Deborah Kaplan <dkaplan@safaribooksonline.com> wrote: > > Ivan, > > Something in the conversion to HTML from respec is very strange on the > Dpub accessibility note. > > For example, compare > > http://w3c.github.io/dpub-accessibility/#discussion-of-digital-publishing-issues-not-currently-addressed-by-w3c-standards > > http://w3c.github.io/dpub-accessibility/#h-action-needed > > http://w3c.github.io/dpub-accessibility/#page-numbers-pagination > > all different levels in the source, but all H2 in the HTML. And then > compare all of the headings after that, such as > > http://w3c.github.io/dpub-accessibility/#phonetic-spellings-of-proper-nouns-and-jargon-terms > > Which ought to be at the same heading level as pagination above it, but > is coming through as H4. > > I thought some of it might be explained by [section] in the source > button playing around with things didn't address that. Is this something > you can explain that we can fix easily? > > Thank you, > > Deborah >
Received on Friday, 18 December 2015 20:20:40 UTC