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: Re: [office] accessibility caption proposal comments


thank you


Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www-106.ibm.com/developerworks/blogs/dw_blog.jspa?blog=441
Inactive hide details for Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM>Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM>


          Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM>
          Sent by: Michael.Brauer@Sun.COM

          06/23/2006 12:49 AM


To

Richard Schwerdtfeger/Austin/IBM@IBMUS

cc

"Bruce D'Arcus" <bruce.darcus@OpenDocument.us>, OpenDocument <office@lists.oasis-open.org>, office-accessibility@lists.oasis-open.org

Subject

Re: [office] accessibility caption proposal comments

Rich,

Richard Schwerdtfeger wrote On 06/22/06 18:17,:
> Thanks Michael.
>
> content-id is fine.
>
> It looks like all text for a caption is wrapped in a text:sequence. I
> have only seen the use of draw:text-box in Open Office and Workplace
> implementations. Is this a spec. change and user agent implementation
> change or just a user agent implementation change?

It's a user agent implementation change. User agents would have to wrap the
caption in an additional <text:section> element if it constist of more than
one paragraph (what I assume won't happen very often). The draw:text-box,
that is exported by OOo and Workpace, still would exist, since it is required
to position the text-box. The advantage I have seen in using a section here
is that it seems to make clearer what belongs to the caption. The text box
that contains the caption also contains the object which references the
section, so referencing it may lead to some kind of ambuguity. However, this
could simply be resolved by specifying that the element that takes the
caption-id and its content should not be considered to be part of the
caption. If we do that, referencing a draw:text-box actually is a very
interesting option, that keeps changes for existing applications smaller.

The more I think about it, I consider your proposal to reference a
draw:text-box to be the better solution. I will put this on the agenda for
the Monday TC call.

Michael

>
> Cheers,
> Rich
>
>
> Rich Schwerdtfeger
> Distinguished Engineer, SWG Accessibility Architect/Strategist
> Chair, IBM Accessibility Architecture Review Board
> blog:
http://www-106.ibm.com/developerworks/blogs/dw_blog.jspa?blog=441
> Inactive hide details for Michael Brauer - Sun Germany - ham02 - Hamburg
> <Michael.Brauer@Sun.COM>Michael Brauer - Sun Germany - ham02 - Hamburg
> <Michael.Brauer@Sun.COM>
>
>
>                         *Michael Brauer - Sun Germany - ham02 - Hamburg
>                         <Michael.Brauer@Sun.COM>*
>                         Sent by: Michael.Brauer@Sun.COM
>
>                         06/22/2006 08:16 AM
>
>
>
> To
>
> Richard Schwerdtfeger/Austin/IBM@IBMUS
>
> cc
>
> "Bruce D'Arcus" <bruce.darcus@OpenDocument.us>,
> office-accessibility@lists.oasis-open.org, OpenDocument
> <office@lists.oasis-open.org>
>
> Subject
>
> Re: [office] accessibility caption proposal comments
>
>
>
>
> Rich,
>
> what Bruce describes actually is what the TC agreed on Monday and what it
> already included in the 1.1 draft I'm currently editing.
>
> Does it work for you?
>
> Michael
>
> Bruce D'Arcus wrote On 06/22/06 14:39,:
>  > Hi Rich,
>  >
>  > On Jun 22, 2006, at 8:34 AM, Richard Schwerdtfeger wrote:
>  >
>  >> I modified the caption proposal to replace the target id for
>  >> describedby to be <draw:text-box> vs. <text:p>. The reason is that we
>  >> discovered later that the caption can have multiple <text:p> per the
>  >> schema and therefore the encapsulating text box should be the target id.
>  >
>  >
>  > IIRC, Michael Brauer said you could wrap the paragraphs in a
>  > text:section element as well. Am not sure which is better, but in any
>  > case, the idea is that same.
>  >
>  >> Where is the TC at on the caption proposal. Has it agreed to use
>  >> describedBy or are they wanting to do something more heavyweight like
>  >> introducing a caption element?
>  >
>  >
>  > We actually approved the attribute on Monday, although there was
>  > consensus that caption-id is better because more specific. So 1.1 will
>  > add a "caption-id" attribute per the original proposal.
>  >
>  > I guess this is unofficial until the minutes are posted and approved?
>  >
>  > Bruce
>  >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe from this mail list, you must leave the OASIS TC that
>  > generates this mail.  You may a link to this group and all your TCs in
>  > OASIS
>  > at:
>  >
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
> --
> Michael Brauer                                Phone:  +49 40 23646 500
> Technical Architect Software Engineering      Fax:    +49 40 23646 550
> StarOffice Development
> Sun Microsystems GmbH
> Sachsenfeld 4
> D-20097 Hamburg, Germany                e-mail: michael.brauer@sun.com
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
>
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>

--
Michael Brauer                                Phone:  +49 40 23646 500
Technical Architect Software Engineering      Fax:    +49 40 23646 550
StarOffice Development
Sun Microsystems GmbH
Sachsenfeld 4
D-20097 Hamburg, Germany                e-mail: michael.brauer@sun.com

GIF image



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