Skip to content

editorial: clarify RFC terms #2488

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Mar 27, 2025
Merged

editorial: clarify RFC terms #2488

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
03eca31
editorial: clarify RFC terms
pkra Mar 24, 2025
e8bae65
chore: prettier
pkra Mar 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 15 additions & 34 deletions dpub-aam/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,22 +192,13 @@ <h2>Introduction</h2>
</p>
</section>
<section id="conformance" class="normative">
<section id="rfc-2119-keywords">
<h3>RFC-2119 Keywords</h3>

<p>
RFC-2119 keywords are formatted in uppercase and contained in a <code>strong</code> element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this
format, they do not convey formal information in the RFC 2119 sense, and are merely explanatory (i.e., informative). As much as possible, such usages are avoided in this specification.
</p>
</section>

<section id="normative-and-informative-sections">
<h3>Normative and Informative Sections</h3>

<p>The indication whether a section is normative or non-normative (informative) applies to the entire section including sub-sections.</p>

<p>
Informative sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow such
Informative sections provide information useful to understanding the specification. Such sections can contain examples of recommended practice, but it is not required to follow such
recommendations in order to conform to this specification.
</p>
</section>
Expand All @@ -227,7 +218,7 @@ <h3>Roles deprecated in DPUB-ARIA</h3>
<h2>Supporting keyboard navigation</h2>

<p>
Enabling keyboard navigation in web applications is a necessary step toward making accessible web applications possible. Conforming [=user agents=] <span class="rfc2119">MUST</span> conform to
Enabling keyboard navigation in web applications is a necessary step toward making accessible web applications possible. Conforming [=user agents=] MUST conform to
<a class="core-mapping" data-cite="core-aam-1.1#keyboard-focus">Supporting Keyboard Navigation</a> requirements in [[!CORE-AAM-1.1]].
</p>
</section>
Expand All @@ -237,25 +228,19 @@ <h2>Mapping <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> t
<section id="mapping_general">
<h3>General rules for exposing <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> semantics</h3>

<p>
This section <span class="rfc2119">MUST</span> conform to <a class="core-mapping" data-cite="core-aam-1.1#mapping_general">General rules for exposing WAI-ARIA semantics</a> in
[[!CORE-AAM-1.1]].
</p>
<p>This section MUST conform to <a class="core-mapping" data-cite="core-aam-1.1#mapping_general">General rules for exposing WAI-ARIA semantics</a> in [[!CORE-AAM-1.1]].</p>
</section>
</section>
<section id="mapping_conflicts">
<h2>Conflicts between native markup semantics and <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr></h2>

<p>
User agents <span class="rfc2119">MUST</span> conform to <a class="core-mapping" data-cite="core-aam-1.1#mapping_conflicts">Conflicts between native markup semantics and WAI-ARIA</a> in
[[!CORE-AAM-1.1]].
</p>
<p>User agents MUST conform to <a class="core-mapping" data-cite="core-aam-1.1#mapping_conflicts">Conflicts between native markup semantics and WAI-ARIA</a> in [[!CORE-AAM-1.1]].</p>
</section>
<section id="mapping_nodirect">
<h2>Exposing attributes that do not directly map to accessibility <abbr title="application programming interface">API</abbr> properties</h2>

<p>
User agents <span class="rfc2119">MUST</span> conform to
User agents MUST conform to
<a class="core-mapping" data-cite="core-aam-1.1#mapping_nodirect"
>Exposing attributes that do not directly map to accessibility <abbr title="application programming interface">API</abbr> properties</a
>
Expand All @@ -267,7 +252,7 @@ <h2>Role mapping</h2>

<p>
Platform <a class="termref">accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a> traditionally have had a finite set of predefined <a class="termref">roles</a> that
are expected by <a class="termref">assistive technologies</a> on that platform and only one or two roles may be exposed. In contrast,
are expected by <a class="termref">assistive technologies</a> on that platform and only one or two roles are usually exposed. In contrast,
<abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> allows multiple roles to be specified as an ordered set of space-separated valid role tokens. The additional roles are
fallback roles similar to the concept of specifying multiple fonts in case the first choice font type is not supported.
</p>
Expand All @@ -276,8 +261,8 @@ <h2>Role mapping</h2>
<h3>General Rules</h3>

<p>
User agents <span class="rfc2119">MUST</span> conform to the Role Mapping <a class="core-mapping" data-cite="core-aam-1.1#roleMappingGeneralRules">General Rules</a> accessibility API
computational requirements in [[!CORE-AAM-1.1]].
User agents MUST conform to the Role Mapping <a class="core-mapping" data-cite="core-aam-1.1#roleMappingGeneralRules">General Rules</a> accessibility API computational requirements in
[[!CORE-AAM-1.1]].
</p>
</section>

