-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
AVT 1 - React or the Header Base w/Navigation, Actions & SideNav UI Shell has DAP violations #3576
Comments
This change eliminates duplicated `<main>` (one from UI shell story) and `<div role="main">` (one from the Storybook decorator for all stories) by telling the existence of former to the latter. This change also does: * Defines the color of non-focused state of skip-to-content element, given our a11y test tool cannot detect "shown for screen reader only" element * Make focus sentinel point to the main content for better navigation Refs carbon-design-system#3576.
@snidersd looking into this, it seems the color contrast violation is coming from the SkipToContent component when it's not visible, DAP mistakenly sensing it there with our regular |
@abbeyhrt @mattrosno I reported the color contrast violation on the Skip to Main to the Accessibility Web Engine Github repo # 234. If the violation, "An element with WAI-ARIA role must be contained within a valid element" is addressed the issue should be closed. Thx. |
Thank you for clarifying @snidersd - I don't see such violation in latest code. Closing. |
Environment
macOS Mojave version 10.14.5
Chrome Version 75.0.3770.100 (Official Build) (64-bit)
Carbon v10 - React
DAP - July 2019 Ruleset
Detailed Description
Run DAP on the Header Base w/Navigation, Actions & SideNav UI Shell. The following 7 violations:



violations are identified (see screenshots below):
Note:
Add a role to the parent of the menuitems. Use role="menu" or "menubar" or "group" to fix the issue. DAP only reports this issue if the page size reduced and the links do not display across the top of the page.
The text was updated successfully, but these errors were encountered: