Clean up mentions of HTML4 and XHTML #3980
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
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
patrickhlauke
approved these changes
Jul 21, 2024
|
patrickhlauke marked as non substantive for IPR from ash-nazg. |
giacomo-petri
approved these changes
Jul 27, 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.
A lot of HTML4 and XHTML descriptions were removed by #2490, but there are still some parts left. This PR attempts to clean up those pieces.
Modify link from HTML4 to HTML
F40 and F44
Remove mentions of XHTML in techniques
ARIA6, SCR22, C27, F46, F58, F69, F70, F77, F80, G108, G110, G175 and G204
Remove mentions of XHTML in understanding
However, the following pages are excluded:
Understanding SC 3.1.1:
This link text is probably inappropriate, but I didn't know what to change it to, so I left it as it is.
Understanding Conformance:
In the Examples of Conformance Claims section, there are several mentions of XHTML 1.0. I didn't change them in this PR, but I think it needs to be rewritten separately.