This evaluation tool is WCAG 1.0 only so should be removed as it causes confusion:
evalaccess. http://sipt07.si.ehu.es/evalaccess2/index.html

This one here is useful & has WCAG 2.0:
http://www.tawdis.net/

But the config pages should never have something like this "Tools you would like to utilize. (not implemented, does nothing.)" - if it does nothing it shouldn't be there.

Simply having a block in this module which presents the following would be good:

<div style="float: left; align: center;"><a href="http://wave.webaim.org/refer"><img src="http://openconcept.ca/sites/openconcept.ca/files/webaim-wave-icon.gif" alt="Check with WebAIM's Wave Toolbar"></a> <a href="http://fae.cita.illinois.edu/evaluate/link/"><img src="http://openconcept.ca/sites/openconcept.ca/files/fae_logo.gif" alt="Check with FAE"></a></div>

Something that makes it easy for admins to evaluate their site.

By default it should be enabled for all authorized users.

Comments

johnbarclay’s picture

Title: Get rid of evalaccess, stick with WCAG 2.0 compliance & add block » Accessible Help: add block
Assigned: Unassigned » johnbarclay

Sounds good. Seems like separate issues. I suspect such a block should go in accessible content, but it won't hurt to have it in both for the time being. I committed this to head on 2.x. Its in the accessible help module.

mgifford’s picture

Thanks!