New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update documents to reflect ACT format latest draft #69
Conversation
pages/design/rule-design.md
Outdated
|
||
6. **[Selector](#selector)**: Use selectors to group the tests by page element and Success Criterion. | ||
6. **[Expectations](#expectations)**: Assert everything what must be true about the target elements, in order for them to pass the rule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assert everything that must be true
or
Assert what must be true
pages/design/rule-design.md
Outdated
|
||
**Note**: The rule should specify the minimum level of pre-processing. A test that is carried out on the DOM can usually also be carried out on the rendered page but the the latter needs more processing power. It should also be kept in mind that the use of a (headless) browser can introduce bugs in the test procedure. | ||
Other aspects may be necessary for testing. These can be added as well as long as they are sufficiently defined. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove "as well"
pages/design/rule-design.md
Outdated
|
||
The selectors help the user (or tool) identify what has to be checked. The goal of the Auto-WCAG test design is to cover the complete workflow, i.e. all steps / all tests that are necessary to reach a conclusion. The procedure contains automated and manual steps. Usually a combination of both. | ||
Each expectation exposes a reason why an element may not meet a particular conformance requirement. The expectations can be "linked", in that one has to be met before a second can be tested. For example, a rule testing link names may have as its first expectation "Target element has an accessible name", and as a second expectation "Expectation 1 is true for the target element, and the accessible name is describes the function of the target element". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove the last "is" in the final sentence
pages/structure/aggregation.md
Outdated
@@ -2,20 +2,19 @@ | |||
title: Result Aggregation | |||
--- | |||
|
|||
Each test case of the Auto-WCAG group is related to a specific WCAG 2.0 success criterion. A success criterion can (and usually does) have multiple test cases associated with it. Each test case can have one of three outcomes: Pass, CannotTell and Fail. The results of individual test cases can be combined in the following manner, to find the result of a specific success criterion. | |||
Each rule of the Auto-WCAG group is related to a specific WCAG 2.x success criterion. A success criterion can (and usually does) have multiple rules associated with it. Each rule can have one of three outcomes: Pass, CannotTell and Fail. The results of individual rule can be combined in the following manner, to find the result of a specific success criterion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last rule should be rules
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments for minor edits
List of changes to make:
|
No description provided.