Accessibility/Accessible Table Implementation: Difference between revisions

Accessibility/Accessible Table Implementation (view source)

77 bytes removed , 23 May 2007

17

edits

@@ Line 31: / Line 31: @@
 * getIndexAt(0,0) returns the child index under the table accessible of the top-left data cell. Again, row and column headers cannot be fetched using this method.
 * getRowHeader(n), getColumnHeader(n) return the accessible representing the header on the nth row and nth column. I have not found a XUL table with more than one header.
-* getRowDescription(n), getColumnDescription(n) return the accessible text or name on the one and only one header on the nth row and nth column. This is equivalent to getRowHeader(n).name or getRowHeader(n).queryInterface(<whatever the text idd is>).getText(0,-1). I can't tell which one gail is doing for us without looking at the gail code.
+* getRowDescription(n), getColumnDescription(n) return the accessible text or name on the one and only one header on the nth row and nth column. This is equivalent to getRowHeader(n).name or getRowHeader(n).queryInterface(<whatever the text idd is>).getText(0,-1).
 * Cells that visually span columns (e.g., a separator in the bookmarks tree table), exist as separate cells in the table. getRowExtentAt(r,c) and getColumnExtentAt(r,c) return 1 for all rows and columns falling into the spanning cell.
 * The table container fires no events. Moving the active selection box up and down within the table causes focus events on the cells in the first column. Focus cannot traverse other columns.