Add visual content indicators section #118
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hm, the diff isn't working in the above comment, either. Looks like a w3c service is down. Whenever it comes back up, the link should work again, though. |
madeleinerothberg
approved these changes
Nov 25, 2024
clapierre
approved these changes
Nov 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is my best attempt to try and address the issue raised in w3c/epub-specs#2653
I've taken all the access modes that are describing visual content and created a new section called "Visual content indicators" for them. I've tried to explain that these are expanding on access mode visual but also caution that "visual" should always be set with them.
That's the best I can think of to avoid removing or deprecating them, but other ideas welcome.
I've also standardized the casing of the section titles and added a change log for 2024 (with the missed entry for the descriptor mechanism we added over the summer).
💥 Error: 500 Internal Server Error 💥
PR Preview failed to build. (Last tried on Nov 25, 2024, 2:37 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 [Related URL]([object Object])
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.