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
[4.0] Assignment menu function not accessible to blind users #23911
Comments
@zwiastunsw if you can come up with an HTML markup I'll do the js part... PS nevermind here is the correct HTML markup:
Goes to |
@dgrammatiko : Do you want to improve only the switch? |
@zwiastunsw ok define the HTML here and I'll do the coding part |
This PR addresses some of the issues for joomla#23911 Specifically numbers 2, 4, 6 There are others that need to be addressed relating to the actual lists themselves but I a not sure if the list is even remotely accessible so wish to tackle that in a deperate issue
@chmst is this something you can look into for Accessibility? This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23911. |
@jwaisner: Yes, this page component needs to be rebuilt because it has many accessibility bariers. You can improve particular elements (for ex. select button and expand button), but in my opinion it is better to build it from scratch. |
simply not true but keep repeating it and magically someone will read your mind to decide what the |
If you have nothing to say, you better not say anything. You could finally learn that. |
Words are cheap. Actions have real value. |
Alright, enough. This can be worked we just need someone with the knowledge/time to do so. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23911. |
I'll re-activate the PRs tomorrow and see what happens. I am highly interested in a accessible backend. |
issue 2 was not solved #28726 (comment) |
The user of the screen reader gets access to almost all implemented operating possibilities, but they are not understandable.
The "Menu selection" label is not announced by the screen reader.
A widget to select / expand menu tree is not accessible because
a. Does not have an accessible name (headings or label)
b. “Select” & “Expand” labels are not announced by the screen reader
c. “All”, “None” options are links instead of buttons.
d. “All link” & “None link” messages announced by the screen reader are incomprehensible to the blind person.
The names of the menus in which the user is to select are not announced by the screen reader.
Aliases next to menu item names are unnecessary. They do not provide new information, but they cause information noise, confusion, etc.
Accessibility errors in the context menu:
a. Nonconsecutive level heading used. The menu contains an
<h5>
tag directly following an<h3>
(“Sub-items”). In order to maintain a consistent outline of the page for assistive technologies, reduce the gap in the heading level by upgrading this tag to an<h3>
or<h2>
or see paragraph b. below.b. The names of items in the context menu are unclear. They should rather be: “Select sub-items”, “Deselect sub-items”, “Expand sub-items”, “Collapse subitem”. In this case the heading H5 (Sub-items) is not needed.
c. When you select or deselect from the context menu, all items in the level are always selected, not just the selected item. Blind screen reader user does not see or hear it.
d. Icons next to the names of items in the context menu are unnecessary.
There is a search box on the Assignment Menu tab. The field does not have an accessible label. In addition, it is not keyboard focusable, because it has been excluded from the tabulation order using the
tabindex="-1"
attribute.The text was updated successfully, but these errors were encountered: