Updated to reflect changes related to presentationNumbers and references.
Revised testId and assertionId descriptions:
* Only include characters `a-z`, `0-9`, and dash ("-").
* Be generated from the test title by removing extraneous words, shortening some common words (e.g., navigate to nav), converting to lowercase, capitalizing the first letter of the second and subsequent words, and removing spaces and punctuation.
* Be generated from the `assertionStatement` by removing extraneous words (e.g., 'conveyed'), shortening some common words, converting to lowercase, capitalizing the first letter of the second and subsequent words, and removing spaces and punctuation.
Revised presentationNumber specifications for tests and commands:
* A positive number that controls the order of presentation of tests in the test runner and reports. By default, tests will be presented in numerical ascending order using the values in this column, i.e., the values are `Number`, not `String`, primatives when sorted.
* A positive number that controls the order of presentation of commands in the test runner and reports. By default, commands within a test will be presented in numerical ascending order using the values in this column, i.e., the values are `Number`, not `String`, primatives when sorted.
Revised requirements related to refId values as described in the assertion and references sections:
* The refId values designate references to the ARIA or HTML-AAM specification covered by the assertion. Typically, an assertion should cover only one ARIA or HTML feature. Some assertions will cover a behavior that is not described by any specification, so this cell will be blank in those rows.
* The convention for ARIA attributes is that the `refId` is equivalent to the ARIA attribute, e.g., `slider` or `aria-orientation`. For HTML-AAM mappings, it is a good idea to avoid ambiguity by using a `refId` that includes the string `html`, e.g., `htmlButton`, or `htmlLink`.
Defined new values for reference types:
* `metadata`: Indicates the `refId` is for information that applies to all tests in the plan.
* `aria`: Indicates that the refId is for an ARIA attribute specification.
* `htmlAam`: Indicates the refId is for an HTML element mapping specification.
Revised reference value specification for `aria` and `htmlAam` reference types.
Added requirements for `linkText`.
Added a section describing how link text and href values are calculated for reference links.
Updated validation rules.