Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Eligibility Questionnaire][Accessibility] Heading hierarchy is incorrect #262

Closed
elenm opened this issue Jul 26, 2021 · 2 comments · Fixed by #504
Closed

[Eligibility Questionnaire][Accessibility] Heading hierarchy is incorrect #262

elenm opened this issue Jul 26, 2021 · 2 comments · Fixed by #504
Assignees
Labels
epic: eligibility questionnaire Tickets related to the eligibility questionnaire workstream
Milestone

Comments

@elenm
Copy link

elenm commented Jul 26, 2021

There are only level 2 and level 5 headings on the page.

This fix requires updates to the Bloom core components.

@elenm elenm added the epic: eligibility questionnaire Tickets related to the eligibility questionnaire workstream label Jul 26, 2021
@github-actions github-actions bot added the M10 label Jul 28, 2021
@willrlin willrlin added this to the M10 milestone Jul 28, 2021
@willrlin
Copy link

Which page? Just the eligibility questionnaire or all pages?

Could you also say a bit more about what the fix would be? Do we need to adjust the heading hierarchy to include other levels across all ui-components or is there a smaller scope we can work with?

@elenm
Copy link
Author

elenm commented Aug 30, 2021

All the pages require the heading hierarchy to be fixed, but I intended the scope of this issue to to be for the eligibility questionnaire.

I actually went ahead and fixed the headings for the homepage as well because that was necessary for fix the eligibility questionnaire headings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: eligibility questionnaire Tickets related to the eligibility questionnaire workstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants