The philosophy of this test suite entails the concept of "roles" in testing. There are two roles defined: (1) the role of one (called "developer") who is knowledgeable of the authoring tool, and provides (necessary?) data to enable/assist the tester to run the tests, and (2) the role of one or more author(s) (called "tester(s)" - no prior knowledge of tool assumed) who may take this knowledge and run the tests, as specified following, to evaluate the claims made (by the developer?) on behalf of the authoring tool. Developer and tester may be the same individual, and more than one tester can run tests on the same tool.
It is important that the date and version of the specification tested against be mentioned in the tests. It would be good to provide some extra incentive for developers and testers for taking their time in filling out the forms? It is also important that QA work (including deprecation, obsoleting, variability, and classes of conformance) be taken into account. These templates should also be accessible (including to screen readers).
NOTE: These tests will be represented as templates (interactive forms) to be completed and submitted to another site. For now they are just HTML files. The test procedure (process of executing a test) is for a template (form): take the actions indicated, fill out the entries, and submit (to testreports site). Specific results of filling out the templates (forms) should be reproducible to the maximum extent possible, given the possible human interpretation of test results for certain of the tests. Reporting of results may be by machine or by human. It is desired that the templates be usable (easy and quick to fill out) to the maximum extent possible, and that it should be easy to move between templates.
At this point in time this document is informative (not-normative), and is consistent with the ATAG2.0 Techniques. Multiple means of navigation are possible through this document (maybe use XML test description with XSLT?). It is possible that in the future different kinds of tests or more complex tests may be included. It is possible that this test suite may be "configurable" in the future. For information on how to use this test suite (manual on the test suite and templates, how to execute tests to fill ou the forms, contents of the test suite, etc.), go to ?. For ATAG2.0 conformance info (including references to the ATAG spec/techniques), go to ? For W3C QA info, go to ?. For other WAI testing resources, go to ? The reference specifications for these tests are given in this document.
Naming conventions for templates (forms) indicate name of spec (atag), developer or tester, success criterion number, dash, and levels 1, 2, or 3 to refer to ATAG Conformance Levels A, AA, or AAA. This convention can be used as metadat for a filtering mechanism. The templates (forms) may be submitted (navigated) in any order; there are no "prerequisites" for use of any template. One may go directly from one template (form) to the next (or previous), or come back to this page for a different ordering (NOTE: Are these templates "approved" by the AUWG? Assuming so, the current status of each template (form) may be given as: under review, accepted, or rejected, according to specific criteria to be determined). Each template also links to a log history, containing, for example, creator of template, modification history, etc.). Are these templates "normative"? Does the AUWG want to define what PASS/FAIL mean? If you would like to suggest new templates (forms) or changes to existing templates (forms), please submit your information to ? Any deprecated and/or obsoleted features of ATAG1.0 which affect this ATAG2.0 test suite will be listed at this point. Any extensions to ATAG2.0 which affect this ATAG2.0 test suite will also be listed at this point.
NOTE: Tool designer is assumed knowledgable of tool; author is one who uses tool (no prior knowledge of tool assumed, but can be the same as tool designer, and can be many authors performing tests on a single tool). Test plan may include combinations of machine-testing and human-controlled testing.
NOTE: THE STATUS OF TEMPLATE DEVELOPMENT IS INDICATED, SO YOU CAN FOLLOW MY PROGRESS. ALSO, EVIDENCE TO SUPPORT YOUR ANSWER OF "YES/NO" FOR EACH TEMPLATE QUESTION "AFTER THE INVESTIGATION" CAN BE SUPPLIED VIA LINK IN THE ANSWER SPACE FOR EACH TEMPLATE QUESTION IF APPROPRIATE. ALSO, I THINK THAT THE ATAG TECHNIQUES SHOULD BE LINKED TO THE TESTS IN SOME WAY (BOTH AS A RECORD OF WHO USES THE TECHNIQUES AND OF HOW USE OF THE TECHNIQUES HELPS TO SATISFY THE SUCCESS CRITERIA). THEREFORE, SOME OF THE TEMPLATES INCLUDE QUESTIONS RELATED TO TECHNIQUES - STILL NOT SURE HOW TO HANDLE THIS - COMMENTS WELCOME. IF THE TESTER/DEVELOPER DOES NOT UNDERSTAND HOW TO ANSWER A PARTICULAR QUESTION ON A TEMPLATE, THERE WILL BE LINKS TO HELP..
This document is organized as follows: first comes the test report site where all test reports submitted for all templates are collected, and then comes the actual templates (in order of ATAG conformance level and success criteria within that level).
Any problems or issues with this test suite can be reported by email to ?; responses will be given in all instances.
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms)
Test Templates (Forms)
Test Templates (Forms)
Test Templates (Forms)
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):
Test Templates (Forms):