Communicate “page breaks” via more than just styles #51 #54
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
chasenlehara
requested review from
mikemitchel,
tobiasnteireho and
janebitovi
chasenlehara
force-pushed
the
51-page-breaks
branch
2 times, most recently
from
f767f48 to
e895af4
Compare
Previously, the page break element was not perceivable to screen readers because it rendered no text. Now, some text will be in the DOM for screen readers to read, while the visual representation of the page break has not changed. Closes #51
chasenlehara
force-pushed
the
51-page-breaks
branch
from
e895af4 to
e1be3c1
Compare
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 page break element was not perceivable to screen readers because it rendered no text.
Now, some text will be in the DOM for screen readers to read, while the visual representation of the page break has not changed.
Closes #51