OASIS ODF Accessibility SC Meeting
Attendees
- Dave Pawson
- Peter Korn
- Steve Noble
- Hironobu Takagi
- Chieko Asakawa
- Tatsuya Ishihara
- Janina Sajka
- Pete Bournet
- Rich Schwerdtfeger - Acting chair
- Malte Timmerman
Apologies
- David Clark
- Nathaniel Borenstein
- Mike Paciello
- Jerry Berrier
Scribe(s): Dave Pawson
Agenda
Item. Roll Call
Item. Approval of Minutes of Previous (3/30) Meeting
Item.
Old business:
- Presentation sub/sub team meeting Friday - Time resolution
Item.
-- alt texts, short/long/caption
Item.
- How is the Name attribute used? - Malte Timmerman. - Discuss
Peter's proposal:
Item.
- What are the appropriate name mapping rules by user agents?
Item.
- Do we use name for a user name field?
Item.
- Should we allow captions on primitives?
Item.
- Limit <svg:desc> to groupings?
Item.
- Disposition of described By for ATVs?
Item.
IV. New business:
-- Face to Face May 25/26 at RNIB (Edinburgh or Peterborough)
Item.
-- Soft/hard page break issue from Dave P
Item.
-- Nested list markup issue from Dave P
Item.
V. Deferred for post-June (keeping on agenda as placeholder):
-- Mediaobject proposal from Dave P
Item.
VI. Deferred until Nathaniel returns Table/SVG resolution in TC
Item.
VII. Agenda/Topics for Next Meeting
1 Roll Call. Approval of previous minutes.
DISCUSSION: RS: Minutes accepted.
2 Friday subteam meeting. - Time resolution
DISCUSSION: Time set to 1300Z, 90 minutes duration. Agenda posted to
list.
3 IRC
DISCUSSION: IRC was tried for the first time.
DISCUSSION: Details. url is http://irc.oasis-open.org/
Channel &office-accessibility (note the ampersand, not hash)
ports: 6667 (default) and 6669.
4 alt texts, short/long/caption
DISCUSSION: MT. name attribute is not used elsewhere. Without AT,
there is no automatic naming. Hence name attribute is available
for our use
- RS. Names were assigned when I created the
application?
- PK. The new code base has no names assigned unless
named by user. Seems different in 2.0 and 2.02 from
1.0. Drawing tool different is from presentation tool. Control
shift F5 in one, F5 in another.
- RS. I have many items named? Running 2.0. If I name it,
it overwrites the default value. (Ednote. Appears that Rich
experienced different results from others. Unresolved as to
why)
- PK. Not making sense. Not happening for MT, PK. Not
named in exported content.xml file. Conclusion, not needed, so
we can use it.
- RS. Can we use name for grouped objects too? Hence
there is no need for svg:title?
- JS. If builds diverge in what they provide, we need to
know.
- RS. This should happen if AT turned on or not. We want to
use name instead of adding svg:title.
- PK. Also do we only need longdesc on groups?
- MT. Why not on elements? I think it is wanted.
- RS. Group want svg:desc on all objects. Used as
longdesc. Name now can be now be used as short description, all
agree?
- Unanimous.
- RS. Re caption.
- PK. Proposal is. From Gnome, if name is blank and
caption has content, caption content given to AT. If object
has a name value, name value is given. We don't persist
information which is not there. Gnome on screen keyboard could
be built from objects in a slide.
- RS. Accepted. We can no send a proposal to TC. Notation
in specification, name will be used for accessibility, adding
description and described by for non-text objects.
- PK. Does this go to the errata? Name only contains a
value if explicitly set by user. We don't want UA to persist
data not set by author.
- PK. If there are meaningless names, AT will ignore
them. AT needs to be able to distinguish meaningful names from
others.
- PK. Want to know what object is and where it
is. Also meaningful is tab order and position.
- CA. We should define criteria when we need a name.
- RS. Should draw name be optional?
- PK. Alt text would be svg:text or description. No alt
text if nothing available. Currently nothing shows up if it is
not named. E.g. 4th obj, a rectangle, at coord X,Y. List
position from XML document model. All are derived. Provide to
user if wanted. User can get more information if needed (via
AT).
- JS. List position is useful for shared
information.
- PK. What does the blind user want
to know? I suggest they want to know what the thing is
(e.g. a "rectangle"), which of how many it is (e.g. "drawing
object 4 of 7, rectangle 1 of 3"), and where it is
(e.g. inside bounding box at [(3,4), (12,15)].
- DP. I like it.
- Proposal accepted
Action item: Refine proposal, post to list?
Who? PK
Due date: For next week.
Action item: Send proposal to TC post review.
Who? NB.
Due date: AFter group review (send comments to list).
5 Face to Face meeting May 25, 26, UK (Edinburgh or
Peterborough)
DISCUSSION:
- Discussion of available dates. Eventually settled on 20 and 21 May as best compromise.
- Also considered meeting alongside Oasis symposium, May 9-12.
- MT. What reason for meeting?
- RS. We get a lot from them, help to meet June date. E.g. CSUN meeting. I have May meetings. WAI in DC. Gets harder earlier.
- RS.
Action item: Check room availability, catering, for 20,21st.
Who? DP
Due date: ASAP
Action item: Provide availability for those dates, to list.
Who? All
Due date: Before next week
Summary of Actions
- PK
-
Action item: Refine proposal, post to list?
Due date: For next week.
- NB.
-
Action item: Send proposal to TC post review.
Due date: AFter group review (send comments to list).
- DP
-
Action item: Check room availability, catering, for 20,21st.
Due date: ASAP
- All
-
Action item: Provide availability for those dates, to list.
Due date: Before next week
|
Date: 2006-04-06T15:16:47.0Z
Time: 1600Z
Venue: Telcon
Date: 2006-04-06T15:16:52.0Z
Version: 1