- Issue created by @Kristen Pol
- Assigned to itmaybejj
- Status changed to Postponed: needs info
over 1 year ago 10:25pm 2 August 2023 - 🇺🇸United States itmaybejj
If you'd like to draft something I'll look it over. I've tried to avoid naming names when I talk about the advantages of a more user friendly UI.
- Status changed to Closed: works as designed
about 1 year ago 2:36pm 17 November 2023 - 🇺🇸United States itmaybejj
Hi Kristen -- I think...I'm going to close this for now. The short story is that "Web accessibility" is one of the modules that requires pressing a button, and runs more comprehensive checks. This is one of the approaches I'm pushing back on, since it asks a lot of the user. But I'm a little more comfortable saying that obliquely within my own description.
It may be good to do this more comprehensively and neutrally in the Drupal accessibility module roundup → -- perhaps we could add a table with what is checked (rendered vs in-WYSIWIG), which checks are run (content-focused, AXE core, AXE plus proprietary, etc) how it is checked (automatic/on-demand/crawler), and whether a site-wide dashboard is provided. I could help with that, and link to it.
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
No worries. Thanks for the info and the module:)