From 0c47c14169b841d54d3f30b2affbcb24a3dda409 Mon Sep 17 00:00:00 2001 From: Joanmarie Diggs Date: Wed, 5 Jul 2017 15:07:52 -0400 Subject: [PATCH] Counter-proposal regarding aria-roledescription --- aria/aria.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aria/aria.html b/aria/aria.html index 5f7357e77..45433cec2 100644 --- a/aria/aria.html +++ b/aria/aria.html @@ -10309,8 +10309,8 @@

Definitions of States and Properties (all aria-* attributes)

Some assistive technologies, such as screen readers, present the role of an element as part of the user experience. Such assistive technologies typically localize the name of the role, and they may customize it as well. Users of these assistive technologies depend on the presentation of the role name, such as "region," "button," or "slider," for an understanding of the purpose of the element and, if it is a widget, how to interact with it.

The aria-roledescription property gives authors the ability to override how assistive technologies localize and express the name of a role. Thus inappropriately using aria-roledescription may inhibit users' ability to understand or interact with an element. Authors SHOULD limit use of aria-roledescription to clarifying the purpose of non-interactive container roles like group or region, or to providing a more specific description of a widget.

User agents MUST NOT expose the aria-roledescription attribute if the value of aria-roledescription is empty or contains only whitespace characters.

-

If aria-roledescription is applied to a generic or semantically meaningless presentational element (for example, div or span in HTML), user agents SHOULD NOT expose aria-roledescription unless the author also defines an explicit WAI-ARIA role value. -

If aria-roledescription is applied to a semantically meaningful host language element whose implicit role semantic is not defined by WAI-ARIA, user agents SHOULD expose aria-roledescription, even if the author does not provide an explicit WAI-ARIA role value. +

User agents MUST expose the aria-roledescription attribute if a valid value is applied to a host language interactive control.

+

If aria-roledescription is applied to a host language container element, user agents MUST NOT expose aria-roledescription unless the author also defines an explicit WAI-ARIA role value, or the host language has explicitly identified the element as supporting aria-roledescription.

Assistive technologies SHOULD use the value of aria-roledescription when presenting the role of an element, but SHOULD NOT change other functionality based on the role of an element that has a value for aria-roledescription. For example, an assistive technology that provides functions for navigating to the next region or button would allow those functions to navigate to regions and buttons that have an aria-roledescription.

The following two examples show the use of aria-roledescription to indicate that a non-interactive container is a "slide" in a web-based presentation application.

<div role="region" aria-roledescription="slide" id="slide42" aria-labelledby="slide42heading">