ARIA Best Practices Quality Assurance (QA)

This page is the starting point for assuring the quality, functionality, and coding of the examples included in the ARIA Best Practices document. A Test Case Test Matrix is also available as an external resource.

Goals of ARIA Best Practices Quality Assurance Testing

The goals of this QA exercise is to provide:

comprehensive testing of all example files
- A) this means keeping a log of example files as they are added to the wiki; Links to resources containing test files, sample widgets, etc. are available on this wiki.
testing with multiple configurations -- what needs to be defined is precisely what comprises a "configuration" for purposes of our testing protocol; what is needed is a mix of platforms/operating systems, user agents, assistive technologies, and inspection tools (DOM viewers and the like)
parallel testing of sample/example code, using DOM Inspector ensuring that code is properly implemented
testing criteria -- this should be self-evident from the parent page to which an example has been attached -- the parent page should describe expected action, so a tester has an exact idea of what it is he or she is testing, vis a vis ARIA markup and implementation
a "test template" would be the best way to shape feedback, as it could list "required" information (such as software configuration, etc.) so that all feedback is uniform in depth and scope, and can be replicated by a "disinterested third party"
- A) ARIA Best Practices QA Test Template (note: this is a generalized mock-up of the template; individually tailored templates for each concept test will be added to the Test Case Test Matrix