-
Notifications
You must be signed in to change notification settings - Fork 686
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
BUG#AC-2485 No visual indication of focus on buttons. (pattern: Butto… #3962
Conversation
…ns lack indication of focus)
|
…ns lack indication of focus)
…ns lack indication of focus)
…ns lack indication of focus)
…ns lack indication of focus)
…ns lack indication of focus)
…ns lack indication of focus)
@magento create issue from PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RaghavendraTirumalasetti please resolve merge conflicts
…ns lack indication of focus)
run cypress |
Successfully started codebuild job for |
LogERROR ON TASK: cypressTests
|
QA Approved. |
…ns lack indication of focus)
Description
Reproduction Steps
Locations (representative sample):
Landing Page
Search Results
Product Detail Page
Shopping Bag
Actual Behavior
There is no visual indication of keyboard focus of buttons when using TAB or SHIFT+TAB to navigate through controls of the page. For the following buttons:
Module 02 - Landing Page:
"Dot" icon buttons for homepage carousel
"Slider" buttons for "Top Sellers" carousel
Module 03 - Search Results Page:
Page selection buttons (which includes - First, Previous, Page #, Next, Last)
Module 04 - Product Detail Page:
QTY "-" and "+" buttons
Page controls on resize (200%) - "<", ">", and page dots
Module 05b - Shopping Bag:
QTY "-" and "+" buttons
Options "dots" button
Visual keyboard-only users can become disoriented when focus is not indicated.
Expected Behavior
Ensure that when actionable elements receive focus, that it appears on screen and that a visible focus indicator is present.
Related Issue
Closes https://jira.corp.adobe.com/browse/AC-2485
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist
Resolved issues: