Active
Project:
Accessible Helper Module
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Apr 2009 at 16:50 UTC
Updated:
26 Feb 2016 at 07:47 UTC
Jump to comment: Most recent
Comments
Comment #1
johnbarclay commentedProbably 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.
Comment #2
mgifford