W3C home > Mailing lists > Public > public-pfwg@w3.org > September 2014

ACTION-1442 Draft spec text for aria-current

From: Léonie Watson <LWatson@PacielloGroup.com>
Date: Mon, 22 Sep 2014 08:37:43 +0100
To: "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Message-ID: <001b01cfd638$19240f60$4b6c2e20$@PacielloGroup.com>
This is a modified version of Brian’s original draft text for aria-current



Indicates the current element within a navigation container.


The aria-current attribute indicates whether the element is current (true),
or not current (false). If the aria-current attribute is false, the current
state of the element should not be conveyed by User Agents.


For example, aria-current may be used to indicate the current step in a
process, or the current document within a collection.



The aria-current attribute is similar to the aria-selected attribute, but
there are important differences. the aria-selected attribute indicates the
selected state of children within certain widgets, whilst the aria-current
attribute indicates the current element within the scope of a navigation


Characteristics of aria-current

Used in roles: ?

Value: true/false/undefined


Values of aria-current

true: The element is current

false: The element is not current

undefined: The element cannot be current



The original draft text allowed aria-current to be used on all elements of
the base markup. I’m not sure this is the right approach, but equally I’m
not sure how best to constrain it in the spec text. I also feel that
"navigation container" is too vague a term to be practically useful. 


Thoughts on this, and the draft text as it stands, very welcome.




[1] https://www.w3.org/WAI/PF/Group/track/actions/1442




Léonie Watson – Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup

Received on Monday, 22 September 2014 07:38:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:08 UTC