Apologies,
I expect to be late to this con-call again - more urgent matters (same
as last week).
Regards,
Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.
OFBDE4D913.9B111DA6-ON862574AC.0065FAE3-862574AC.0067E985@us.ibm.com"
type="cite">
Dear colleagues,
This is the agenda for the OASIS ODF Accessibility subcommittee
meeting: Monday August 25, at 7am PT / 9am CT / 10am ET / 4pm CET /
11pm Japan time. Please use our usual (and unpublished) dial-in, and
our usual IRC channel: &office-accessibility at irc.oasis-open.org
Based on the last discussion with the ODF TC we need to be looking to
get things wrapped in September regarding requirements. We do face some
hurdles as we don't feel the ODF 1.2 spec. is really ready for review.
So, we are still focusing on ODF Accessibility Guidelines.
Call-in information:
The passcodes are not distributed on archived lists and must be
obtained from your respective chairpersons.
US: 1-877-421-0030
Toll: 770-615-1247
Toll Free Toll
Australia: 1-800-24-2283
Austria: 0800-292-738 +43 179576264
Belgium: 0800-7-3026 +32 22006114
Canada: 1-877-421-0030 770-615-1247
China North: 10800-711-0770
China South: 10800-110-0713
Czech Republic: 800-143-241 +420-272-133-001 or
+420-533-413-001
Denmark: 80-888377 +45 38323070
Finland: 0800-914-630 +358 972519061
France: 0800-902366 +33 157323040 or +33 157323041
Germany: 0800-181-6323 +49 6951709081
Greece 00-800-11-004-9793
Hungary 06-800-16-381
India 000-800-100-1156
Ireland: 1800-558728 +353 16569209
Israel 1-809-317-098 +972-3-9165956
Italy: 800-788634 +39 0269430413
Japan
KDD 00531-11-3180
Cable/Wireless 0066-33-801263
Softbank Telecom 0044-22-112668
NTT 0034-800-900155
Mexico: 1-877-421-0030 770-615-1247
Netherlands: 0800-022-8558 +31 202008077
Norway: 800-18373 +47 24159528
Poland: 0-0800111-1712 +48 22 366 5400 or +48 22 609 5400
or IBM PlusGSM 85400
Portugal 800-8-11111
Russia 8-10-800-2-172-10-44
Slovakia +421-2-4954-6539 or
+421-2-4964-9935
South Africa 0800-981-078
Spain: 900-95-1089 +34 912754171
Sweden: 020-799414 +46 850163259
Switzerland: 0800-564-331 +41 446545620
UK: 0808-234-1969 +44 2070260533
IBM Tie-Line: 421-0030
IBM ITN: 2-421-0030
2-421-0035 from Europe
Agenda:
Note: This is a short call. If there is any progress
on the action items in
1. Identify Scribe
2. Approval of Minutes August 18 Meeting? http://www.oasis-open.org/apps/org/workgroup/office-accessibility/email/archives/200808/msg00025.html
3. Charts being backed by tables.
http://www.oasis-open.org/apps/org/workgroup/office/email/archives/200808/msg00068.html
Action Item: Rich's call with Rob Weir
- Cover agreement on rendering data
- Suggestions on creating an informative BPG tied to
1.2 spec.
- Spec. release targeted for end Q109 currently
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 to follow-up with OpenOffice and Symphony on how to
provide access to <chart:series> chart:values-cell-range-address
attribute
Discuss two videos at (Hopefully some of us will have time to view):
http://mediacast.sun.com/share/korn/chart-accessibility-challenge.ogg
http://mediacast.sun.com/share/korn/chart-in-writer.behavior.ogg
3. Radio Grouping Disposition:
Pete Action item 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).
This seemed to be acceptable:
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 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.
4. Discuss Being an Informational document in the 1.2
suite which would be referenced by the ODF 1.2 series of specifications
5. Action items needing attention
- 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
- Pete to investigate if there are
any new charts not backed by tables (see above discussion)
- Pete to document how to navigate
to those tables in OpenOffice and Symphony. (see above discussion)
- 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).
Latest Office 1.2 specifications: http://www.oasis-open.org/apps/org/workgroup/office/documents.php
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
|