This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
remove "If aria-expanded (state) is not "true", expose STATE_SYSTEM_COLLAPSED' from UIA Express column for combox. This is normal behavior for aria-expanded property and is covered in property table. Check with David if this is needed for IA2.
Done for MSAA+UIAExpress. David, does this text need to be removed from the MSAA+IA2 column?
It's not really covered by aria-expanded mapping: "aria-expanded is undefined (state) (default)" has "Not mapped" for all platforms including both UIA and IA2. Bug doesn't seems valid.
Cynthia, Can you please respond to Alex's comment in the bug? Do we need to change the aria-expanded undefined row now that we have removed this text?
(In reply to comment #2) > It's not really covered by aria-expanded mapping: > > "aria-expanded is undefined (state) (default)" has "Not mapped" for all > platforms including both UIA and IA2. Alex we discussed this briefly during a W3C call but weren't 100% sure what you meant here. > > Bug doesn't seems valid. Sounds like we can close this bug as INVALID/WORKSFORME right? (I'd agree)
(In reply to comment #4) > (In reply to comment #2) > > It's not really covered by aria-expanded mapping: > > > > "aria-expanded is undefined (state) (default)" has "Not mapped" for all > > platforms including both UIA and IA2. > > Alex we discussed this briefly during a W3C call but weren't 100% sure what > you meant here. I don't recall details. But I think the problem is. Cynthia asked to remove "If aria-expanded (state) is not "true", expose STATE_SYSTEM_COLLAPSED' from UIA Express column for combox" because "This is normal behavior for aria-expanded property and is covered in property table". However aria-expanded property table says "aria-expanded is undefined (state) (default)" has "Not mapped" for all platforms". That means if those words are removed then combobox having not "true" aria-expanded shouldn't expose STATE_SYSTEM_COLLAPSED. > > Bug doesn't seems valid. > > Sounds like we can close this bug as INVALID/WORKSFORME right? (I'd agree) You can't call it invalid or worksforme until you back out the fix in MSAA+UIAExpress case (see comment #1).
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #2) > > > It's not really covered by aria-expanded mapping: > > > > > > "aria-expanded is undefined (state) (default)" has "Not mapped" for all > > > platforms including both UIA and IA2. > > > > Alex we discussed this briefly during a W3C call but weren't 100% sure what > > you meant here. > > I don't recall details. But I think the problem is. > > Cynthia asked to remove "If aria-expanded (state) is not "true", expose > STATE_SYSTEM_COLLAPSED' from UIA Express column for combox" because "This is > normal behavior for aria-expanded property and is covered in property > table". However aria-expanded property table says "aria-expanded is > undefined (state) (default)" has "Not mapped" for all platforms". That means > if those words are removed then combobox having not "true" aria-expanded > shouldn't expose STATE_SYSTEM_COLLAPSED. This made my head hurt but I think I got it :) Cynthia are you sure you don't want to state that UIA Express should expose STATE_SYSTEM_COLLAPSED for the case where role=combobox and aria-expanded is undefined? > > > > Bug doesn't seems valid. > > > > Sounds like we can close this bug as INVALID/WORKSFORME right? (I'd agree) > > You can't call it invalid or worksforme until you back out the fix in > MSAA+UIAExpress case (see comment #1). It took me a while but I think here you are simply pointing out a technicality that if we close this as is then it would be as "FIXED" not INVALID/WORKSFORME right? Alex are you OK leaving this one up to Cynthia/MS or are you concerned about this text WRT a possible FF UI Express implementation?
If we leave out it as it is then it means that <div role="combobox"> is neither collapsed nor expanded in UIA Express and it is collapsed in IA2. In other words IA2 and UIA Express have different requirements about MSAA states. In case of Firefox both IA2 and UIA Express shares same MSAA tree so that will make us to break the spec this or that way. On the another hand if UIA bridge doesn't guess that neither collapsed nor expanded combobox is actually collapsed then screen readers should have a different logic for combobox processing depending on API. I don't think more diversity in this case is sensible. Anyway we could do a guessing more but it'd be great to hear Cynthia. It seems there is a bunch of options here: 1) It was done on purpose to comply with some UIA requirements 2) I missed some part of the spec and my guesses are wrong 3) It was a mistake
Here's another consideration. The spec for combobox asserts that aria-expanded is a *required* state [1] -- see the "Characteristics of combobox table". The implication is that comboboxes are inherently expandable/collapsible. That, in turn, means a combobox is either expanded or collapsed. I think it's a safe bet that when first instantiated, the combobox is collapsed. Rather, I can't think of a use case where a combobox is initially expanded without the user interacting with it. (It's possible that I'm just not creative enough...). This logic leads back to "if aria-expanded is not 'true', expose STATE_SYSTEM_COLLAPSED". [1] http://www.w3.org/WAI/PF/aria/roles#combobox
Shouldn't UAIG explicitly say that collapsed combobox means SYSTEM_STATE_COLLAPSED must be exposed in case of MSAA+UIA/MSAA+IA2 ?
(In reply to comment #9) > Shouldn't UAIG explicitly say that collapsed combobox means > SYSTEM_STATE_COLLAPSED must be exposed in case of MSAA+UIA/MSAA+IA2 ? It does for MSAA+IA2. It doesn't for MSAA+UIA because Cynthia requested it be removed (the reason for this bugzilla). IMHO, that edit should be undone; but, waiting for Cynthia's opinion.
Go ahead and put it back, pending david's approval of Issue 566.
(In reply to comment #11) > Go ahead and put it back, pending david's approval of Issue 566. Sure I'm fine with reintroducing text like: 'If aria-expanded (state) is not "true", expose STATE_SYSTEM_COLLAPSED' to be put in the UIA Express Column for role combobox. (Issue 566)
(In reply to comment #12) > (In reply to comment #11) > > Go ahead and put it back, pending david's approval of Issue 566. > > Sure I'm fine with reintroducing text like: 'If aria-expanded (state) is not > "true", expose STATE_SYSTEM_COLLAPSED' to be put in the UIA Express Column > for role combobox. (Issue 566) Cynthia, feel free to close this given David's comment.