You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading the spec, I notice that the table of contents is fine, but all headings are h1. This makes navigation harder for people who use them (blind people for example), as we can't skip to the next section without round trips to the TOC (I can only skip to the next heading, as they have the same level). Two possible solutions:
Put the headings of the spec in a hierarchical order (section 1 is h1, 1.1 is h2, etc.); or
Postprocess the code of epmarkup to change the heading levels and make them hierarchical, as it's already done in the TOC.
Of course, the end result will be the same.
The text was updated successfully, but these errors were encountered:
When reading the spec, I notice that the table of contents is fine, but all headings are h1. This makes navigation harder for people who use them (blind people for example), as we can't skip to the next section without round trips to the TOC (I can only skip to the next heading, as they have the same level). Two possible solutions:
Of course, the end result will be the same.
The text was updated successfully, but these errors were encountered: