textarea and input[type="text"] elements, and ARIA textbox, gridcell and combobox widgets
To identify a required form control, add the HTML5 required attribute to the standard form controls.
If compatibility with HTML4 standards or legacy browsers and assistve technologies, you can also use aria-required="true" to indicate a form control is required.
Use the required attribute (or the aria-required if used) as the CSS selector for visually styling the form control as required. This ensures that the visual state stays synchronized with the accessibility API state used by assistive technologies.
The only reason to support both required and aria-required on the same form control is to support legacy browsers and assistive technologies. This required extra care to make sure the two values do not conflict. If they do conflict the required attribute will override the aria-required property value.
Information about the element associated with the result.
The information typically includes the tag name, accessible name or other information related to the rule requirements.
"Page" means that the result applied to the page. For example, the rule "One main landmark on the page" is a page level rule.
The element position is based on the DOM order of elements in the page.
The element position maybe useful in helping to locate a specific element on the page evaluated (e.g smaller numbers are typically toward the beginning of a page and larger numbers typically toward the end of a page).
Element position 1 is the first element.
The highest element position is the last element.
Element position values for most rule/page results will not be consecutive since a rule only applies to a sub set of elements found on a page.