OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-accessibility message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Fwd: Fw: ODF AccSC meeting minutes 7/13/06]


Greetings,

Here are Pete Brunet's meeting minutes from our July 13th meeting.  For 
our approval.


Peter
--- Begin Message ---
----- Forwarded by Pete Brunet/Austin/IBM on 07/20/2006 10:09 AM -----
Pete Brunet/Austin/IBM

07/13/2006 11:04 AM

To
Richard Schwerdtfeger/Austin/IBM
cc
Subject
ODF AccSC meeting minutes 7/13/06




Attendees: Peter, Pete, Rich, Chieko, Hiro, Dave Clark, Steve Nobel, Tatsuya-san

rich: Ma Yue posting regarding tables in presentations. Peter, Any problems?
pk:  don't know - will take it as action item
rich: caption ID reference - Bruce D had questions about it - not sure we are at consensus -
pete/hiro: there is no spec for forumulas - waiting for input from Rob Weir - inportant for interop between editors
pete/hiro: there is a problem with sub-tables - sub-tables are used by implementors for split and merge but it adds semantic structure that is not really there thus causing confusion for the AT user
rich: captions (mentioned above) - no problem  - captions go in draw:text-box (this is in 9.2.1.5) - so can have more than one text:p in a caption
rich: putting together an implementation appendix outline
rich: any limit on size
peter: not sure - bidi appendix is 1 page - might be extra doc - ODF spec is several hundred pages - let's go ahead and not worry about it for now - and then get feedback from TC about how to deal with packaging it
DC: please ref UAAG and ATAG
Rich: Good idea
Hiro: Need to cover generator, converter, acc. checker - this is not like web - we have edit mode and reading mode - is acc. checker a UA
DC: we need to mention that accessibility has application for people beyond disabilities, e.g. auto testing, extracting text from graphics for searches, etc.
PK: Reorged the material
Rich: Looks good - need to not mention 508 - this is an issue for Europe
PK: need to address other, non accessibility, audiences
Rich: might have small appendix and reference a large doc
PK: OK - but let's leave this up to the TC
DC: don't focus on interop with ATs, but interop of editors on varios platforms
PK: section 2 would contain general statements, then a description of specifics on a per platform basis (win, unix, mac)
PK: will go through the docment now
PK: section 1
Rich: How far do we want to go with discussion of what accessibility is
PK: not too far - a few sentences - refer to glossary
DC: What does the TC want - we should check with them
Chieko - If audience is technical then the doc language can be technical
Hiro:  Would be nice to have a chart like this:  http://www.w3.org/WAI/guid-tech.html
PK: section 2
Rich: either not mention 508 or mention them all - so European countries don't have an issue
DC: perfer not any mention - no need, it's a tech doc
Rich: ditto
PK: having the references might be helpful to reader
Rich: Is there a list we can reference
DC: this is not about compliance with other standards
PK: not implying this is about legal issues - but can point out that this info is consistent with other legal requirements such as 508 and others in the global community
PK: These issues are important: keyboard, theme, interop with AT
PK: Engineers will be coming to this doc because being driven by 508, etc
Rich: If we do this, some group - somewhere will be upset
PK: OK Let's table this for now and think some more about this between now and next meeting
PK: Would suggest starting with general description of problem and then provide more OS specific info with links to refs to support for KB, Themes, ATs
PK: Web based ODF - needs to point to docs on accessibility for AJAX apps like Writely
Rich: How to proceed from here?
PK: take a few more days on the outline, then submit the outline and start filling out the doc
Rich: Add a glossary
Rich: will be out next week
PK: will still have a call next week




Pete Brunet
                                                                         

IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, TL 678-4594, Fax: (512) 838-9666
Ionosphere: WS4G
--- End Message ---


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]