RE: ACTION-1442 Default state of aria-current

Brian Garaventa wrote:

“So, if undefined, the user agent sets no current flag either way.

If false, the current flag is set to false,

And if true, the current flag is set to true.

 

Then the screen reader for example can convey that, when a flag is present,
that an element is currently active or not currently active based on whether
the flag is set, or convey nothing at all if the flag is undefined.

 

Would this make sense?”

 

Thanks Brian. I’m actually starting to wonder whether we’re
over-complicating this attribute?

 

The original use case for aria-current was to identify the current element
within a collection, for example the current page as represented by a link
in a list. In that scenario, I’m not sure there is a use case for informing
the user that the other elements in the collection are not the current one.

 

At the moment the proposed scope for aria-current is a navigation container,
but a navigation container isn’t a collection. The more I look at this, the
more I wonder whether aria-attribute should be scoped to a list, and for its
default state to be false.

 

Léonie.

 

 

 

 

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup

 

From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
Sent: 09 June 2014 16:55
To: LWatson@PacielloGroup.com; 'W3C WAI Protocols & Formats'
Subject: RE: ACTION-1442 Default state of aria-current

 

If aria-current is included within an element node, but it’s value is null
“” or includes a value other than “true” or “false”, shouldn’t this be
treated the same as undefined?

 

Please correct me if I’m wrong, but this seems to make sense for a Boolean
attribute.

 

So, if undefined, the user agent sets no current flag either way.

If false, the current flag is set to false,

And if true, the current flag is set to true.

 

Then the screen reader for example can convey that, when a flag is present,
that an element is currently active or not currently active based on whether
the flag is set, or convey nothing at all if the flag is undefined.

 

Would this make sense?

 

From: Léonie Watson [mailto:lwatson@paciellogroup.com] 
Sent: Saturday, June 07, 2014 1:57 PM
To: 'W3C WAI Protocols & Formats'
Subject: ACTION-1442 Default state of aria-current

 

TF,

 

What should the default state of aria-current be? In the draft spec text
from brian, it has an undefined state, but I’m wondering whether its default
state should be false?

 

Is there a use case for indicating which element(s) are not current, or just
the one that is?

 

 

Léonie.

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup