GRO-202-Update accessibilty statement #322
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
PaolaDMadd-Pro
force-pushed
the
GRO-202-Update-Accessibilty-Statement
branch
2 times, most recently
from
b40ca4d
to
ac9b73e
Compare
- set getAccessibility in hof.settings.json as false - add accessibility.html file with content changes -add static pages in index.js before steps - update PR file name
PaolaDMadd-Pro
force-pushed
the
GRO-202-Update-Accessibilty-Statement
branch
from
ac9b73e
to
a608615
Compare
davidafolabiHO
approved these changes
Sep 20, 2024
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?
Update accessibility statement specifically for GRO
Why?
As per business request Jira ticket GRO-202
How?
I set
getAccessibilityinhof.settings.jsonas false. I then addaccessibility.htmlfile with content changes. Finally I included inindex.jsthe static pages sessions before steps.Testing?
n/a
Screenshots (optional)
see Jira ticket GRO-202
Anything Else? (optional)
Check list
here is an example commit