Web Accessibility Evaluation Tools List. Page Speed Online. WebPagetest - Website Performance and Optimization Test. Review Of Cross-Browser Testing Tools. Advertisement At some point in the future, the way that all major browsers render Web code will likely be standardized, which will make testing across multiple browsers no longer necessary as long as the website is coded according to Web standards.
But because that day is still a way off (if it will really come at all), testing your design the advanced browsers as well as legacy browsers is a necessary part of any project. The old-school way to test code was to load your website on as many computers as you could find, using as many different combinations of browsers and operating systems as possible. That was fine if you had access to a bunch of different computers (and had some time to kill). But there are much more efficient ways to test across browsers, using either free or commercial Web services and software. Free Cross-Browser Testing Good news: very powerful free testing tools are available for Web designers today. Access for All – Swiss foundation for accessible technologies - Freeware: PDF Accessibility Checker (PAC)
PDF-Accessibility-Checker (PAC 2) The freeware program PAC provides a fast way to test the accessibility of PDF files.
PAC supports both experts as well as end users conducting accessibility evaluations. The Matterhorn Protocol (PDF) is designed to foster adoption of PDF/UA by providing a set of 31 Checkpoints and 136 Failure Conditions that help software developers exchange detailed information on PDF/UA conformance and create software to make it easier for document authors to create fully accessible PDF files and forms. PAC 2, the new PDF Accessibility Checker from Access for All, a Swiss non-profit organisation, is the first implementation of the Matterhorn Protocol. PAC ist recommended by the World Wide Web Consortium (W3C): PDF Techniques for WCAG 2.0 Donate now! Overview evaluation tools in PAC 2 Technical check (1) Click «Start» for automated error checking. Detailed report (2) Analyze the specific errors in the document based on the detailed report. C mobileOK Basic Tests 1.0. If an HTTP request does not result in a valid HTTP response (because of network-level error, DNS resolution error, or non-HTTP response), FAIL If the HTTP status indicates redirection (status code 3xx): Do not carry out tests on the response If the response relates to a request for the resource under test, or any of its Included Resources (see 2.4.7 Included Resources): Include the size of the response in the "total size" as described under 3.16 PAGE_SIZE_LIMIT Include this response under the count as described under 3.6 EXTERNAL_RESOURCES If there is no HTTP Location header, FAIL.
If the URI identified by the HTTP Location header is a relative URI, create an absolute URI by combining the value of the Location header with the absolute URI of the request to which this is a response, warn If the resulting URI is not a URI with the scheme http or https, FAIL. Re-request the resource using the URI formulated above. If the HTTP status indicates that authentication is required (e.g. status code 401): Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0. This version: (plain text, postscript, pdf) This document is an appendix to: Latest version of Web Content Accessibility Guidelines 1.0: Editors: Wendy Chisholm, Trace R & D Center, University of Wisconsin -- Madison Gregg Vanderheiden, Trace R & D Center, University of Wisconsin -- Madison Ian Jacobs, W3C Copyright © 1999 W3C (MIT, INRIA, Keio), All Rights Reserved.
Abstract This document is an appendix to the W3C "Web Content Accessibility Guidelines 1.0". This list may be used to review a page or site for accessibility. A list version of the checkpoints is also available. This document has been produced as part of the Web Accessibility Initiative. Status of this document This document is an appendix to a document that has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. A list of current W3C Recommendations and other technical documents can be found at Please send comments about this document to email@example.com.
Web Content Accessibility Guidelines 1.0. W3C Recommendation 5-May-1999 This version: (plain text, PostScript, PDF, gzip tar file of HTML, zip archive of HTML) Latest version: Previous version: Editors: Wendy Chisholm, Trace R & D Center, University of Wisconsin -- Madison Gregg Vanderheiden, Trace R & D Center, University of Wisconsin -- Madison Ian Jacobs, W3C Copyright © 1999 W3C (MIT, INRIA, Keio), All Rights Reserved.
Abstract These guidelines explain how to make Web content accessible to people with disabilities. This is a reference document for accessibility principles and design ideas. This document is meant to be stable and therefore does not provide specific information about browser support for different technologies as that information changes rapidly. This document includes an appendix that organizes all of the checkpoints by topic and priority.
Google Demo - Gmail Signup.