Confirmed users
1,396
edits
Accessibility/Accessible Table Implementation: Difference between revisions
Jump to navigation
Jump to search
Accessibility/Accessible Table Implementation (view source)
Revision as of 15:06, 8 April 2008
, 8 April 2008→Implementation Problems
| Line 69: | Line 69: | ||
# SODC: The acc name is the full line of text (all the col data). The list has one next sibling that is a COLUMN_HEADER with no name and no action. The n of m info is coded in IA2::groupPosition. | # SODC: The acc name is the full line of text (all the col data). The list has one next sibling that is a COLUMN_HEADER with no name and no action. The n of m info is coded in IA2::groupPosition. | ||
= Implementation Problems = | =Implementation Problems = | ||
== HTML static tables in ATK == | == HTML static tables in ATK == | ||
| Line 96: | Line 96: | ||
ATK specification requires <code>getIndexInParent</code> method should be synchronized with <code>getRowAtIndex and getColumnAtIndex</code>. Here we get the problem. We should expose accessible for html:tr element since it's accessible since it has ARIA role and therefore the rule above is broken. | ATK specification requires <code>getIndexInParent</code> method should be synchronized with <code>getRowAtIndex and getColumnAtIndex</code>. Here we get the problem. We should expose accessible for html:tr element since it's accessible since it has ARIA role and therefore the rule above is broken. | ||
== List Tables in MSAA/IA2 == | |||
It was mentioned above tables in MSAA/IA2 are exposed as lists. Since table cells can contain anything then we can't expose just name and description on table accessible and we should expose accessible for table, table rows and table cells. Therefore we will broke synchronization of <code>IAccessibleTable</code> interface methods with <code>getIndexInParent</code> method like we have for the case of static HTML table in ATK. | |||