-
Notifications
You must be signed in to change notification settings - Fork 350
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
Navigation Treeview Example: Convert to single page example with functionality equivalent to disclosure navigation example #1558
Conversation
Regression test coverage:Examples without any regression tests:
Examples missing some regression tests:
Example pages with Keyboard or Attribute table rows that do not have data-test-ids:
SUMMARY:54 example pages found. ERROR - missing tests: Please write missing tests for this report to pass. |
@spectranaut |
@jongund it's flagging some HTML validator issues
|
Co-authored-by: Nick Schonning <[email protected]>
@jongund, thank you, this is wonderful progress! Do we need that much filler content? It takes a long time to read through it. Can we have short, simple content that matches what we have in the Instead of a complementary landmark region for the filler, can we use a region named "Mythical University sample page content"? That is what we have on the disclosure example page. In the disclosure example, activating a link moves focus to the heading of the content. Shouldn't we do the same here? |
When the page loads, the home content page is displayed, but it doesn't have aria-current set. |
I expanded about and loaded overview. If I refresh the page, the about branch is collapsed so the user can't see which page is current. Should the current page always receive focus when tabbing into the tree? After expanding a parent tree item, the name seems to get duplicated. For example, JAWS reads about as "Open about about". |
@mcking65 |
@jongund commented:
Thank you!
Excellent addition. Thank you. I revised a bit to remove the word "should", reduce words, and to emphasize the need for the design to accommodate the tab sequence. We wouldn't want people to make a visually unpredictable tab sequence to make it 1 tab stop away. |
Communicating with @jongund regarding color contrast issue. - tree item links in hover status. Foreground color, #005a9c and Background color #ccc has color contrast ratio of 4.44:1. This fails Nomal text size WCAG AA, WCAG AAA, Large text WCAG AAA. Here is the CSS code. .treeview-navigation a[role="treeitem"] { |
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.
Tree item link hover color contrast issue can be addressed before the merge.
@a11ydoer |
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.
Changed background color, #ADDDFF now has color contrast ratio of 4.94:1 and it pass Normal text WCAG AA, Large text WCAG AA and WCAG AAA.
@mcking65 |
* Confirm the aria-owns element. | ||
* | ||
* @param {obj} t - ava execution object | ||
* @param {String} elementSelector - the element with aria-owns set |
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.
* @param {String} elementSelector - the element with aria-owns set | |
* @param {string} elementSelector - the element with aria-owns set |
/** | ||
* ARIA Treeview example | ||
* @function onload | ||
* @desc after page has loaded initialize all treeitems based on the role=treeitem |
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.
* @desc after page has loaded initialize all treeitems based on the role=treeitem | |
* @description after page has loaded initialize all treeitems based on the role=treeitem |
this.fillerTextSentences.push( | ||
'The content on this page is associated with the <a href="$linkURL">$linkName</a> link for <a href="$siteURL">$siteName</a>.' | ||
); | ||
// this.fillerTextSentences.push('The text content in this paragraph is filler text providing a detectable change of content when the <a href="$linkURL">$linkName</a> link is selected from the menu. '); |
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.
Delete commented out code
} | ||
|
||
/** | ||
* ARIA Treeview example |
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.
* ARIA Treeview example | |
* ARIA Treeview example | |
* |
@jongund |
@nschonni |
Thanks @carmacleod I spun up #1728 |
Resolves #1526 by revising the navigation tree view example.
Changes:
To dos:
Preview link
View revised example in compare branch
Review checklist
Preview | Diff