-
Notifications
You must be signed in to change notification settings - Fork 295
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
[PWA Builder][Shoelace]: Content present on the Generate Service Worker dialogue is not get scrolled using up/down arrow keys. #4240
Comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
2 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
6 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
1 similar comment
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
fixes/features (should be multiple, add to the list) 1. App Capabilities: #4034 2. Accessibility issues: #4258, #4259, #4239, #4240 ## Describe the current behavior? <!-- Please describe the current behavior that is being modified or link to a relevant issue. --> 1. App Capabilities are mixed in with manifest and SW fields and there is no easy way to discover and learn about them 2. Accessibility Issues from most recent pass ## Describe the new behavior? 1. New designs to isolate app capabilities and give our users more information about what they are and how to implement them. 2. Fixed those issues ## PR Checklist - [x] Test: run `npm run test` and ensure that all tests pass - [x] Target main branch (or an appropriate release branch if appropriate for a bug fix) - [x] Ensure that your contribution follows [standard accessibility guidelines](https://docs.microsoft.com/en-us/microsoft-edge/accessibility/design). Use tools like https://webhint.io/ to validate your changes. ## Additional Information 1. Known issue: #4453 waiting on dependency (shoelace-style/shoelace#1612). 2. No additional context --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Justin Willis <jgw9617@gmail.com> Co-authored-by: Gleb Khmyznikov <gleb.khmyznikov@gmail.com> Co-authored-by: Nikola Metulev <nmetulev@users.noreply.github.com> Co-authored-by: Mara'ah Lee <maraahlee@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Adolf Daniel <10156724+adolfdaniel@users.noreply.github.com> Co-authored-by: Justin Willis (HE / HIM) <juwillis@microsoft.com> Co-authored-by: Zach Teutsch <88554871+zateutsch@users.noreply.github.com> Co-authored-by: Beth Pan <xupa@microsoft.com> Co-authored-by: vipul-bhojwani <67650372+vipul-bhojwani@users.noreply.github.com> Co-authored-by: Amrutha Srinivasan <amrutha.srinivasan95@gmail.com> Co-authored-by: Federico Navarrete <darklord.navarrete@gmail.com> Co-authored-by: Toby Liu <ybot1122@gmail.com> Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com> Co-authored-by: Amrutha Srinivasan <amsrin@microsoft.com> Co-authored-by: Jonas Thelemann <e-mail@jonas-thelemann.de> Co-authored-by: Siraj Chokshi <19193347+SirajChokshi@users.noreply.github.com>
What happened?
User is unable to scroll up and down the dialogue with up/down arrow keys to read the whole information of the Generate Service Worker dialogue.
How do we reproduce the behavior?
Repro Steps:
What do you expect to happen?
The dialogue must get scroll up and down with keyboard up/down arrow keys.
What environment were you using?
Test Environment:
OS Build: Windows 11 Enterprise Insider Preview 22H2 (23493.1000)
Edge Browser: Version 115.0.1880.3 (Official build) dev (64-bit)
User ID: V-
URL: https://www.pwabuilder.com/reportcard?site=https://webboard.app
Additional context
Observation:
Screen reader users are able to read whole information in scan mode.
User Experience:
If the dialogue will not get scrolled up and down with keyboard up/down arrow keys. then the users dependent on the keyboard will not be able to read the whole information of the dialogue and they will not get the information of the UI properly.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html
Attachments:
2023-08-08.23-27-44.mp4
The text was updated successfully, but these errors were encountered: