Shall we include headings in the localisation file?

[gautierchomel]

First test implementations have revealed that the heading structure adopted in the guide is too atomic and generates One line of text per heading, making it heavily repetitive.

This can be tested thanks to DAISY Accessibility Metadata Viewer

Therefore, we expect that implementers will use different heading structure and make different groupings like Reading modes for non visual, text adjustment and pre recorded audio.

Because reworking the structure now would be too much work, we agreed, to reflect that, to add the following note: "implementer can decide the preferred order and appropriate headings to use to show the accessibility information that follows".

I suggest that we don't include actual headings in the localisation file as this would generate confusion for implementers who will have to use only part of the localisation file and an additional own localisation.

Keeping our main localisation file with usable elements would also allow for an implementer to release an open source additional structure localisation to use in combination.

[gautierchomel]

Editors decided to:

• delete from the technics the "Display as heading" instructions
• maintain headings in the JSON localization file for if implementers want to use them
• add a group heading "Ways of reading" to the JSON localization file for if implementers want to use it in complement or instead of headings for Visual adjustment, Non Visual Reading and Pre recorded audio.