Support for HTML_CodeSniffer over sites that use Secure HTTP (HTTPS) has been an issue for some time. With recent changes that Github made to their secure certificate (to now cover sites on the Github Pages domain) combined with changes to the bookmarklet now mean that it should now work over HTTPS.
The bookmarklet link on the HTML_CodeSniffer home page has been updated. Existing bookmarklets can be updated by removing the “http:” from the path near the start (so that the path reads “//squizlabs.github.io/HTML_CodeSniffer/build/”). This ensures that the same scheme (protocol) is used as the site you are testing.
This will allow many more sites to be able to use HTML_CodeSniffer, but it is not completely foolproof, depending on site and browser security settings.
References to Principles, Guidelines, Success Criteria and Conformance Requirements should be read in line with the WCAG 2.0 Recommendation.
Success Criterion 1.3.1:
The test for Multiple label tags with the same “for” attribute has been removed. The standard does not state that this is a violation, and the things it appeared to have been written for are covered in other tests which more directly check such violations (namely duplicate IDs).
Colour contrast tests (Success Criteria 1.4.3 and 1.4.6):
If a colour contrast ratio fails, but by less of a margin than the default precision shown by HTML_CodeSniffer (which is 2 decimal places), the extra decimals are now shown to prove that this is not a false positive.
An example in the issues list had a contrast ratio of 4.497:1, which would show as “4.5:1” and thus appearing to “pass” a 4.5:1 contrast test, but now shows with all three decimals.
Also, a JavaScript error in the standard was fixed, which was triggered when a colour contrast test failed.
References to Section 508’s rules should be read in line with the U.S. Government’s regulations defining the Section 508 standards for “Web-based intranet and internet information and applications”.
Rules A and L:
Unwound dependencies against the WCAG 2.0 standard, so that developers wishing to only distribute the Section 508 standard can do so without also needing to distribute the WCAG 2.0 standard.
Rule J:
Fixed a JavaScript error that triggered when a page had no title element.