Minutes: August 25 ODF Accessibility Subcommittee Meeting

[Pete Brunet <brunet@us.ibm.com>]

Attendees: Pete Brunet, Rich, Janina,
Tatsuya, Hiro, Chieko
Regrets: Malte, Peter Korn

1) Minutes: approved

2) Charts backed by tables 

Rich talked to Rob Weir.  Should
a11y issues be in the 1.2 Spec or separate guidelines.  Rob suggested
that perhaps the guidelines could be informative and part of the suite
of documents delivered as the 1.2 spec.  There would be links back
and forth between the primary spec and the guidelines.  The target
1.2 release date is 1Q09.  

The group was in agreement that this
would be a good idea but we need input from Peter and Malte.  

There was concern that some a11y solutions
will not be mature enough yet to be included in the spec, e.g. solutions
for Ajax or visualization based documents.  It was agreed that these
topics would not be released until ready and when ready released as an
errata.  Again, input is needed from Peter and Malte

3) New action items

• Malte and Peter: Provide input on the above topic of integration of the a11y guidelines into the suite of docs comprising the ODF 1.2 spec.
• Malte: Provide input on charts backed by disjoint cells:  

How
does (or how will) OpenOffice provide access to charts backed by disjoint
cell ranges either in a single or multiple tables?  If this case be
done today, what are the examples?
http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200808/msg00054.html
http://mediacast.sun.com/share/korn/chart-accessibility-challenge.ogg
http://mediacast.sun.com/share/korn/chart-in-writer.behavior.ogg

• Malte: Provide input on radio button groups

What are the best practices
for creating button groups?  There are two tags providing labeling:
1)form:frame and 2) form:fixed-text.  In the latter case, i.e. static
text is labeling a group of buttons (rather than the buttons being groups
in a form:frame, would you be able to implement an accessible hierarchy
(including the proper relations) for a button group?

4) Action item from prior meeting

• Pete: Ask Symphony team about best practices for radio button groups (see last action item above)
• Janina to 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.
• Janina to clarify text in section 3.4
• Peter to add a new section with guidelines as to how to provide tracking information to ATs.
• Peter to modify guidelines to ensure applications respond to system font and color settings.
• Peter will add explanation that this ODF 1.1 OLE embedding for presentation tables is no longer supported and that native ODF tables are used in 1.2
• Steve Noble to look at formulas specification identify data that would update frequently, such as volatile formula information that would require the Office application to inform the AT of updates sections. Will complete by next meeting.
• Rich to provide base document for ODF 1.2 change specification (starting with caption-id reference) to Mike Paciello. Mike is to own the requirements document for ODF 1.2 which will be submitted to the ODF TC. Rich is waiting on a decision as to where the ODF schema is to reside (separate or within the base document).

Pete Brunet
                    
                     
                     
         
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G