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
