| OLD | NEW |
|---|
| 1 Wai-aria: Tests for the WAI-ARIA Recommendations | 1 dpub-aria: Tests for the DPUB-ARIA Recommendations |
| 2 ================================================ | 2 ================================================== |
| 3 | 3 |
| 4 The [WAI ARIA Recommendations](https://www.w3.org/TR/wai-aria) | 4 The [DPUB ARIA Recommendation](https://www.w3.org/TR/dpub-aria-1.0) |
| 5 define extensions to HTML4/5 for support of extended semantics. These | 5 define extensions to HTML4/5 for support of extended semantics. These |
| 6 semantics make it easier for Assistive Technologies to intepret and | 6 semantics make it easier for Assistive Technologies to intepret and |
| 7 present content to users with varying physical and cognitive abilities. | 7 present content to users with varying physical and cognitive abilities. |
| 8 | 8 |
| 9 The purpose of these tests is to help ensure that user agents support the | 9 The purpose of these tests is to help ensure that user agents support the |
| 10 requirements of the Recommendations. | 10 requirements of the Recommendation. |
| 11 | 11 |
| 12 The general approach for this testing is to enable both manual and automated | 12 The general approach for this testing is to enable both manual and automated |
| 13 testing, with a preference for automation. | 13 testing, with a preference for automation. |
| 14 | 14 |
| 15 | 15 |
| 16 Running Tests | 16 Running Tests |
| 17 ------------- | 17 ------------- |
| 18 | 18 |
| 19 In order to run these tests in an automated fashion, you will need to have a | 19 In order to run these tests in an automated fashion, you will need to have a |
| 20 special Assistive Technology Test Adapter (ATTA) for the platform under test.
We will | 20 special Assistive Technology Test Adapter (ATTA) for the platform under test. W
e will |
| 21 provide a list of these for popular platforms here as they are made available. | 21 provide a list of these for popular platforms here as they are made available. |
| 22 | 22 |
| 23 The ATTA will monitor the window under test via the platforms Accessibility | 23 The ATTA will monitor the window under test via the platforms Accessibility |
| 24 Layer, forwarding information about the Accessibility Tree to the running test | 24 Layer, forwarding information about the Accessibility Tree to the running test |
| 25 so that it can evaluate support for the various features under test. | 25 so that it can evaluate support for the various features under test. |
| 26 | 26 |
| 27 The workflow for running these tests is something like: | 27 The workflow for running these tests is something like: |
| 28 | 28 |
| 29 1. Start up the ATTA for the platform under test, informing it of the location | 29 1. Start up the ATTA for the platform under test. |
| 30 of the test server and the user agent to be tested. | 30 2. Start up the test driver window and select the dpub -aria tests to be run |
| 31 2. Start up the test driver window and select the wai-aria tests to be run | 31 (e.g., the DPUB ARIA 1.0 tests) - click "Start" |
| 32 (e.g., the ARIA 1.1 tests) - click "Start" | |
| 33 3. A window pops up that shows a test - the description of which tells the | 32 3. A window pops up that shows a test - the description of which tells the |
| 34 tester what is being tested. In an automated test, the test with proceed | 33 tester what is being tested. In an automated test, the test with proceed |
| 35 without user intervention. In a manual test, some user input may be required | 34 without user intervention. In a manual test, some user input may be required |
| 36 in order to stimulate the test. | 35 in order to stimulate the test. |
| 37 4. The test runs. Success or failure is determined and reported to the test | 36 4. The test runs. Success or failure is determined and reported to the test |
| 38 driver window, which then cycles to the next test in the sequence. | 37 driver window, which then cycles to the next test in the sequence. |
| 39 5. Repeat steps 2-4 until done. | 38 5. Repeat steps 2-4 until done. |
| 40 6. Download the JSON format report of test results, which can then be visually | 39 6. Download the JSON format report of test results, which can then be visually |
| 41 inspected, reported on using various tools, or passed on to W3C for | 40 inspected, reported on using various tools, or passed on to W3C for |
| 42 evaluation and collection in the Implementation Report via github. | 41 evaluation and collection in the Implementation Report via github. |
| (...skipping 13 matching lines...) Expand all Loading... |
| 56 be automatically included in documents generated by | 55 be automatically included in documents generated by |
| 57 [wptreport](https://www.github.com/w3c/wptreport). The same tool can be used | 56 [wptreport](https://www.github.com/w3c/wptreport). The same tool can be used |
| 58 locally to view reports about recorded results. | 57 locally to view reports about recorded results. |
| 59 | 58 |
| 60 | 59 |
| 61 Writing Tests | 60 Writing Tests |
| 62 ------------- | 61 ------------- |
| 63 | 62 |
| 64 If you are interested in writing tests for this environment, see the | 63 If you are interested in writing tests for this environment, see the |
| 65 associated [CONTRIBUTING](CONTRIBUTING.md) document. | 64 associated [CONTRIBUTING](CONTRIBUTING.md) document. |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2477133002:
Import wpt@306326cfe973b6c7019c50879ad03b02825c7539 (Closed)
