Either make a page similar to the Drupal status page that points out accessiblity problems or hook into the drupal status page. Examples include:

- warn if calendar popup module is enabled.
- warn if wysiwg editor is enabled by deafult for text editing
- etc.

This could feed off of the "Evaluation of Contributed Modules for Accessiblity Page" at http://drupal.org/node/394458

Comments

johnbarclay’s picture

Probably best to hook into status page, rather than separate accessible status page.

If the page at:

http://drupal.org/node/425494

had role="modulename" or some other designation of what module the issue was related to, this page could be screen scraped and added to status warnings if any were applicable. If the tagging on the page went one step further and added what guideline set it violated (eg guidelines="aria wcag1 wcag2" or guidelines="aria_1.7 wcag1_2.3 wcag2_231.23"), the accessible_api preferences could be used to filter out guidelines the site admin wasn't interested in.

This would fit into accessible_content module or a sub module of accessible helper modules.

mgifford’s picture

Version: 6.x-1.x-dev » 7.x-3.x-dev
Issue summary: View changes