Introduce accessible routing documentation #497
Merged
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
Robdel12
changed the title
|
I've added a section to the top-level readme for the patterns files. If ya wanna merge master and add a link to this in that section, that'd be great. I also think it should be linked in the Accessibility.md file in the docs folder. |
Robdel12
force-pushed
the
rd/routing-document
branch
from
98b2734
to
7123c9f
Compare
|
Okay cool, I rebased and added the links to the README and the accessibility doc :D |
JohnC-80
approved these changes
Jul 19, 2018
|
Woop woop! 🎉 I'm excited this made it's way in |
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.
What is this?
This document details the things @wwilsman & I learned while spiking an approach to make the FOLIO UI module we work on accessibile. You can see this work in action in the demos that happened for sprint review 40-41, @cowboyd did a great job! Here's a direct link to that demo on YouTube.
This document is written as a way to describe what we learned so other developers FOLIO can use this as a launch point for making their apps accessibile. This document does not describe the way to make your app accessibile.
As always we are always happy to help with any questions you might have regarding accessibility :)
Lastly here's the PR to eHoldings that was the implementation of this work: folio-org/ui-eholdings#448
Link to the rendered document
TODOs