-
Notifications
You must be signed in to change notification settings - Fork 106
fix(accordion): keyboard a11y #1827
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
Conversation
|
paging @kelsS This PR attempts to fix accordion keyboard a11y within the pfe rewrite, #1804 To try it out for yourself, first ensure you have the prerequisites (nvm recommended) clone the pfe repo then setup the node version with run the unit tests on the accordion with run the development server I was able to get some of the tests passing with minimal code changes. I have some questions about behaviour before I continue implementing fixes:
|
35b3a32 to
8abcb16
Compare
aa8a9a1 to
5dcf92d
Compare
8abcb16 to
eae8eec
Compare
5dcf92d to
81f7e9a
Compare
c85b570 to
27b90f0
Compare
7a95a7c to
7f52cf3
Compare
|
Note to reviewers: at the target branch gets updated, a github action workflow tries (and fails) to update this branch. That makes it hard to find the relevant changes, so I'm linking to the test cases for keyboard accessibility here: I've also changed this to a draft so it doesn't get merged until it's been reviewed |
|
@markcaron helped me understand the authoring practices
That means our implementation is fine. I'll update my tests |
test(accordion): update keyboard a11y tests
4ed591a to
3f48c00
Compare
|
I'm going to merge this into #1804 now, further review should proceed there |
Adds unit tests for keyboard accessibility fixes in
<pfe-accordion>Related issues
Preview
Link(s) to demo page(s) where this element can be viewed:
What has changed and why
delegatesFocuswhen attaching<pfe-accordion-header>shadowrootTesting instructions
Test case 1
npm run test -- --watch --group default --files elements/pfe-accordion/test/pfe-accordion.spec.tsTest case 2
npm startReady-for-merge Checklist
Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the [email protected] mailing list!