Hi!
The accessibility of IMCE could be greatly increased by incorporating a few basic structural elements. Right now, because of these missing elements, it is essentially unusable by disabled users (e.g., users of screen readers). As with most things done to improve accessibility, these improvements would likewise improve the utility of IMCE by non-disabled users as well. The primary things that could be done are as follows:
1. There appears to be no heading level structure. At the top of the page where all the buttons are, perhaps there could be a heading level 1 (<H1>) caption called something like "Operations." Additionally,, each file folder name (I.e., caption like "In-line Images") could be made into an actual heading level (e.g., <H2>).
2. Present the contents of each file folder (e.g., "In-line Images") as a structured table. Additionally, the column heading should be clickable allowing for sorting within each table so that the user can sort the table by, for example, filename, size etc.
3. For each table (as described in "2" above), add a column at the left-most with a checkbox for each row (i.e., file) for the purpose of selecting (checked) or not )unchecked) each file. This way, it is really easy, intuitive and controllable by users to mark a file(s) on which an operation is to be performed (e.g., upload). Additionally, a couple of buttons could be added just above the start of each table for "Check All" and "Uncheck All."
4. Mark each button within the "Operations" section, as described above in "1", with an appropriate tag so that their respective keyboard commands are correctly spoken by screen readers (perhaps the alt-tag attribute as with an image?). Right now, when moving across each button using a screen reader the button's keyboard command does not announce. Keyboard commands do exist for the buttons, but their implementation could be greatly improved.
5. Make a help file to document the use of these accessibility features. There are many ways this could be done. Perhaps the best would be a new button at the top of the page under the "Operations" heading called something like "Accessibility Help" that opens a page with some instructions.
Were the above things incorporated into IMCE, it would be a wonderfully accessible module. It would likely get a #D8AX badge too.
" How does pledging benefit me? By pledging to support the accessibility of your module or theme, it is more likely to be used by large enterprises, government and educational institutions. By making each piece of the Drupal puzzle accessible, you are helping to set Drupal apart from other CMS tools and position our community to grow in these arenas. You should expect to see more use of your module or theme. If a few modules all provide the same feature but one is accessible, it may be more likely to be chosen. In addition, the accessibility of your module/theme and the content it generates will help Google and other search engines to find and share that content. And once you pledge, members of the Drupal Accessibility group will give you more support and technical resources."
I would love to volunteer to assist in this work!
Many thanks,
Richard
Related issues:
Comments
Comment #2
mgiffordFixing formatting in the description.
Comment #3
thallesComment #4
thallesComment #5
thallesFixed in dev branch