Skip to content
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

Addition: clarify when to expose a required element as invalid #429

Merged
merged 10 commits into from
Oct 3, 2023
11 changes: 11 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -4989,6 +4989,17 @@ <h3>HTML Attribute State and Property Mappings</h3>
<td class="ax"><div class="general">Use WAI-ARIA mapping</div></td>
<td class="comments">
If the element includes both the `required` attribute and the `aria-required` attribute with a valid value, User Agents MUST expose only the `required` attribute value.
<p>
If an element is <a data-cite="html/input.html#concept-input-required">required</a>, user agents MUST NOT expose the
element with an intitial invalid state (<a class="core-mapping" href="#ariaInvalidTrue">`aria-invalid="true"`</a>).
The user agent SHOULD expose the invalid state only after <strong>1)</strong> a user has purposefully interacted with a required element,
or attempted to submit a form and <strong>2)</strong> the element, or elements, do not meet
<a data-cite="html/form-control-infrastructure.html#constraint-validation">constraint validation</a>.
</p>
<p>
Until these conditions are met, user agents MUST expose the elements as
(<a class="core-mapping" href="#ariaInvalidFalse">`aria-invalid="false"`</a>).
</p>
</td>
</tr>
<tr tabindex="-1" id="att-reversed">
Expand Down