Open zakkinsey opened 5 years ago
Peter Spraul <p.spraul@axes4.com>
assigned issue to self
Comment created by Peter Spraul <p.spraul@axes4.com>
:
Attached PDF changed: is now an atomic example
Comment created by @MarkusErle:
Accepted as an example Create an additional example with H7 mapped to H6
Write a note to TWG: William - because of Best Practice Guide: there is only the mapping of H7 to P mentioned
Comment created by @pkopicar:
Cleaned up. Is this supposed to be accepted?
@pkopicar added a link to #75: This issue is duplicated by #75
Comment created by @MarkusErle:
Yes, please move to accepted
Comment created by @MarkusErle:
Add in the description that there is theoretically no level limit
@pkopicar added a link to #203: This issue relates to #203
@MarkusErle added a link to #74: This issue relates to #74
Comment created by @MarkusErle:
Reworked the test items according to the new basic test items that are valid for every heading use case example (see Policy Document).
Comment created by @luciatoda:
@zakkinsey unassigned issue from Peter Spraul <p.spraul@axes4.com>
as part of jira->github migration
Jira issue originally created by user Peter Spraul p.spraul@axes4.com:
The objective of this technique is to show how to tag headings with a heading level higher than 6. Use a custom Hn tag that expresses the appropriate heading level. Role mapping an Hn heading tag higher than H6 to P could serve the purpose of simplifying the headings hierarchy. Role mapping an Hn heading tag higher than H6 to H6 allows assistive technology that does not support headings above H6 to nonetheless perceive a heading. Choosing an appropriate role mapping is at the discretion of the author. This example shows H7 rolemapped to P. #203 shows H7 rolemapped to H6.
Note: Naming custom heading tags requires the use of the letter H followed by Arabic numerals without any spaces or punctuation. For example, H1247 is permissible while H1,247 and H1 247 are not.