Re: ARIA Test Cases 86 and 87 are invalid

I wrote:
> This discussion is within the context of a container that supports
> multiselection -- the second table in section 5.8.3 [1].  If only the
> focused item is selected, that sounds like a single selection scenario.  How
> does "selection follows focus" work in a context where multiple items can be
> selected?

Alex replied:
> Nothing prevents the mutliselectable container to manage the single
> selection, I think, that is the case.
>

I think you are saying that even containers that support multiple 
selection also support single selections.  Heres is a concrete case:  A 
list box that allow multiple selections.  However, the user is simply 
arrowing down the list, one option at a time.  Visually, a single option 
is highlighted, and the highlight moves down the list as the user 
presses the down arrow.

Is that the case you have in mind in your reply?

If so, the highlighted option is the one that has focus, and also the 
one that whose state has just changed to "selected" -- a case of 
selection following focus.  Is that what the second row of the second 
table in section 5.8.3 describes?  If so, that row mandates that the 
user agent fire

- MSAA: EVENT_OBJECT_SELECTION then EVENT_OBJECT_STATECHANGE on the 
newly focussed item.
- UIA:  FocusChangedEvent
- ATK/AT-SPI:  object::selection_changed
- AXSelectedChildrenChanged.

Aside:  except for UIA, this row is identical to the first table in 
5.8.3 that describes what happens for single selection containers.

[1] http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_selection

-- 
;;;;joseph.


'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
              - J. D. Klaun -

Received on Friday, 20 September 2013 14:57:10 UTC