Skip to content
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

Closed
snidersd opened this issue Jul 29, 2019 · 3 comments
Labels

Comments

@snidersd
Copy link

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:
Screen Shot 2019-07-29 at 4 35 01 PM
violations are identified (see screenshots below):
HeaderNavActionsSideNav-1
HeaderNavActionsSideNav-2

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.

@aledavila aledavila added this to the UI Shell - A11y Project Team milestone Sep 30, 2019
@dakahn dakahn added priority: high severity: 1 https://ibm.biz/carbon-severity labels Sep 30, 2019
@dakahn dakahn modified the milestones: UI Shell - A11y Project Team, Carbon WCAG Compliance Nov 21, 2019
asudoh added a commit to asudoh/carbon-components that referenced this issue Dec 12, 2019
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.
@abbeyhrt
Copy link
Contributor

@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 a tag color. If you run DAP with the SkipToContent visible, no violation is present:
Screen Shot 2019-12-13 at 10 44 49 AM
and the "Each page should have no more than one main section..." violation is just coming from our storybook environment, not from the UIShell itself. If we address the "An element with WAI-ARIA role must be contained within a valid element" violations, could we close this issue?

@snidersd
Copy link
Author

@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.

@asudoh
Copy link
Contributor

asudoh commented Jan 17, 2020

If the violation, "An element with WAI-ARIA role must be contained within a valid element" is addressed the issue should be closed.

Thank you for clarifying @snidersd - I don't see such violation in latest code. Closing.

@asudoh asudoh closed this as completed Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants