Alex, those colspan and rowspan mappings were direct from the HTML mappings … an exact copy for that matter. Presumably you have implemented rowspan and colspan for years. I don’t see why they need to be only object attributes. Rich Rich Schwerdtfeger > On Aug 8, 2016, at 2:10 PM, Alexander Surkov <asurkov@mozilla.com> wrote: > > Hi. > > Iirc there's a problem to make the accessible table interface to > reflect aria- values as they can be used to create not-yet-loaded > grids, see Jamie's concern [1]. I think that's why we expose them as > object attributes and group position in IA2. > > Joanie, what is your thinking on this issue, since ATK and IA2 > shouldn't be different on this? > > Note, the spec says to map aria-rowspan and aria-colspan into IA2 > table interface, they should be mapped into object attributes instead. > > Thanks. > Alex. > > [1] https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2015-June/001913.html > > On Fri, Aug 5, 2016 at 6:53 PM, Rich Schwerdtfeger <richschwer@gmail.com> wrote: >> Alex, >> >> Please take a look. Joanie reviewed ATK/ATSPI >> >> https://rawgit.com/w3c/aria/action2102/core-aam/core-aam.html >> >> >> Joseph, >> >> Alex is updating the IA2 spec. I am waiting on aria-errormessage and >> aria-details mappings. Also, Cynthia is going on vacation. I fixed her >> aria-rowspan and aria-colspan mappings but I will have to wait until she >> returns to get the rest for action 2102. I also still need to get the Mac >> mappings. We might want to pull in the changes after Alex weighs in on the >> this branch. there are A LOT. … or we can wait. >> >> Cheers, >> Rich >> >> >> >> Rich Schwerdtfeger >> >> >> >>
Received on Monday, 8 August 2016 19:30:50 UTC