feat(www): add accessibility statement #13190
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
DSchau
changed the title
DSchau
reviewed
Apr 8, 2019
There was a problem hiding this comment.
In the interest of not blocking this PR--could we introduce the document, and then in a separate PR introduce the footer?
The document and content itself looks great--just a little less sure about the footer, particularly the design and content (and I'd defer to @fk on the design, of course!).
Yes we can. I'll remove the link with a commit and open an issue to sort out placement! |
Co-Authored-By: marcysutton <[email protected]>
Co-Authored-By: marcysutton <[email protected]>
DSchau
approved these changes
Apr 8, 2019
marcysutton
changed the title
This was referenced Sep 16, 2021
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.
Description
This PR adds a central place for Gatsby accessibility information to live on the .org site. It's currently linked from the homepage, with a centered text link at the bottom. We should add it to other sections too, but that will require some design work to fit a footer on pages that go full-height. This PR was intended to ship something we can link to, specifically for @amberleyromo's talk at JAMStack conf.
We'll want to update the accessibility statement whenever we have new information to add, particularly around our current status / commitment to WCAG 2.0 (and the last edited date on the statement...perhaps could be automated? seemed like overkill to me.)
EDIT: the homepage link was removed and #13221 was opened to sort out the design / placement.