Re: [Accessibility-ia2] rowspan and colspan
So we do have two use cases. #1 Example of spanned cells in a table having missed column div role=table aria-colcount=4 div role=row div role=cell aria-colindex=1 aria-colspan=2cell 1/div div role=cell aria-colindex=4cell 4/div /div div role=row div role=cell aria-colindex=1 aria-colspan=2cell 1/div div role=cell aria-colindex=2cell 2/div div role=cell aria-colindex=4cell 4/div /div /div #2 Example of spanned cells div role=table div role=row div role=cell aria-colspan=2cell 1/div /div div role=row div role=cellcell 1/div div role=cellcell 2/div /div /div Do I understand correct that the table interface should take into account of aria-colspan in case #2, and it should ignore it in case #3? On Sun, Jun 28, 2015 at 9:13 PM, James Teh ja...@nvaccess.org wrote: I think it should. However, this shows up an edge case. What if the author provides non-contiguous rows or columns, as aria-row/colindex allows? For example, suppose only columns 1 and 4 were in the DOM (using aria-colindex), but column 1 had a span of 2 (using aria-colspan). Column 4 in the DOM would be mapped to column 2 in the table interface (since the table interface is always contiguous). In this case, the table interface should not expose column extent for column 1, since that would suggest that column 2 in the table interface was spanned (which is column 4 in the DOM). So now we need a secondary way of exposing aria-colspan, perhaps an object attribute. This is really quite hideous. FWIW, I don't know of any API that can handle this; UIA can't either. Jamie On 27/06/2015 8:15 AM, Alexander Surkov wrote: Hey. ARIA introduced aria-rowspan and aria-colspan attributes [1] and [2]. Should be they exposed as part of IAccessibleTable interface, i.e. as col/row extents? [1] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-rowspan [2] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-colspan ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org 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: ja...@nvaccess.org ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
Re: [Accessibility-ia2] STATE_INDETERMINATE as a means to indicate things like unknowable set size?
On Tue, Sep 30, 2014 at 7:22 PM, James Teh ja...@nvaccess.org wrote: On 30/09/2014 2:32 AM, Joanmarie Diggs wrote: Given a large data set where the set size is not known (e.g. gmail's 1 of about 120), we need a way to be able to communicate the known set size along with the fact that the total is not (yet) known. One proposal has been to expose this via something like 120+. The problem with that is it means most of the time set size is a number, except for when it's a string one needs to parse. Seems like a less-than-ideal situation to me. Agreed. It's even worse in IA2 because it has a groupPosition property which uses ints, not strings, so it would be impossible to expose the + in that case. In ATK, we happily have STATE_INDETERMINATE which seems like it would fit the bill nicely,making it possible for quantifiable things like set size to remain numbers and giving implementors a means to indicate the size is indeterminate. In chatting with Alex Surkov about this, he seemed to think this was a reasonable approach. The only problem was that the ATK docs specifically said this state was for tri-state checkboxes in the mixed state. In IA2, this is exposed using MSAA's STATE_SYSTEM_MIXED (since IA2 is a superset of MSAA). While we *could* use this, there are two problems: 1. We can't update the documentation for MSAA, and even if we could, this wouldn't make sense because MSAA doesn't have groupPosition. I guess we could document an addition to STATE_SYSTEM_MIXED in the IA2 spec, but that's rather ugly. 2. This could be confusing for clients which support MSAA but not IA2. Therefore, we'd probably need to introduce a new IA2 state. STATE_INDETERMINATE? both for tri-state checkboxes and groups of unknown size? I just solved that with new docs. This change has just been committed. [1] So we're good. I'm not sure if this is an issue for ATK, but one problem I see is that in IA2, it's possible for any control to be checkable. This could include an item which has groupPosition. So, for example, what if there were a tri-state checkable tree item? How would you tell whether it were tri-state or in an indeterminate group? Jamie -- James Teh Executive Director, NV Access Limited Ph +61 7 3149 3306 www.nvaccess.org Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess SIP: ja...@nvaccess.org ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
Re: [Accessibility-ia2] aria-roledescription
It's not said by the spec but could the author use custom value for @role attribute and @aria-roledescription both, for example, div role=hyperbutton aria-roledescription=hyperspace button. In that case extendedRole would be used to contain @role value, localizedExtendedRole would expose value of aria-roledescription. On Sun, Jun 28, 2015 at 7:22 PM, James Teh ja...@nvaccess.org wrote: It's technically not quite a match for localizedExtendedRole, as that would suggest there was an extendedRole. However, I thinklocalizedExtendedRole is still a better match than object attributes. It may be helpful to update the spec to note that localizedExtendedRole can be valid even if extendedRole is NULL. Jamie On 27/06/2015 7:47 AM, Alexander Surkov wrote: ARIA 1.1 introduced aria-roledescription attribute which contains a localized version of ARIA role. Would it be a match for localizedExtendedRole or should we proceed with object attributes? Thanks. Alex. [1] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-roledescription ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org 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: ja...@nvaccess.org ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 ___ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
