Agree. Firefox exposes a current item within a widget as active state both in ATK and IA2. Reusing it for aria-current we will run into conflict.
I don't have data about IA2 activate state usage, I can check it out if needed. On Wed, Sep 2, 2015 at 12:06 AM, James Teh <[email protected]> wrote: > Hi all, > > One problem here is that the term "active" is somewhat ambiguous, > especially given aria-activedescendant. > > Joanie, for a container which uses aria-activedescendant, do you expect > that ATK_STATE_ACTIVE would be exposed on the element which is currently > the active descendant? That also fits the definition: "the active > subelement within a container or table". I believe this is how > IA2_STATE_ACTIVE is currently being used. > > If you do expect this would be the case, we have a problem because there > are apparently cases where aria-current and aria-activedescendant can apply > to different descendants: > https://lists.w3.org/Archives/Public/public-pfwg/2014Nov/0287.html > > On the other hand, I can totally see how this definition also fits > aria-current. That ambiguity is concerning. > > aria-current seems a lot like "selected" to me. However, I understand > there are cases where selected and current conflict; e.g. the tree example > in the spec. > > Alex, do we know if existing ATs are using IA2_STATE_ACTIVE? NVDA isn't at > this stage. > > Jamie > > > On 1/09/2015 6:29 AM, Joanmarie Diggs wrote: > >> Hi Alex. >> >> Up through ATK 2.14 [1], the definition of ATK_STATE_ACTIVE was: >> >> Indicates a window is currently the active window, or is an active >> subelement within a container or table >> >> That struck us as odd. Can a window be "an active subelement within a >> container or table"? We figured that the part after the comma referred >> to objects which were not windows. >> >> In order to clarify that, and also distinguish it from FOCUSED and >> SELECTED, we updated the docs in ATK 2.16 [2]: >> >> Indicates a window is currently the active window, or an object is >> the active subelement within a container or table. ATK_STATE_ACTIVE >> should not be used for objects which have ATK_STATE_FOCUSABLE or >> ATK_STATE_SELECTABLE: Those objects should use ATK_STATE_FOCUSED >> and ATK_STATE_SELECTED respectively. ATK_STATE_ACTIVE is a means to >> indicate that an object which is not focusable and not selectable >> is the currently-active item within its parent container. >> >> Being the active subelement within a container or table does sound like >> aria-current (doesn't it?). >> >> Lastly, note that we do NOT expect you to do any validation, and there >> may be cases where an author has a current object which happens to be >> focusable. That's OK. :) We were more concerned about desktop toolkits >> getting the states wrong. >> >> --joanie >> >> [1] https://developer.gnome.org/atk/2.14/atk-AtkState.html#AtkStateType >> [2] https://developer.gnome.org/atk/2.16/atk-AtkState.html#AtkStateType >> >> On 08/31/2015 03:54 PM, Alexander Surkov wrote: >> >>> Hi, Joseph. I agree on 'current' object attribute, not sure ACTIVE_STATE >>> is a proper mapping for both IA2 and ATK (ATK defines it as "Indicates a >>> window is currently the active window"). Why do you think it's worth to >>> set up the state? >>> Thanks. >>> Alex. >>> >>> On Mon, Aug 31, 2015 at 3:45 PM, Joseph Scheuhammer <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi Alex, >>> >>> I have finalized the ATK/AT-SPI mappings of aria-current [1], and >>> based on that, have a proposal for the MSAA+IA2 mappings. >>> >>> However, I've been following the related mozilla bug [2], and >>> likely, you will have thoughts. Has there been any progress with >>> respect to FF/IA2/aria-current? >>> >>> For what it's worth, it appears that AXAPI will be adding an >>> AXCurrent property whose value is that given by aria-current, that >>> is, one of page, step, location, date, time, true, or false [3]. >>> >>> Thanks. >>> >>> [1] >>> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaCurrent >>> [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1104947 >>> [3] https://bugs.webkit.org/attachment.cgi?id=260300&action=diff >>> >>> -- >>> ;;;;joseph. >>> >>> 'Array(16).join("wat" - 1) + " Batman!"' >>> - G. Bernhardt - >>> >>> >>> >>> >>> _______________________________________________ >>> Accessibility-ia2 mailing list >>> [email protected] >>> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >>> >>> _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >> > > -- > James Teh > Executive Director, NV Access Limited > Ph +61 7 3149 3306 > www.nvaccess.org > Facebook: http://www.facebook.com/NVAccess > Twitter: @NVAccess > SIP: [email protected] > > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
