Draft Minutes: August 18 ODF Accessibility Subcommittee Meeting

[Hironobu Takagi <TAKAGIH@jp.ibm.com>]

All, 

I will attach my draft minutes. Please
check it carefully. : )

Pete, 
Could you check IA2 part (topic 4)?

Regards
Hiro

--------------

Attendees: Hironobu Takagi (Hiro), Richard
Schwerdtfeger (Rich), Tatsuya Ishihara (Tatsuya), Mike Paciello (Mike),
Pete Brunet (Pete), Peter Korn (Peter)

1. Identify scribe
Hiro

2. Approval of July 20th minutes
http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200807/msg00062.html

Approved

3. Charts being backed by tables?
http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200808/msg00068.html

Rich: In order to make charts accessible,
the back-end table should be rendered in an accessible format. 
Pete: one possibility of chart without
table:table is a reference to other tables or a part of other tables.
  we need to check real implementation
in office editors. 
Rich: action item: need to ask adding
wording (description) for chart accessibility in the ODF spec (v 1.2).

Pete: in guideline?
Rich: both. "data table behind
charts must be informed (or rendered)" for assistive technologies"
http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200808/msg00003.html

Peter: user interface legislation is
always challenging. should we do that? 
Rich: I want to ask Rob Weir to make
sure it is reasonable or not. 
Peter: <<explains operation in
OO.o>>
  current user interface is challenging
for keyboard access users.
Rich: we can say "we need to have
a way to render data behind chart."
Peter: <<walk through operation
to create charts>>
Peter: multiple ranges can be combined
into (virtually) one table to create a chart. 
Peter: the operation is to "add
series" in the ranges dialog. 
Peter: I believe next action should
be ask to implementation team (for feasibility). 

ACTION ITEM Pete: to follow-up with
OpenOffice and Symphony on how to provide access to <chart:series>
chart:values-cell-range-address attribute
http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200808/msg00054.html

ACTION ITEM: Rich Discuss with Rob Weir
whether it is acceptable to require chart data found in tables elsewhere
in and ODF document (outside the embedded chart table) to be reconstituted
into a table rendering.

4. Radio-button Grouping Disposition

Quote from agenda
"Rich Comment: Seems like there
is available with Form:Frame. Unlike (X)HTML, ODF supports XForms and there
should be no limitation on the number of forms you can have and consequently
there should be no limitations on Form:Frame usage. It looks like we can
have form.frame and use the labeling capabilities form:for associate the
label text with the frame making this a BPG (best practice) discussion.

From Michael Brauer: the label would
be a <form:fixed-text> element. It has an (optional) attribute "form:for"
which contains the ID of a control for which the text is a label. The same
attribute is actually existing for the <form:frame> element which
defines a group box. Her, it can be used to specify that the group box
is the label for a set of radio buttons."

Rich: can we define "group"
and "label for"?
Pete: in IA2, "member-of"
is the way to define the relationship. 
Rich: if each child radio button can
refer parent group element, then parent's label can be determined as their
group label.  
Pete: labels are static?  is it
OK to assign static texts (in IA2)?
Rich: guidance to developers of user
agents is necessary. 

ACTION ITEM: PETE: Get input for "Best
Practices Guide" from implementors on how to best implement radio
groups as follow up to today's action item 4 (quoted above).

5. Action items needing attention 

Rich: Three action items for PK. 
- 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 
Peter: I will target the end of September.


Rich: we need to reassign action items
for Steve Noble to others.   

6. Meeting schedule

Because of schedule restriction of co-chairs,
we will setup calls in August and September as follows: 

August 25th 
- meeting for table/chart wrapup
- half hour call 
- Rich will set agenda and host the
call 

September 15th (Peter Korn will host.)
- Peter will set agenda and host the
call 


---------------------
Hironobu Takagi, PhD.
Accessibility Research
Tokyo Research Laboratory, IBM Research
+81-46-215-4557
E-mail: takagih@jp.ibm.com