On Fri, Jan 10, 2014 at 5:55 AM, Christophe Strobbe <[email protected]> wrote: > Hi, > > I agree that WCAG 2.0 is the way to go; the current Section 508 is still > based on a pre-final version of WCAG 1.0 and will hopefully get updated by > the end of the year. > I wouldn't aim higher than WCAG 2.0 AA; even WCAG 2.0 A may be a challenge > at the start. > With regard to tools, I currently don't know what to recommend because I > haven't evaluated any such tools recently. WebAIM's WAVE > <http://wave.webaim.org/> (and the Firefox toolbar > <http://wave.webaim.org/toolbar/>) and the IDRC's AChecker > <http://achecker.ca/checker/index.php> were developed by competent teams. > I don't know who's behind Total Validator (meaning: I don't know the > developers). >
Thanks. I'll take a look at the other tools as well. The thing I liked about Total Validator is it integrates HTML validation, CSS validation, accessibility checking and spell checking in a single tool. I'm seeing errors in all of these areas (though spelling errors are most usually US versus UK inconsistencies), so it would be good to fix them all at once. Regards, -Rpb > Best regards, > > Christophe > > Am Fr, 10.01.2014, 04:35 schrieb V Stuart Foote: >> Rob, *, >> >>>... However, there was a confusing (to me) number of >>>authorities for accessibility standards. >> >> It is really pretty simple--WCAG 2.0 is the gold standard for Web content, >> and is applicable to Non-Web Information and Communications Technologies >> (ICT). National and International Standards bodies are basing conformance >> against this standard. >> >> WCAG 2.0 A, AA, AAA ( also published as ISO/IEC 40500:2012 ) are >> functional levels of conformance with accessibility standards. >> http://www.w3.org/WAI/intro/wcag >> >> The reworked AOO Website should probably meet majority of WCAG v2.0 AA >> level requirements. And Apache OpenOffice as a document preparation and >> review program should also strive to meet WCAG level A & AA conformance >> criteria for ICT (http://www.w3.org/TR/wcag2ict/ ). >> >> Fortunately much of that is accomplished for the website with valid HTML >> 5.0 and WAI-ARIA markup. While the introduction of IAccessible2 to >> supplement MSAA, and improvements in ATK and NSAccessibility move the >> office suite proper into a better compliance with some notable >> shortcommings. >> >> In the United States, the existing Accessibility Board US Section 508 >> requirements were loosely equivalent to WCAG v1, and are being rewritten >> to match functional levels of WCAG 2.0 A & AA. The draft proposal for >> U.S. conformance can be found here: >> >> http://www.access-board.gov/attachments/article/490/draft-rule.pdf >> >> Also, relevant parts of the European Union EN 301 549 ( >> http://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.00.00_20/en_301549v010000c.pdf >> ) as work of the European Commision (EC) Mandate M 376 ( >> http://www.mandate376.eu/ ) are also based on WCAG v2.0 level A and AA. >> >> So running conformance validators for WCAG 2.0 A, AA, & AAA is probably >> the correct choice in reworking the web site. >> >> Stuart > > > -- > Christophe Strobbe > Akademischer Mitarbeiter > Adaptive User Interfaces Research Group > Hochschule der Medien > Nobelstraße 10 > 70569 Stuttgart > Tel. +49 711 8923 2749 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
