Form: Accessibility & SEO Fixes #97
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
natalialuzuriaga
changed the title
natalialuzuriaga
requested review from
IsaacMilarky,
DinneK,
sachin-panayil and
decause-gov
sachin-panayil
approved these changes
Sep 9, 2025
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.
Problem
According to lighthouse, the form's accessibility score is 62. We would like to implement some fixes to improve it.
Solution
h4s to beh3to change to correct heading descending orderdescriptionmetatag to improve SEOResult
Accessibility score is now 80!
SEO score is now 91!
These are all the fixes that can be made under our control. The rest of the fixes will be addressed upstream (https://github.com/formio/uswds) since issues deal with Form.io components