-
Notifications
You must be signed in to change notification settings - Fork 353
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 editor menubar example revisions made through June 2017 #409
Comments
Related to issue #409: 1. Add aria-disabled to menuitems for for increasing and decreasing font size. Disable larger when size is already largest and smaller when size is already smallest. 2. Add documentation to roles, states, and properties for aria-disabled. 3. Add documentation to roles, states, and properties for names calculated from content.
Below are my observations:
2)When I selected Fantasy, now I go to the next item (Style/Color) in the menubar by clicking the right arrow. Screen reader NVDA in FF browser is not announcing that the different font is selected (on selecting enter) and when I go back to that font type by using up and down arrow, NVDA is reading the font type is not checked but the font is changed in the tab panel according to the selection made. In Style/color menu. Upon selecting only first two submenu items got check mark next to them. Not for the remaining selections. |
I ran the example through aXe, since it had some stuff that looked fishy (li with aria-expanded which never changes, then inside a direct-child span with aria-expanded which DOES change... confusing for a developer) and aXe claimed a menuitem role'd thing can't have aria-expanded. Indeed I don't see aria-expanded in the list for menuitems and related types, though I do see aria-haspopup. So what's the secret way of showing the expanded/collapsed state of the submenu "popup"? Should the menuitem NOT have a haspopup and instead have a button inside with haspopup and expanded? Are menuitems allowed to have controls inside them other than what they themselves do? If it has a menu child, can it also have a button child? Should it? Whatever it is I'm doing at work, it's never going to be following the spec entirely, because I'm too dumb to be able to read it right. |
@shirsha, thanks. It looks like this example was broken by commit 0de93bd. It took some digging, but I found if I checkout one of the parents of that commit, commit a6d74df, the aria-checked properties are getting set correctly. That is the cause of the NVDA behavior you are observing. I could not reproduce the first issue you observed. I also observed that that the Enter key behavior does not match what is documented in the pattern. I raised issue #524. |
@StommePoes commented:
No, menuitems are not composite widgets. They cannot contain other widgets. |
No refer to menubar-2-init.js in the Javascript and CSS Source Code paragraph of menubar-2 example. CSS and js in menubar-2.html <!-- CSS and javascript for this example. -->
<link href="css/menubarAction.css" rel="stylesheet">
<script src="js/styleManager.js" type="text/javascript"></script>
<script src="js/MenubarAction.js" type="text/javascript"></script>
<script src="js/MenubarItemAction.js" type="text/javascript"></script>
<script src="js/PopupMenuAction.js" type="text/javascript"></script>
<script src="js/PopupMenuItemAction.js" type="text/javascript"></script>
<script src="js/menubar-2-init.js" type="text/javascript"></script> |
The editor menubar example has been significantly revised and is ready for additional review.
Known issues
Reviews requested as of June 20, 2017
The text was updated successfully, but these errors were encountered: