-
Notifications
You must be signed in to change notification settings - Fork 347
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
Review Navigation Treeview Example Using Computed Properties #225
Comments
…perties Modified examples/treeview/treeview-2/treeview-2a.html for issue #225: * Corrected typos. * Editorial revision to wording. * Added description of function of the example. * Revised statement that said treeitems cannot contain interactive elements because they can contain other treeitems.
…iew Example Using Computed Properties For issue #225, modified examples/treeview/treeview-2/treeview-2a.html: * Under accessibility features, removed redundant information about computed level, setsize, and posinset. * Under accessibility features, removed incorrect statement: "The expandable <code>treeitem</code> widgets cannot behave as links, their only action can be to open and close a leaf in the tree." * Added section summarizing treeview terminology with link to the pattern. * Corrected action defined for enter and space (had the action from the file tree example). * Revisions for editorial consistency to keyboard table. * Updated states/properties section header. * For the tree element, corrected row for label. It specified aria-label instead of aria-labelledby. * Revisions for editorial consistency to states and properties table. * Removed level, setsize, and posinset rows since they are not used in this example.
In the Keyboard Support section, currently the following is listed: Question: does Home expand any nodes that are closed? Also, none of the links with role="treeitem" causes a page to load either via keyboard or mouse. |
For issues #223, #224, #225, and #226, modified the keyboard table of the tree view example pages and the keyboard section of the tree view design pattern. For the description of the Home key, per suggestion from @annabbott and @MichielBijl, added the phrase "without opening or closing a node".
Two more issues that need to be resolved before we can complete this review:
|
For issues #223, #224, #225, and #226, made the following changes. 1. In the `tree` row of the states and properties table, change "an tree" to "a tree". 2. In the `tree` row of the states and properties table, removed unnecessary bullet that defines the tree role. 3. In the `tree` row of the states and properties table, reworded the bullet about the roving tabindex focus management. 4. In the source code section of the navigation treeview examples, removed link to no longer existent treeitemClick.js file.
…sion to accessibility features For issue #225, in examples/treeview/treeview-2/treeview-2a.html accessibility features section, added brief description of purpose of custom focus indicator.
Keyboard Support > last row: Suggest adding "(asterisk)" without the double quotes after the character for clarity. |
No other issues noted. |
Per comment from @annabbott in issue #225, In all 4 treview example pages, changed the key column in the keyboard table for the <kbd>*</kbd> key. Added "(asterisk)" after the `*`.
The This appears to be because the corresponding span ( [role="treeitem"].hover,
[role="treeitem"] span.hover {
background-color: #DDDDDD;
/* this causes the hover class to be removed if the cursor is outside the 16em */
width: 16em;
} |
Closing with all review issues resolved. |
All clean up of the Navigation Treeview Example Using Computed Properties is complete and it is ready for final task force review.
Task Force Member Reviews Requested as of Nov 20, 2017
Required Updates
The text was updated successfully, but these errors were encountered: