Alex, The aria example is an interesting scenario. I think in the vast
majority of cases the non header cells in a row that contains header
cells would be empty.
Just to be sure, are you saying you can't build tables with spanning
cells in ARIA?
Rob, For rowHeader, it's an out which indicates the column in the main
table where the header starts. Most of the time it's 0 but sometimes
there will be headers that start at an offset. The information may or
may not be useful. Let's say focus was at row 1 and colHeader returned
a startingRowIndex of 2, I can think of scenarios both where the user
does and doesn't want to know about that header below the point of
focus, but most of the time I think the user would not want to hear
about it.
Pete
--
*Pete Brunet*
a11ysoft - Accessibility Architecture and Development
(512) 238-6967
pete @ a11ysoft.com
http://www.a11ysoft.com/about/
http://www.linkedin.com/in/petebrunet
Ionosphere: WS4G
Rob Gallo wrote:
> Alex,
>
> I think this is good.
>
> But what is the purpose of the second parameter? I'm not sure this is
> supposed to be an [out] parameter.
>
> HRESULT rowHeader(
> [out] IAccessibleTable **accessibleTable,
> [out, retval] long * startingColumnIndex) [get]
>
>
>
>
> Thanks,
> RG
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Alexander Surkov
> Sent: Wednesday, May 27, 2009 7:59 PM
> To: [email protected]
> Cc: Willie Walker; IA2 List
> Subject: Re: [Accessibility-ia2] rowHeader/columnHeader
> implementationproposal
>
> Hi, Pete.
>
> It's really good question. I can see two cases.
>
> 1. If we operate with HTML table where rowspans and colspans are used then I
> believe you're right. In this case row and column indexes are in sync with
> main table.
> 2. If we deal with pure ARIA grid where there is no way to specify row/col
> spans then we could return header table of the same width/height like for
> primary table. For example,
>
> <div role="grid">
> <div role="row">
> <span role="gridcell">cell</span><span role="columnheader">cell</span>
> </div>
> <div role="row">
> <span role="gridcell">cell</span><span role="gridcell">cell</span>
> </div>
> </div>
>
> I think we should return table column header containing one row with two
> cells (gridcell and columnheader).
>
> Does it makes sense?
>
> Alex.
>
>
> On Fri, May 22, 2009 at 10:53 PM, Pete Brunet <[email protected]> wrote:
>
>> Alex, A question that came up offline: When the column headers are
>> not the full width of the table what is the relation between the row
>> offset in the primary table and the header table?
>>
>> What I am remembering now is that you will get back a table, and most
>> of the time the table will have one cell. A table is provided because
>> there might be n rows in the header portion in which case the table
>> would be one cell wide and with n rows. Or there might be a cell in
>> the header which spans n columns. In that case I think you should get
>> back a table with a single cell with columnExtentAt indicating it
>> spans n columns. You could also have the case of a header table with
>> two rows, with the first row containing a spanning cell and the second
>> row containing n normal cells under the spanning cell.
>>
>> Also, one feedback I got was that an AT would not expect to manipulate
>> the cell in the table header expecting it to reflect that change in
>> the primary table.
>>
>> I am ccing Will Walker in case he has comments regarding AT-SPI as we
>> will want to remain in harmony with it and also Xing Li since his team
>> implemented table headers in Symphony.
>>
>> Pete
>> --
>> Pete Brunet
>>
>> a11ysoft - Accessibility Architecture and Development
>> (512) 238-6967
>> pete @ a11ysoft.com
>> http://www.a11ysoft.com/about/
>> http://www.linkedin.com/in/petebrunet
>> Ionosphere: WS4G
>>
>> Alexander Surkov wrote:
>>
>> Hi.
>>
>> I summarized all our discussions with Pete about IAccessibleTalbe
>> rowHeader/columnHeader implementation -
>> https://wiki.mozilla.org/Accessibility/TableHeaders. Feedback on this
>> proposal is needed.
>>
>> Thank you.
>> Alex.
>>
>>
>>
>>
>> _______________________________________________
>> Accessibility-ia2 mailing list
>> [email protected]
>> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>>
>>
>>
> _______________________________________________
> Accessibility-ia2 mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>
>
>
>
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
