Peter,
One of the things we avoided in 1.0 of the guidelines is adding API mappings to the scale of work involved. If we do this for tables we would have to do it for the rest of the document. That is a huge undertaking and we would need to do multiple API mappings.
So, we took the approach instead to approach this generically.
We are looking to do an implementers guide for user agents and ARIA but that is a huge job and we are looking to have participation from the major browser manufacturers. We are not staffed for this.
You agree?
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
blog: http://www.ibm.com/developerworks/blogs/page/schwer
Peter Korn ---01/14/2009 11:22:01 PM---Pete,
Sent by: Peter.Korn@Sun.COM 01/14/2009 11:21 PM |
|
Pete,
Ummm.... OK. Looking at the writeup I saw from you, it really wasn't clear to me how that would translate into prose in what section. That's why I was asking. It seems to me it would be a level of detail/documentation on accessibility APIs around tables that isn't in keeping with the level we have for other things (e.g. text attributes).
Perhaps it would be easiest if I first saw your actual proposed write up, in context, for IA2...
Regards,
Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.
Peter, I currently have the document and was going to take a stab at that along with a few other things. If you have some text or just thoughts let me know. Rather than getting into the details of documenting the mapping from ODF to MSAA/IA2 and ATK I was going to put something more generic in section 2.3.1 "Characteristics of Engineered Accessibility Frameworks".
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 286-5485, Cell: (512) 689-4155
Ionosphere: WS4G
| From: | Peter Korn <Peter.Korn@Sun.COM> |
| To: | Richard Schwerdtfeger/Austin/IBM@IBMUS |
| Cc: | Pete Brunet/Austin/IBM@IBMUS, office-accessibility@lists.oasis-open.org |
| Date: | 01/14/2009 05:35 PM |
| Subject: | Re: [office-accessibility] ODF 1.2 accessibility guidelines |
| Sent by: | Peter.Korn@Sun.COM |
Richard,
For this AI, where do you expect the text to go in the guidelines document?
Regards,
Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.
I updated the guidelines to cover PDF conversion and remove the special casing of Tables in Presentations. Meanwhile I will look at live regions. ... I am trying to get this all wrapped up. I had some problems getting the table of contents working properly but that is largely editorial. I want this wrapped up soon so we can put together a final document that can be reviewed. I need to get the ODF work off my plate to work on other efforts as I know both of you do. Again, Peter thank you for applying the other changes.
Can both of you get together coordinate a change for this action item:
- Peter Korn and Pete Brunet to specify the text of how table row and column information are mapped in ATK and IA2
Pete's response: http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200811/msg00020.html
(See attached file: ODF_Accessibility_Guidelines_v1.1_v1-4Jan11.odt)
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
blog: http://www.ibm.com/developerworks/blogs/page/schwer
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
