Made plaintext decklist outputs more friendly to screenreaders #848
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
|
My editor added that extra space after the five_threes line. I don't know why. |
|
This makes it better for screen readers and worse for browser users. Let's take a look at how we can get the best of both worlds here. |
|
Feel free to edit this |
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.
Previously the plaintext data for decklists would include an
xbefore each card (e.g. "3x Sure Gamble") which screenreaders would read out, making it an inaccessible feature. It also reads out the influence pips individually, so those have been simplified to plaintext.