joanmarie
joanmarie
@zcorpan: Please and thank you when you have time.
@smhigley The ATK/AT-SPI2 value interface is intended for numeric ranges (progress bars, spin buttons, sliders, etc., etc.). For instance, in the case of a spin button that lets you select...
Consensus from TPAC: * First: Change implementations to treat cell inside grid as they do gridcell. * Then: Make gridcell synonym for cell initially * Finally: Deprecate gridcell
@cookiecrook - Mac mappings please @jcsteh and/or @asurkov and/or @feerrenrut - IA2 mappings please @boggydigital and/or @melanierichards - UIA mappings please @joanmarie (aka me) - ATK mappings please
@jcsteh and @cookiecrook : Could you please each open an issue against the ARIA spec for your concerns? If need be we can hold off on including these three roles...
Adding the F2FCandidate label because I think we want to discuss and achieve consensus regarding what we expect/want user agents to calculate.
Related: https://github.com/w3c/core-aam/issues/49
@aleventhal: Regarding this: > Maybe simple answer is to say same platform role? It will end up as menuitem on the platform. Some platforms have different roles for the various...
Perhaps (from Matt): Counting items that have one of the required owned element roles within the context.
We also have to deal with: associationlistitemkey and associationlistitemvalue. Should these even support aria-posinset and aria-setsize?