-
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]: Spin button form field does not have label. #4229
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 . |
1 similar comment
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 . |
…n input box in Image Gen page. (#4335) fixes [#4229](#4229), [#4218](#4218) and [#4228](#4228) <!-- Link to relevant issue (for ex: "fixes #1234") which will automatically close the issue once the PR is merged --> ## PR Type <!-- Please uncomment one ore more that apply to this PR --> Bugfix <!-- - Feature --> <!-- - Code style update (formatting) --> <!-- - Refactoring (no functional changes, no api changes) --> <!-- - Build or CI related changes --> <!-- - Documentation content changes --> <!-- - Sample app changes --> <!-- - Other... Please describe: --> ## Describe the current behavior? <!-- Please describe the current behavior that is being modified or link to a relevant issue. --> 1. For the padding input on the image gen page there was no accessible label 2. For some of our black buttons the focus ring wasn't showing when tabbed over 3. Incorrect aria roles defined ## Describe the new behavior? 1. Input has a label 2. New visible focus ring. 3. Removed unnecessary definitions of role. ## 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
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
5 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 . |
Closing this issue as fixed. |
What happened?
Spin button form field present on the URL does not have label, narrator does not announce the information of the 'Padding' label.
How do we reproduce the behavior?
Repro Steps:
What do you expect to happen?
Spin button form field present on the URL must be associated with the label 'Padding'.
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)
URL: https://www.pwabuilder.com/imageGenerator
Tool: AI4W
Additional context
Element path:
app-index,image-generator,sl-input,#input
Snippet:
How to fix:
Fix all of the following:
Form element has explicit that is hidden
User Experience:
If the label of the form element will not be defined then the users depend on screen reader will not get the information of the purpose of the spin button, and they may get confused in accessing the UI properly.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html
Attachments:
The text was updated successfully, but these errors were encountered: