RE: Conflicting inclusion/exclusion criteria for elements in the accessibility tree (Was: Re: [ARIA] Agenda: March 3, 2016 WAI-ARIA Working Group)

" How does that work for a keyboard only user?  On the assumption that the user can see it, wants to put focus on it, and the only way they can is via TAB navigation ...?"

That would be an authoring error, a bad practice, and a critical accessibility issue for the website designer to fix... :) 

I think allowing all elements with tabindex="-1" to be in the tab order would be a huge mistake, because that would break simulated widgets everywhere.

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Tuesday, March 15, 2016 10:59 AM
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Cc: White, Jason J <jjwhite@ets.org>; Fred Esch <fesch@us.ibm.com>; ARIA Working Group <public-aria@w3.org>; Richard Schwerdtfeger <richschwer@gmail.com>
Subject: Re: Conflicting inclusion/exclusion criteria for elements in the accessibility tree (Was: Re: [ARIA] Agenda: March 3, 2016 WAI-ARIA Working Group)

On 2016-03-15 1:52 PM, Amelia Bellamy-Royds wrote:
> If something has negative tabindex *and* aria-hidden="true", it should 
> definitely not be in the tab order!

How does that work for a keyboard only user?  On the assumption that the user can see it, wants to put focus on it, and the only way they can is via TAB navigation ...?

--
;;;;joseph.

'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
                  - C. Carter -

Received on Tuesday, 15 March 2016 18:10:43 UTC