-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON missing title #654
Comments
Actually, they no longer have status beyond separating the logic of what goes under "Ways of reading" (i.e., they aren't expected to be output anymore). |
@mattgarrish per https://w3c.github.io/publ-a11y/a11y-meta-display-guide/2.0/draft/guidelines/#ways-of-reading and your response, we should essentially ignore Prerecorded Audio, Support for Nonvisual Reading and Visual adjustments as sub headings / a title that should be displaying and just show Ways of reading as the heading and render the techniques as direct children to Ways of reading? |
Right, "ways of reading" was introduced to replace the three individual headings as it was thought that they weren't conveying enough information to warrant having separate headings. This is shown in the examples for the section: https://w3c.github.io/publ-a11y/a11y-meta-display-guide/2.0/draft/guidelines/#wr-examples The subsections were retained in the guidelines as a means of speaking to each of the key areas, but I know the best structuring of that section was struggled with. I think it would be helpful if 3.1 started by speaking to why there are three subsections but headings for each are not expected. Having it immediately jump to 3.1.1 without any prose is probably going to confuse most people. |
Thanks @mattgarrish for the clarification. Ill let our team know and let @rickj know we can close this issue out. |
Please keep the issue open as we can use it to address the lack of clarity. |
Wow.... that is all news to me... and I've been an active participant!! I'm sure it needs clarity for any new readers. |
The addition of the 'Ways of Reading" top level heading, while still wanting the three sub-headings to have 'top level status' requires some minor adjustments to the json formatting. We would like to suggest the following structure for the 'Ways of Reading" section to enable cleaner processing of visual adjustments, nonvisual reading, and prerecorded audio:
The text was updated successfully, but these errors were encountered: