Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Pull of various commits including Sec.508 support, issue #57 #60

Merged
merged 8 commits into from Jan 8, 2013

Conversation

Projects
None yet
1 participant
Member

luketw commented Jan 8, 2013

First dump of Section 508 support, including some significant backend changes to the auditor so it no longer assumes WCAG 2.0-related aspects.

Issue #57 (about problems with inputs that have no input type specified - and so should default to text instead of causing JS errors) also fixed.

Luke Wright added some commits Oct 31, 2012

1. First batch of Section 508 sniffs, to get the ball rolling. Will b…
…e named by their paragraph "1194.22" rule letter. (1194.22 is the portion of Section 508 which relates to electronic content.)

2. WCAG2 SC 1.1.1, 1.3.1: first tests to be genericised (null alt text), with the intention to use these in Section 508, but with different msg codes.
   Table header testing moved to HTMLCS util, but might get moved back to 1.3.1.
3. Standards now define what "extra information" is displayed in the auditor. By "extra information": in WCAG 2.0 this is principle and technique(s); in S508 this would be the violated portion of paragraph 1194.22.
   .. A new getMsgInfo() function is in the standard, which takes the code of a message and emits an array of information (two-element arrays) with title and content to display.
4. Auditor now genericised so it can look for things that look like a standard, instead of simply assuming that WCAG 2.0 is the only possible standard set. The "extra info" changes are related to this, too.
5. Fixed some reset style issues with the colour of the "unable to point" and "no code snippet available" messages.
More 508 commits.
Includes some changes to 1.1.1 and 4.1.2 in the WCAG tests to provide more generic results, which can be converted into messages in the appropriate standard.
I'd misread rule L's intent, so changing up the tests made there, to …
…be a combination of 4.1.2's link checking (in reduced format, ie. no warnings for document fragment links), and 2.1.1's "ensure keyboard access to mouse event functionality" tests.

luketw pushed a commit that referenced this pull request Jan 8, 2013

Merge pull request #60 from lwright-sq/master
Pull of various commits including Sec.508 support, issue #57

@luketw luketw merged commit 7a2678c into squizlabs:master Jan 8, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment