- From: Richard Schwerdtfeger <richschwer@gmail.com>
- Date: Fri, 24 Jun 2016 16:52:15 -0500
- To: Joanmarie Diggs <jdiggs@igalia.com>
- Cc: ARIA Working Group <public-aria@w3.org>
I agree. > On Jun 24, 2016, at 4:48 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote: > > Hey Rich. > > I'm going to add a "third" which is implied from what you've said here: > > On 06/24/2016 05:16 PM, Richard Schwerdtfeger wrote: >> So, expanded can be fired by the browser per platform for focusable >> widgets without the author having to apply it. Then it makes sense to >> not have the author provide the property. So, we would have to >> deprecate it. >> >> Second, check with Cynthia to make sure this will not violate a UIA >> control pattern regarding values. > > Third: For platforms which expect (depend upon) expanded being fired, we > need to find out what their definition of expanded is. A couple of > possibilities that spring to mind: > > 1. Going from 0% to a value that's greater than 0% > 2. Going from a value that's less than 100% to a value of 100% > > We'll need this for the Core AAM. > > With this information, I would hope that we could have authors provide > values, have user agents map the values to expanded/collapsed for those > platforms expecting that, and have ATs never notice that something has > changed. > > <strike>And make Joanie a little less twitchy.</strike> > > Thanks for considering this! And apologies, again, for having missed the > CfC on it. > > --joanie >
Received on Friday, 24 June 2016 21:52:46 UTC