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

Investigate if <details>/<summary> is a good choice for our Checklist #1419

Open
ericwbailey opened this issue Mar 2, 2022 · 0 comments
Open
Labels
bug Problems with the project's functionality help wanted Issues the team would like assistince with.

Comments

@ericwbailey
Copy link
Member

ericwbailey commented Mar 2, 2022

We currently use the details and summary elements for our Checklist page. These element allow for a native expand/collapse experience, without the use of JavaScript.

Our checklist items do not use heading elements, which was a concern voiced in this thread on the web-a11y Slack. There is also mention of concerns around interactive content placed within the summary element, which we do use for both WCAG links and permalinks.

Additionally, this repo by Melanie Sumner highlights other potential issues.

We should revisit our usage of details and summary elements to see if they are usable, or if an ARIA construct would be a more desirable replacement.

@ericwbailey ericwbailey added bug Problems with the project's functionality help wanted Issues the team would like assistince with. labels Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Problems with the project's functionality help wanted Issues the team would like assistince with.
Projects
None yet
Development

No branches or pull requests

1 participant