Remove tilde from accessibility strategy content #4189
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
✅ You can preview this change here:
To edit notification comments on pull requests, go to your Netlify site configuration. |
calvin-lau-sig7
approved these changes
Oct 8, 2024
Change to 'about'
calvin-lau-sig7
force-pushed
the
remove-tilde
branch
from
5d9666b
to
f318062
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.
Change
Replaces the tilde on the accessibility strategy page with 'around'.
Resolves #4024
Notes
Following a discussion of the remaining issues from the 2024 audit of the design system website, we've decided that we'll fix this specific reported issue but won't be auditing the website for instances of special characters, in the same way we're auditing our link text for #4023 and #4013.
The reason for this is that special characters are the lowest priority issue for the accessible content audit we're carrying out in response to DAC's reported content issues and we're confident that compared to the other content issues raised, this isn't a significant content issue that we need to investigate further for the moment.