The Drupal accessibility team have been considering the imminent release of Drupal CMS and we have agreed that it would be a good idea to assess the contrib modules that are going to get into Drupal CMS for accessibility issues #3475279: [Meta] Audit each module to be included into Drupal CMS for accessibility issues. We are well aware that, at this point, no definite decisions were made as to which modules would get in. We started the assessment under the premise that even if an evaluated module does not get into Drupal CMS in the end, it wouldn't do any harm to highlight potential a11y issues for the Token module and ideally suggest how to tackle them.
Comments
Comment #2
rkollerComment #3
rkollerComment #4
the_g_bomb commentedComment #5
rkollerComment #6
rkollerComment #7
rkollerComment #8
berdirThanks for starting this, well aware that accessibility and usability of the token UI is really not great. (And performance!).
Frontend stuff is really not my area of expertise, so I can't help much there, but I can try to review and commit things that are reviewed and approved by others.
That said, I'm not sure if granular improvements are feasible or the whole thing should be redesigned from scratch, which is what #1229568: Token UI 2.0 would be about.
If you have any knowledge of existing tools that could be used for such a purpose, that are better at those things out of the box than the old jquery treetable then that would be great. One of the main things it would need to support is partial/lazy loading of the structure so we avoid to load hundreds of tokens upfront and get rid of the depth limit at the same time.
Very open to alternative UI approaches as well, I've been thinking about about some kind of mix of autocomplete and tree traversing.
Comment #9
ressaWhat a great side effect of the Drupal CMS initiative, lifting up collectively the rest of Drupal as well, making an already amazing module even better. Nice!