Re: ACTION-1442: Draft spec text for aria-current and aria-currentfor

Right, really good points about displayed vs hidden in the CSS sense..... 
displayed is lousy idea due to that fact alone.

aria-YouAreHere ...LoL ...

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com



From:   Joseph Scheuhammer <clown@alum.mit.edu>
To:     Matthew King/Fishkill/IBM@IBMUS, Alexander Surkov 
<surkov.alexander@gmail.com>, 
Cc:     Joseph Scheuhammer <clown@alum.mit.edu>, W3C WAI Protocols & 
Formats <public-pfwg@w3.org>
Date:   11/19/2014 12:07 PM
Subject:        Re: ACTION-1442: Draft spec text for aria-current and 
aria-currentfor



On 2014-11-19 2:15 PM, Matthew King wrote:
> Alex wrote:
> > displayed sounds like visible with me, something on the screen
>
> Yes, that is the understanding we want to convey, right? 

I thought the semantic we wanted to convey is "you are here". The 
essential character or @aria-current is orientation, as in "you are on 
this page in a collection of pages", or "you are at this step in a 
online purchasing web app",  Maybe @aria-here would be better than 
@aria-current; not sure.

> 2. When it comes to authors, I would think it would be much easier to 
> understand the difference between displayed and selected vs current 
> and selected. 

Authors also have to contend with @aria-hidden, HTML5 @hidden, CSS 
visibility:hidden, CSS display:none, CSS overflow:hidden, and maybe 
others.  It is not a good idea to add another aria attribute, 
@aria-displayed, that seems to have something to do with what is rendered.

-- 
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -