Aspects Under Tests - Editorial updates (Shadi)

[moekraft]

8.0 Aspects Under Test
An aspect is a distinct part of the test subject or its underlying implementation. For example, rendering a particular piece of content to an end user involves multiple different technologies, some or all of which may be of interest to an ACT Rule. Some rules need to operate directly on the Hypertext Transfer Protocol [http11] messages exchanged between a server and a client, while others need to operate on the Document Object Model [DOM] tree exposed by a web browser.
Atomic rules MUST list the aspects used in the Test Definition. Some rules may need to operate on several aspects simultaneously, such as both the HTTP messages and the DOM tree.
An atomic rule MUST include a description of all the aspects under test by the rule. Some aspects are already well defined in a formal specification within the context of web content, such as HTTP messages, DOM tree, and CSS styling [CSS2]. These do not warrant a detailed description further than a reference to the corresponding section in this specification (see Common Aspects below). For other aspects that are not well defined, an ACT Rule SHOULD include either a detailed description of the aspect in question or a reference to that description.
Each aspect MUST be discrete with no overlap between the aspects.
There SHOULD NOT be an aspects under test list for composed rules.
Accessibility Conformance Testing.docx

[moekraft]

Note: Pull request #242 updates section 8.1 Common Aspects Under Test. Keeping these issues and PRs separate.

[moekraft]

Further comments from Shadi during review of PR #242 at weekly WCAG ACT TF meeting, 9/13/18.

[[
An aspect is a distinct part of the Test Subject or its underlying implementation. For example, rendering a particular piece of content to an end user can involve multiple different technologies, some or all of which can be of interest to an ACT Rule. Some rules need to operate directly on the Hypertext Transfer Protocol [[http11]] messages exchanged between a server and a client, while others need to operate on the Document Object Model [[DOM]] tree exposed by a web browser. Other rules need to operate on several aspects simultaneously, such as both the HTTP messages and the DOM tree.

[=Atomic rules=] MUST list the aspects used in the Test Definition. Each aspect MUST be discrete with no overlap between the aspects.

An atomic rule MUST include a description of all the aspects under test by the rule. Some aspects are already well defined within the context of web content, such as HTTP messages, DOM tree, and CSS styling [[CSS2]], and do not warrant a detailed description. Other aspects are not well defined or even specific to web content. In these cases, an ACT Rule SHOULD include either a detailed description of the aspect in question or a reference to that description.

A list of common aspects for reference in ACT rules can be found in Common Aspects under Test.

Since there is no Test Definition in Composed rules, there SHOULD NOT be an aspects under test list for composed rules.
]]

[moekraft]

PR #274 available for review https://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/w3c/wcag-act/b01af906514def95d00cdad1bc1d16cbe34d7add/act-rules-format.bs#input-aspects

[moekraft]

@WilcoFiers I submitted my edits under PR #274 These reflect Anne and Shadi's feedback as well as feedback from the WCAG ACT Meeting 9/20.