Change requirement to use alternative text in nav doc labels to a recommendation - #2513
Merged
Conversation
mattgarrish
requested review from
avneeshsingh,
dauwhe,
iherman,
shiestyle and
wareid
January 6, 2023 13:07
iherman
approved these changes
Jan 6, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As discussed on the 2023-01-05 telecon, this pull request changes the requirement to a recommendation due to the lack of support both for images and fallback alternative text in navigation document labels and headings.
I forgot that we added a caution box to the authoring specification about the lack of support, so we don't need to do anything more to warn authors about the usability issues non-text content can cause.
From an accessibility perspective, there are other problems with non-text content that the specification doesn't solve, so avoiding the content is probably the best solution (i.e., the alt text is not required to be presented if the non-text content is supported, which disadvantages non-sighted readers). Not presenting alt text when non-text content isn't supported disadvantages everyone equally.