Expand Down Expand Up @@ -2574,7 +2559,7 @@ <h2>Translatable Values</h2>
attribute value is the same as the <a data-cite="html#language">language</a> and <a data-cite="html#the-directionality">directionality</a> of the element [[html]].
</p>

<p>To be understandable by assistive technology users, the following <code>role</code> mapping values intended for human consumption should be translated when a page is localized:</p>
<p>To be understandable by assistive technology users, the following <code>role</code> mapping values intended for human consumption SHOULD be translated when a page is localized:</p>

<ul>
<li>AXRoleDescription</li>
Expand All @@ -2588,7 +2573,7 @@ <h2>State and Property Mapping</h2>

<p>
This section describes how to expose <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a class="termref">states</a> and object
<a class="termref" data-cite="wai-aria#dfn-property">properties</a>. User agents <span class="rfc2119">MUST</span> conform to the
<a class="termref" data-cite="wai-aria#dfn-property">properties</a>. User agents MUST conform to the
<a data-cite="core-aam-1.1#mapping_state-property" class="core-mapping">State and Property Mapping</a> accessibility API computational requirements in [[!CORE-AAM-1.1]].
</p>
</section>
Expand All @@ -2608,34 +2593,30 @@ <h3>Name and Description</h3>
<h3>Relations</h3>

<p>
User agents <span class="rfc2119">MUST</span> conform to the <a data-cite="core-aam-1.1#mapping_additional_relations" class="core-mapping">Relation</a> accessibility API computational
requirements in [[!CORE-AAM-1.1]].
User agents MUST conform to the <a data-cite="core-aam-1.1#mapping_additional_relations" class="core-mapping">Relation</a> accessibility API computational requirements in [[!CORE-AAM-1.1]].
</p>
</section>

<section id="mapping_additional_position">
<h3>Group Position</h3>

<p>
User agents <span class="rfc2119">MUST</span> conform to the <a data-cite="core-aam-1.1#mapping_additional_position" class="core-mapping">Group Position</a> accessibility API computational
requirements in [[!CORE-AAM-1.1]].
User agents MUST conform to the <a data-cite="core-aam-1.1#mapping_additional_position" class="core-mapping">Group Position</a> accessibility API computational requirements in
[[!CORE-AAM-1.1]].
</p>
</section>
</section>
<section id="mapping_actions">
<h2>Actions</h2>

<p>
User agents <span class="rfc2119">MUST</span> conform to the <a data-cite="core-aam-1.1#mapping_actions" class="core-mapping">Actions</a> accessibility API computational requirements in
[[!CORE-AAM-1.1]].
</p>
<p>User agents MUST conform to the <a data-cite="core-aam-1.1#mapping_actions" class="core-mapping">Actions</a> accessibility API computational requirements in [[!CORE-AAM-1.1]].</p>
</section>
<section id="mapping_events">
<h2>Events</h2>

<p>
[=user agents=] fire <a class="termref">events</a> for user actions, <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a class="termref">state</a> changes, changes to
document content or node visibility, changes in selection, and operation of menus. Conforming [=user agents=] <span class="rfc2119">MUST</span> support the [[!CORE-AAM-1.1]]
document content or node visibility, changes in selection, and operation of menus. Conforming [=user agents=] MUST support the [[!CORE-AAM-1.1]]
<a class="core=mappings" data-cite="core-aam-1.1#mapping_events">Events</a> mappings.
</p>
</section>
Expand Down
6 changes: 3 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -792,9 +792,9 @@ <h2>Non-interference with the Host Language</h2>
language.
</p>
<p>
If a CSS selector includes a WAI-ARIA attribute (e.g., <code class="highlight css">input[aria-invalid="true"]</code>), user agents MUST update the visual display of any elements
matching (or no longer matching) the selector any time the attribute is added/changed/removed in the <abbr title="Document Object Model">DOM</abbr>. The user agent MAY alter the mapping of
the host language features into an <a>accessibility <abbr title="Application Programming Interface">API</abbr></a
If a CSS selector includes a WAI-ARIA attribute (e.g., <code class="highlight css">input[aria-invalid="true"]</code>), user agents MUST update the visual display of any elements matching (or
no longer matching) the selector any time the attribute is added/changed/removed in the <abbr title="Document Object Model">DOM</abbr>. The user agent MAY alter the mapping of the host
language features into an <a>accessibility <abbr title="Application Programming Interface">API</abbr></a
>, but the user agent MUST NOT alter the <abbr title="Document Object Model">DOM</abbr> in order to remap <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup into host
language features.
</p>
Expand Down
Loading