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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add local abstract role usage warnings. fixes #1428 #1445

Merged
merged 2 commits into from May 6, 2021
Merged

add local abstract role usage warnings. fixes #1428 #1445

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
725e80b
add local abstract role usage warnings. fixes #1428
Apr 1, 2021
291f54f
Update index.html
jorycunningham Apr 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 13 additions & 13 deletions index.html
View file
Open in desktop
Expand Up @@ -2449,7 +2449,7 @@ <h2>Definition of Roles</h2>
<rdef>command</rdef>
<div class="role-description">
<p>A form of widget that performs an action but does not receive input data.</p>
<p class="note"><code>command</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>command</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>commmand</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -2710,7 +2710,7 @@ <h2>Definition of Roles</h2>
<div class="role-description">
<p>A <a>widget</a> that may contain navigable descendants or <a>owned</a> children.</p>
<p>Authors SHOULD ensure that a composite widget exists as a single navigation stop within the larger navigation system of the web page. Once the composite widget has focus, authors SHOULD provide a separate navigation mechanism for users to navigate to <a>elements</a> that are descendants or owned children of the composite element.</p>
<p class="note"><code>composite</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>composite</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>composite</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -4172,7 +4172,7 @@ <h2>Definition of Roles</h2>
<rdef>input</rdef>
<div class="role-description">
<p>A generic type of <a>widget</a> that allows user input.</p>
<p class="note"><code>input</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>input</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>input</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -4430,11 +4430,11 @@ <h2>Definition of Roles</h2>
<rdef>landmark</rdef>
<div class="role-description">
<p>A perceivable <rref>section</rref> containing content that is relevant to a specific, author-specified purpose and sufficiently important that users will likely want to be able to navigate to the section easily and to have it listed in a summary of the page. Such a page summary could be generated dynamically by a user agent or assistive technology.</p>
<p><code>landmark</code> is an abstract role used for the ontology. Authors MUST NOT use <code>landmark</code> role in content.</p>
<p>Authors designate the purpose of the content by assigning a role that is a subclass of the landmark role and, when needed, by providing a brief, descriptive label.</p>
<p>Elements with a role that is a subclass of the landmark role are known as <a>landmark</a> regions or navigational landmark regions.
<p>Elements with a role that is a subclass of the landmark role are known as <a>landmark</a> regions or navigational landmark regions.</p>
<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to landmark regions.
<a>User agents</a> MAY enable users to quickly navigate to landmark regions.</p>
<p class="note"><code>landmark</code> is an abstract role used for the ontology. Authors should not use this role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -6952,7 +6952,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<rdef>range</rdef>
<div class="role-description">
<p>An element representing a range of values.</p>
<p class="note"><code>range</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>range</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>range</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -7112,7 +7112,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<div class="role-description">
<p>The base <a>role</a> from which all other roles inherit.</p>
<p>Properties of this role describe the structural and functional purpose of <a>objects</a> that are assigned this role. A role is a concept that can be used to understand and operate instances.</p>
<p class="note"><code>roletype</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>roletype</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>roletype</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -7757,7 +7757,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<rdef>section</rdef>
<div class="role-description">
<p>A renderable structural containment unit in a document or application.</p>
<p class="note"><code>section</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>section</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>section</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -7827,7 +7827,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<rdef>sectionhead</rdef>
<div class="role-description">
<p>A structure that labels or summarizes the topic of its related section.</p>
<p class="note"><code>sectionhead</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>sectionhead</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>sectionhead</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -7902,7 +7902,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<rdef>select</rdef>
<div class="role-description">
<p>A form widget that allows the user to make selections from a set of choices.</p>
<p class="note"><code>select</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>select</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>select</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -8483,7 +8483,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<div class="role-description">
<p>A document structural <a>element</a>.</p>
<p><a>Roles</a> for document structure support the accessibility of dynamic web content by helping <a>assistive technologies</a> determine active content versus static document content. Structural roles by themselves do not all map to <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a>, but are used to create <a>widget</a> roles or assist content adaptation for assistive technologies.</p>
<p class="note"><code>structure</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>structure</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>structure</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -10255,7 +10255,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<div class="role-description">
<p>An interactive component of a graphical user interface (<abbr title="Graphical User Interface">GUI</abbr>).</p>
<p>Widgets are discrete user interface objects with which the user can interact. Widget <a>roles</a> map to standard features in <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a>. When the user navigates an element assigned any of the non-abstract subclass roles of <code>widget</code>, <a>assistive technologies</a> that typically intercept standard keyboard events SHOULD switch to an application browsing mode, and pass keyboard events through to the web application. The intent is to hint to certain <a>assistive technologies</a> to switch from normal browsing mode into a mode more appropriate for interacting with a web application; some <a>user agents</a> have a browse navigation mode where keys, such as up and down arrows, are used to browse the document, and this native behavior prevents the use of these keys by a web application.</p>
<p class="note"><code>widget</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
<p><code>widget</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>widget</code> role in content.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -10330,8 +10330,8 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
<div class="role-description">
<p>A browser or application window.</p>
<p><a>Elements</a> with this <a>role</a> have a window-like behavior in a graphical user interface (<abbr title="Graphical User Interface">GUI</abbr>) context, regardless of whether they are implemented as a native window in the operating system, or merely as a section of the document styled to look like a window.</p>
<p><code>window</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>window</code> role in content.</p>
<p class="note">In the description of this role, the term "application" does not refer to the <rref>application</rref> role, which specifies specific assistive technology behaviors.</p>
<p class="note"><code>window</code> is an <a href="#isAbstract">abstract role</a> used for the ontology.</p>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
Expand Down