ODF Accessibility SC Agenda April 28, 2008

[Richard Schwerdtfeger <schwer@us.ibm.com>]

ODF Accessibility SC Agenda April 28, 2008

Please note your open action items. We will discuss these on the call.

Thursday 8am PT / 10am CST/ 11am ET / 3pm GMT

US: 1-877-421-0030
Toll: 770-615-1247

Toll Free Toll

UK: 0808-234-1969 +44 2070260533
IBM Tie-Line: 421-0030
IBM ITN: 2-421-0030
2-421-0035 from Europe

Vo/IP Using SIP or IAX: telecon@a11y.org

pc is 2119674 aka a11yorg

USA 877-421-0030; 770-615-1247
Austria +43 179576264
Belgium 0800-7-3026; +32 22006114
Denmark 80-888377; +45 38323070
Finland 0800-914-630; +358 972519061
France 0800-902366; +33 157323040; +33 157323041
Germany 0800-181-6323; +49 6951709081
Ireland 1800-558728; +353 16569209
Italy 800-788634; +39 0269430413
Netherlands 0800-022-8558; +31 202008077
Norway 800-18373; +47 24159528
Spain 900-95-1089; +34 912754171
Sweden 020-799414; +46 850163259
Switzerland 0800-564-331; +41 446545620
United Kingdom 0808-234-1969; +44 2070260533


IRC: http://irc.oasis-open.org
channel: "&office-accessibility"

Agenda: April 28 ODF Accessibility SC Meeting

It has been a while since we have had a meeting. This meeting is largely to synch up and start scheduling and get commitments to finishing up accessibility work on ODF 1.2 and its corresponding guidelines

1. Assign scribe and role call
2. Approve April 10 Minutes: http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200804/msg00009.html
3. Determine a time once a month that will work with Yamato
4. Discuss developing action plan for developing training and educational resources based on these guidelines
5. Work Items for ODF 1.2 specfications.

* Assign team members to review updated draft http://www.oasis-open.org/committees/download.php/27949/OpenDocument-v1.2-v7-01.odt
* Assign team member to create/manage change requirements for ODF 1.2 for TC submittal.

6. ODF 1.2 Action Items

* Peter
Check to see if this is a bug in OpenOffice: Address David's concern that headings were made available in an easy to discern way. ... H2s followed by H1s etc. He obtained that structure from an additional file.  Came back in an OOo update, and that information was no longer available.  Was Dave relying on optional attributes that are no longer there, or did OOo break the spec.? 

* Rich
- How does ODF do language tagging of a range of text?  Font attributes?  And how best to tag a string as "Grade 2 English Braille", vs. "music Braille in German". 
- Find deadlines for ODF 1.2; also to verify whether TC would like to see our 1.2 guidelines doc delivered at same time (in same "bundle") as 1.2 spec.
(Earliest is June)
- Rich/Dave Address accessibility of animations

I clarified this issue with Dave but we need to assess how critical this is and the UI implications for doing this in a presentation. ... or is this just a drawing.
- The issue that I recall was
providing alternate textual descriptions for the animation.

For that, the svg:g (group) element should be used to
wrap the animation(s), and the svg:desc element child
provide a description of the animation. Since the animated object can contain
many svg:animation children, it is necessary for the wrapper to
include all of them
if the animations act in a coordinated manner.
The description should provide a textual equivalent of the information
provided by the
animation (or indicate if the animation is decoration

* Hiro:
- Write proposed modification to 8.1.1 to add caption-id for table, and 9.2.15.2 to include tables - <ref name="common-draw-caption-id-attlist"/> 
- Provide more information related to table headers (from http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200711/msg00007.html) . It was not clear if this was for the ODF spec. or the guidelines. 
Hiro's response: http://lists.oasis-open.org/archives/office-accessibility/200804/msg00023.html 

7. Work Items ODF Accessibility Guidelines 1.2
* Janina 
- Add guidelines to address reload delay section 3.13.2 which would allow user agents to control the reload delay 
Janina's response:  http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200804/msg00034.html
- Modify accessibility guidelines to state how common field attributes (section 6.7 of the ODF 1.2 spec.) should be supplied to the AT. The field attributes would indicate whether something were a boolean, gregorian date, etc.

* Peter Korn
- Provide provide guidelines as to how to provide tracking information to ATs
- Modify guidelines to ensure applications respond to system font and color settings.

* Rich Schwerdtfeger
- Add wording to the next revison of the accessibilty guidelines to allow control of the animation rate of
images in a presentation

* Hiro
- Provide wording in the to adress dynamic, asynchronous updates There are several topics in the specs related to “asynchronous automatic update” of contents or values. Automatic updates should be carefully presented to assistive technologies through accessibility APIs. Documents are becoming more dynamic- async updates - some examples: linked tables, database ranges, scritping, text sections, DDE connecdtions.

-------------
 * [unassigned] Can OOo be a good codebase for Marc to start from for the Icon (which is ARM based)


(See attached file: ODF_Accessibility_Guidelines_v1.0-NEW.odt)(See attached file: ODF_Accessibility_Guidelines_v1.0-NEW.pdf)(See attached file: ODF_Accessibility_Guidelines_v1.0-NEW.zip)

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer


Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer

ODF_Accessibility_Guidelines_v1.0-NEW.odt

ODF_Accessibility_Guidelines_v1.0-NEW.pdf

ODF_Accessibility_Guidelines_v1.0-NEW.zip