MediaObject Proposal for LongDesc

[Richard Schwerdtfeger <schwer@us.ibm.com>]

Hi Dave, Chieko,

I read this and see value in it but it does not fully address an interoperability problem with Accessibility APIs.

In MSAA, Java, or ATK on Gnome there is the notion of an accessibleName an AccessibleDescription. Description would provide the equivalent of longdesc. It provides additional verbose text to the user when asked. However, normally, while navigating a document a short name would be provided and that is the accessibleName. This can be announced quickly to facilitate rapid audio navigation.

So in the case of an OK button:

The accessibleName is would be "OK" and is the equvalent of a label
The accessibleDescription might be "Activating this button will result in the indexing of your mail"

In Java, the accessibleDescription's default value for Swing controls would be the tooltip text.

So, I would think you would want title to be included for this as well:


<define name="med-frame">
 <element name="med:audio-frame">
   <ref name="common-draw-shape-with-text-and-styles-attlist"/>
   <ref name="common-draw-position-attlist"/>
   <ref name="common-draw-rel-size-attlist"/>
   <ref name="presentation-shape-attlist"/>
   <ref name="draw-frame-attlist"/>
   <element name="med:src">
     <ref name="common-draw-data-attlist"/>
     <ref name="Mime-types"/>
     <!-- Enable parameterisation of objects -->
     <ref name="draw-param"/>
   </element>
   <optional>
     <ref name="office-event-listeners"/>
   </optional>
   <zeroOrMore>
     <ref name="draw-glue-point"/>
   </zeroOrMore>
   <optional>
     <ref name="draw-image-map"/>
   </optional>
   <optional>
     <ref name="svg-desc"/>
   </optional>
    <optional>
     <ref name="svg-title"/>
   </optional>
   <optional>
     <choice>
<ref name="draw-contour-polygon"/>
<ref name="draw-contour-path"/>
     </choice>
   </optional>
 </element>
</define>


Comments?


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

"Two roads diverged in a wood, and I -
I took the one less traveled by, and that has made all the difference.", Frost


"Dave Pawson" <dave.pawson@gmail.com>

"Dave Pawson" <dave.pawson@gmail.com>

03/03/2006 03:01 AM

To	office-accessibility@lists.oasis-open.org
cc
Subject	[office-accessibility] Proposal. mediaObject element.

Attached, initial proposal for a syntax for mediaObject.
Also inline


Issues:

I do not know the mime-types well enough to be explicit for audio, video etc
so I have used a general reference to the rfc.
I'm not sure if my naming conventions match those in use in office,
but I have no issue with the syntax changes there.

Comments will be appreciated.


<?xml version="1.0" encoding="iso-8859-1"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0"
xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0"
xmlns:math="http://www.w3.org/1998/Math/MathML"

xmlns:html="http://www.w3.org/1999/xhtml"
xmlns:med="urn:oasis:names:tc:opendocument:xmlns:media:1.0"
>
 <!-- Root for any media object-->
 <start>
   <ref name="Mediaobject"/>
 </start>

<define name="med-mediaobject">
 <element name="med:mediaObject">
   <oneOrMore>
     <ref name="med-imageobject"/>
     <ref name="med-textobject"/>
     <ref name="med-audioobject"/>
     <ref name="med-videoobject"/>
   </oneOrMore>
 </element>
</define>


<!-- Basic image.  -->
<define name="med-imageobject">
 <element name="med:imageObject">
   <ref name="draw-frame"/>
 </element>
</define>

<!-- Basic text alternative form.
Reduced version of text-content.
Is text-box needed ? -->
<define name="med-textobject">
 <element name="med:textObject">
   <ref name="text-content-reduced"/>
 </element>
</define>


<!-- General text descriptor. Reduced general text-content -->

<define name="text-content-reduced">
 <choice>
   <ref name="text-h"/>
   <ref name="text-p"/>
   <ref name="text-list"/>
   <ref name="text-numbered-paragraph"/>
   <ref name="text-section"/>
   <ref name="change-marks"/>
 </choice>
</define>

<!-- Basic audio alternative -->
<define name="med-audioobject">
 <ref name="med-frame"/>
</define>


<!-- Basic video alternative -->
<define name="med-videoobject">
 <ref name="med-frame"/>
</define>




<!-- Modified draw-frame -->
<!-- Used for audio and video -->

<define name="med-frame">
 <element name="med:audio-frame">
   <ref name="common-draw-shape-with-text-and-styles-attlist"/>
   <ref name="common-draw-position-attlist"/>
   <ref name="common-draw-rel-size-attlist"/>
   <ref name="presentation-shape-attlist"/>
   <ref name="draw-frame-attlist"/>
   <element name="med:src">
     <ref name="common-draw-data-attlist"/>
     <ref name="Mime-types"/>
     <!-- Enable parameterisation of objects -->
     <ref name="draw-param"/>
   </element>
   <optional>
     <ref name="office-event-listeners"/>
   </optional>
   <zeroOrMore>
     <ref name="draw-glue-point"/>
   </zeroOrMore>
   <optional>
     <ref name="draw-image-map"/>
   </optional>
   <optional>
     <ref name="svg-desc"/>
   </optional>
   <optional>
     <choice>
<ref name="draw-contour-polygon"/>
<ref name="draw-contour-path"/>
     </choice>
   </optional>
 </element>
</define>



<div>
<html:h3>Mime types</html:h3>
<html:p>All media-type attribute values must conform to RFC 2046. In
addition, the media-type attribute must have the value of the
IANA-registered MIME media type for that type of file, if one exists
(see RFC 2048 for information on the registration process for MIME
media types). If no MIME media type has been registered for the file
type, then the MIME media type recommended in the applicable standard
for that file type must be used. If there is no standard MIME media
type for the file, then an appropriate "x-" MIME media type must be
used, following the rules of RFC 2046. In the case of WAV files, this
standard mandates the use of the media type value
"audio/x-wav".</html:p>

<define name="Mime-types">
 <attribute name="mime-type">
   <data type="String"/>
 </attribute>
</define>
</div>



</grammar>

regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
(See attached file: mediaObject.rng)

mediaObject.rng