Active
Project:
Test Swarm
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Nov 2012 at 16:05 UTC
Updated:
28 May 2013 at 18:38 UTC
Jump to comment: Most recent
QUAIL is a a library for testing accessibility compliance against WCAG 1.0, WCAG 2.0, and Section 508 guidelines.
The QUAIL Library in version 2.0 has a QUnit port: https://github.com/kevee/quail
Passing accessibility tests should be a gate for front end code.
Comments
Comment #1
jessebeach commentedComment #2
mgiffordThis is totally amazing. Really looking forward to seeing this be included in the automated testing!
Comment #3
Anonymous (not verified) commentedHi, there, I'm the maintainer of QUAIL and am totally on board with helping out with this project.
Here's how I think this can work:
QUAIL isn't really "integrated" with QUnit, I just use it a lot to cover the 256 test cases we have in the project. However, given that experience, integrating it shouldn't be too much work ;) QUAIL is separated into three kinds of tests, and for the time being it probably only makes sense to use "severe" tests in the swarm, as moderate or suggestion tests are for things that require some form of human interpretation and in the case of "suggestions" are oftentimes old practices that are not used anymore.
Given that, it's a simple matter of just loading the page, a custom guideline that is built of all severe tests, and it should be good to go. I'm focusing on WYSIWYG editor plugins right now, but after that I'll take a look at the test swarm.
Comment #4
mgiffordAny progress on this? Also interested in having a version backported to D7.
Comment #5
attiks commentedMe too :-) but for the moment I need to do some paid work first :-\
Comment #6
mgiffordI don't know if we can pay you to do it, but if we can swing it would it move this up the priority list?
Comment #7
attiks commentedYes it would :-)
I'll try to have a look tomorrow to see how much work it will be and when I would be able to do it.
Comment #8
attiks commentedI did some thinking about some scenarios
Questions
Comment #9
Anonymous (not verified) commentedThere has been work in a sandbox on a generalized accessibility module with an API and sub-modules. There's a basic implementation with test swarm:
http://drupal.org/sandbox/kevee/2000774
Comment #10
liam morlandComment #11
mgiffordAny progress on the integration for the code sprint on Friday?
Comment #12
attiks commented#11 Work is done in http://drupal.org/sandbox/kevee/2004936 and it is partly working already, although there are some issues, see http://drupal.org/project/issues/2004936?categories=All
I ran a test on admin/help/field_ui (I think WCAG2AA):
<a id="main-content"></a>, see #2005486: aMustContainText error on main-content<img src="http://d8git.ubuntu006.attiks.office/core/themes/bartik/logo.png" alt="Home">Comment #12.0
attiks commentedUpdated issue summary.
Comment #13
mgiffordSee it live here -
http://drupala11y.org/EDIT: Sadly drupala11y.org is down now.