The Accessible Content Module and the Accessible module

Took a brief look at an initial install. I'm really looking forward to seeing quail available within a Drupal module.

I did want to know if you plan to bring this over to Drupal.org at some stage. I just trust the security work that goes on with code on the main site and it's also clear what the status of the license is too.

If you do move the quail libraries out of the main release of this drupal module, I like the process of sticking these external libraries in sites/all/libraries

I get this error, but going here admin/settings/accessibility_themer I don't have an option for anything to select in "Site-wide Guideline:":
# Site-wide guideline not set. Please set the site-wide guideline first.

Would be good to add the description of Accessibility Themer & Accessible Content in the admin/settings for clarity.

Upon the install it didn't "run 250 ac_test nodes", but wow! Sounds very comprehensive! Well, at least I didn't think it ran it, however the first node I created was #213, so there must have been a 212 created elsewhere. Adding the accessibility functionality to the blog node I wasn't able to get it to work. I could go to node/213/accessibility and didn't see the deliberate error I put in with a missing alt text. Although I'm not sure what I can define without first setting the guideline.

On editing the blog, I'm not sure what Check accessibility & Highlight accessibility Issues are supposed to do but they didn't work for me. Could be because I had disabled the AC, but I'd think that would be unrelated..

I found the enable/disable AC link in the bottom right but wasn't sure where to look for it. Good to add that to the docs.

Not sure where things went wrong, but let me know if I'm just missing something obvious. It's looking very helpful as a means of managing user input - the most difficult aspect of keeping a site accessible!

Thanks for this feedback. I scanned through the readme and this line didn't jump out at me:

You should probably first create a node of type ac_guideline and associate it with a few tests. In the future, we will probably need to provide a set of guidelines to begin with like WCAG 1 and 2, 508, etc.

Maybe it would be better phrased:

In order to evaluate the contributed content with this module you will need to ensure that there is at least one ac_guideline node type created and that it is selected for site wide compliance. You will have to look through and select which of the 250 tests you want to add. In the future, we will need to provide initial sets of guidelines (WCAG 1 and 2, 508, etc.) that will make it easier to select how your content is evaluated. Contributions of tests & required guidelines would be appreciated!

I did randomly select some tests, installed them and then ran into this error which is hitting all pages.

[29-Oct-2009 11:21:32] PHP Fatal error: Class 'scriptOnclickRequiresOnKeypress' not found in /Applications/MAMP/htdocs/drupal-6.9/sites/all/modules/accessible_content/quail/common/tests/scriptOnmouseoutHasOnmouseblur.php on line 3

Good to get community feedback, thanks. I think it would probably be best at this point to set it up as it's own module. I don't think John's had much time to update http://drupal.org/project/accessible recently. It's also different. The Accessible Helper Module is more about back-porting enhancements that we want to get into D7 back into D6. It will probably also be where we will put the accessibility enhancements that don't get into core.

I agree, the mission of the two modules is very different, but I didn't want to be stepping on any toes.

I fixed the script tests, there's a class inheritance issue there and committed to the code.google.com site for QUAIL. This is the kind of thing that user testing is helpful for ;)