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

Yes, I agree that screen reader users could initially struggle if they do 
not pickup on such suttle aspects of the UI.
None of this is intuitively obvious for a screen reader user.
I have no idea how good it is for others who can see it.

Once you understand how it works, it is simple and efficient, but 
discovery is a real problem. I have found that to be the case with many 
aspects of rich internet apps for typical screen reader users. We can fix 
a lot of this with screen readers (and even browsers) that better use the 
intelligence provided by ARIA. ... it is a bit of a chicken/egg problem... 
years of work to do ... 

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:   Léonie Watson <LWatson@PacielloGroup.com>
To:     Matthew King/Fishkill/IBM@IBMUS, 
Cc:     <public-pfwg@w3.org>
Date:   11/19/2014 09:47 AM
Subject:        RE: ACTION-1442: Draft spec text for aria-current and 
aria-currentfor



Matt King wrote:
“Léonie, I have applications that have a problem right now because we do 
not have both current and selected available. 
We need to indicate which page in a wiki tree is displayed. 
At the same time, We can also explore the tree and select a page for move 
or delete for when creating a sibling or child. The selection refers to 
the pages that are chosen for action, but they may not be the displayed 
page. 
I think this could be a farily common use case for having both in the same 
widget.”
 
That is a good use case. It’s still going to be a confusing UX though. 
Perhaps there’s nothing we can do to minimise that?
 
Léonie.
 
-- 
Senior Accessibility Engineer, TPG
@LeonieWatson @PacielloGroup