From 725e80b6809e1d823eacb650164c69299820a918 Mon Sep 17 00:00:00 2001 From: Jory Cunningham Date: Thu, 1 Apr 2021 11:50:13 -0400 Subject: [PATCH 1/2] add local abstract role usage warnings. fixes #1428 --- index.html | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/index.html b/index.html index 5dc3f9c4c..67435a4f4 100644 --- a/index.html +++ b/index.html @@ -2449,7 +2449,7 @@

Definition of Roles

command

A form of widget that performs an action but does not receive input data.

-

command is an abstract role used for the ontology.

+

command is an abstract role used for the ontology. Authors MUST NOT use commmand role in content.

@@ -2710,7 +2710,7 @@

Definition of Roles

A widget that may contain navigable descendants or owned children.

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 elements that are descendants or owned children of the composite element.

-

composite is an abstract role used for the ontology.

+

composite is an abstract role used for the ontology. Authors MUST NOT use composite role in content.

Characteristics:
@@ -4172,7 +4172,7 @@

Definition of Roles

input

A generic type of widget that allows user input.

-

input is an abstract role used for the ontology.

+

input is an abstract role used for the ontology. Authors MUST NOT use input role in content.

Characteristics:
@@ -4430,11 +4430,11 @@

Definition of Roles

landmark

A perceivable section 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.

+

landmark is an abstract role used for the ontology. Authors should not use this role in content. Authors MUST NOT use landmark role in content.

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.

-

Elements with a role that is a subclass of the landmark role are known as landmark regions or navigational landmark regions. +

Elements with a role that is a subclass of the landmark role are known as landmark regions or navigational landmark regions.

Assistive technologies SHOULD enable users to quickly navigate to landmark regions. User agents MAY enable users to quickly navigate to landmark regions.

-

landmark is an abstract role used for the ontology. Authors should not use this role in content.

Characteristics:
@@ -6952,7 +6952,7 @@
Note regarding the ARIA 1.1 none role.
range

An element representing a range of values.

-

range is an abstract role used for the ontology.

+

range is an abstract role used for the ontology. Authors MUST NOT use range role in content.

Characteristics:
@@ -7112,7 +7112,7 @@
Note regarding the ARIA 1.1 none role.

The base role from which all other roles inherit.

Properties of this role describe the structural and functional purpose of objects that are assigned this role. A role is a concept that can be used to understand and operate instances.

-

roletype is an abstract role used for the ontology.

+

roletype is an abstract role used for the ontology. Authors MUST NOT use roletype role in content.

Characteristics:
@@ -7757,7 +7757,7 @@
Note regarding the ARIA 1.1 none role.
section

A renderable structural containment unit in a document or application.

-

section is an abstract role used for the ontology.

+

section is an abstract role used for the ontology. Authors MUST NOT use section role in content.

Characteristics:
@@ -7827,7 +7827,7 @@
Note regarding the ARIA 1.1 none role.
sectionhead

A structure that labels or summarizes the topic of its related section.

-

sectionhead is an abstract role used for the ontology.

+

sectionhead is an abstract role used for the ontology. Authors MUST NOT use sectionhead role in content.

Characteristics:
@@ -7902,7 +7902,7 @@
Note regarding the ARIA 1.1 none role.
select

A form widget that allows the user to make selections from a set of choices.

-

select is an abstract role used for the ontology.

+

select is an abstract role used for the ontology. Authors MUST NOT use select role in content.

Characteristics:
@@ -8483,7 +8483,7 @@
Note regarding the ARIA 1.1 none role.

A document structural element.

Roles for document structure support the accessibility of dynamic web content by helping assistive technologies determine active content versus static document content. Structural roles by themselves do not all map to accessibility APIs, but are used to create widget roles or assist content adaptation for assistive technologies.

-

structure is an abstract role used for the ontology.

+

structure is an abstract role used for the ontology. Authors MUST NOT use structure role in content.

Characteristics:
@@ -10255,7 +10255,7 @@
Note regarding the ARIA 1.1 none role.

An interactive component of a graphical user interface (GUI).

Widgets are discrete user interface objects with which the user can interact. Widget roles map to standard features in accessibility APIs. When the user navigates an element assigned any of the non-abstract subclass roles of widget, assistive technologies 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 assistive technologies to switch from normal browsing mode into a mode more appropriate for interacting with a web application; some user agents 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.

-

widget is an abstract role used for the ontology.

+

widget is an abstract role used for the ontology. Authors MUST NOT use widget role in content.

Characteristics:
@@ -10330,8 +10330,8 @@
Note regarding the ARIA 1.1 none role.

A browser or application window.

Elements with this role have a window-like behavior in a graphical user interface (GUI) 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.

+

window is an abstract role used for the ontology. Authors MUST NOT use window role in content.

In the description of this role, the term "application" does not refer to the application role, which specifies specific assistive technology behaviors.

-

window is an abstract role used for the ontology.

Characteristics:
From 291f54f2c032bd5fe04f5b19cb4cc90557daca1d Mon Sep 17 00:00:00 2001 From: Jory Cunningham Date: Thu, 8 Apr 2021 15:54:02 -0400 Subject: [PATCH 2/2] Update index.html Co-authored-by: Carolyn MacLeod --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 67435a4f4..585e29207 100644 --- a/index.html +++ b/index.html @@ -4430,7 +4430,7 @@

Definition of Roles

landmark

A perceivable section 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.

-

landmark is an abstract role used for the ontology. Authors should not use this role in content. Authors MUST NOT use landmark role in content.

+

landmark is an abstract role used for the ontology. Authors MUST NOT use landmark role in content.

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.

Elements with a role that is a subclass of the landmark role are known as landmark regions or navigational landmark regions.

Assistive technologies SHOULD enable users to quickly navigate to landmark regions.

Characteristics: