-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ensured and added keyboard navigation for public facing components #230
base: master
Are you sure you want to change the base?
Conversation
Release d66348a deployed at https://pcns-dev-pr-230.apps.silver.devops.gov.bc.ca |
|
59ed470
to
36482f7
Compare
36482f7
to
9c6600c
Compare
This hasn't been fixed. It still goes to the footer before the Assistance.
Permit status pills' tooltips are skipped
The keyboard focus should go to the first tab-able component in that section, not the header.
This one is good, but I can't test it as a Proponent. So just want to make sure that the linked project name goes to the intake form on Proponent side, not on Nav side.
|
9c6600c
to
6da3bf5
Compare
Description
Ensured and added the ability to navigate the application (proponent side) with keyboard
So that we are WCAG 2.2 compliant for public facing components
PADS-310
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments
The tests that would cover keyboard navigation are too in depth to implement for this ticket. Should be applied to future Integration level Testing.