Re: [Accessibility-ia2] Fw: ARIA 1.1 feature status aria-rowspan and aria-colspan

2015-08-05 Thread Alexander Surkov
On Wed, Jul 29, 2015 at 7:57 AM, Richard Schwerdtfeger sch...@us.ibm.com wrote: Yes, that is possible. He also said that would be hideous. :-) he probably needs time to get ok with it :) One concern is the growth of object attributes and the mechanism to get them. Perhaps we need a new

Re: [Accessibility-ia2] Fw: ARIA 1.1 feature status aria-rowspan and aria-colspan

2015-08-05 Thread James Teh
On 5/08/2015 10:59 PM, Alexander Surkov wrote: One concern is the growth of object attributes and the mechanism to get them. Perhaps we need a new interface to object attributes like a hashing table. IA2 has attribute method

Re: [Accessibility-ia2] Fw: ARIA 1.1 feature status aria-rowspan and aria-colspan

2015-07-29 Thread Richard Schwerdtfeger
Yes, that is possible. He also said that would be hideous. :-) One concern is the growth of object attributes and the mechanism to get them. Perhaps we need a new interface to object attributes like a hashing table. Rich Sent from my iPad On Jul 28, 2015, at 2:32 PM, Alexander Surkov

[Accessibility-ia2] Fw: ARIA 1.1 feature status aria-rowspan and aria-colspan

2015-07-28 Thread Richard Schwerdtfeger
I am continuing the discussion on the list. It sounds like we have two models - contiguous rows/columns vs. author specified. Should we say that if the author is going to provide row and column spans that user agents NOT compute the indices? IOW, It must all be left up to the author. It sounds

Re: [Accessibility-ia2] Fw: ARIA 1.1 feature status aria-rowspan and aria-colspan

2015-07-28 Thread Alexander Surkov
I'd say the problem is in restrictions of IAccessibleTable as it describes the continuous model only, while ARIA allows to have gaps in tables. So if a table has a gap and spanning right before the gap then we should use a mechanism other than IAccessibleTable. Jamie suggested to use object