Re: [office-accessibility] ODF TC accessibility summary from meeting earlier today

[Janina Sajka <janina@freestandards.org>]

As I think about it, our DAISY solution may have rested on line
numbering rather than soft line breaks.

Sorry I don't have the specs here to just go look it up--but I've been
out of the DAISY process for a few years now.

Janina

Janina Sajka writes:
> I believe the question was whether DAISY ever specifies soft line
> breaks.
> 
> I've been racking my memory and am uncertain. Might we have specified
> soft line breaks perhaps in the poetry module? Did that module ever make
> it to the DAISY specs? Seems it would relevant in content such as
> poetry, computer program code, etc.
> 
> So, I guess I'm convincing myself we should look at soft line, even if
> we don't do it right away.
> 
> Janina
> 
> Dave Pawson writes:
> > On 13/06/06, Peter Korn <Peter.Korn@sun.com> wrote:
> > 
> > >
> > >We have one question thus far, as raised by Bruce D'Arcus on how to
> > >implement caption support.  I believe Dave Pawson & Bruce have had
> > >several exchanges about this, with no final conclusion as of yet.  So,
> > >one action item is for you Bruce & Dave - to draft XML schema to address
> > >the caption requirement (Requirement #6).
> > 
> > Will do. OK with that Bruce?
> > 
> > 
> > 
> > > One question came up (from
> > >Florian Reuter) with this: is there any accessibility requirement for
> > >soft line-breaks?  Dave Pawson - does DAISY usage refer to lines that
> > >things are on, or just pages, paragraphs, sections, and such like?
> > >Implementing soft line-breaks is not something the TC is eager to do (it
> > >would significantly increase the file size!), but they don't want to
> > >miss anything we feel is important.  So Dave, can I have your thoughts
> > >on this, either via e-mail or in our meeting this coming Thursday?
> > 
> > A blind persons requirement is no different to yours or mine.
> > The classic example is two children in class. Turn to page 45,
> > third paragraph. Without soft page breaks being identified, how
> > can the blind child navigate to a 'visual' page?  Daisy has a single
> > element.
> > 
> > <!ELEMENT pagenum (#PCDATA) >
> > 
> > <!--Attuse: pagenum
> > 
> >    "page" allows three kinds of page numbering
> >    schemes to be identified:
> >    "front" (for roman-numeral pages at the start of a book),
> >    "normal" (for pages identified by arabic numerals),
> >    or "special" (for all other kinds of pages)
> >    For multi-page continuous content,
> >    such as large <img> or <table>, put the sequence of <pagenum> on
> >    the page where that content starts.
> >    -->
> > 
> > <!ATTLIST pagenum
> >  %attrsrqd;
> >  page (front | normal | special) 'normal'
> >  >
> > 
> > 
> > So I'd see <pagenum page='normal'>45</pagenum>
> > 
> > Since this is primarily a navigational tool, it is picked up and
> > provides a target
> > for navigation, so 'goto page 45' is viable.
> > 
> > HTH
> > 
> > 
> > -- 
> > Dave Pawson
> > XSLT XSL-FO FAQ.
> > http://www.dpawson.co.uk
> 
> -- 
> 
> Janina Sajka				Phone: +1.240.715.1272
> Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com
> 
> Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more.
> 
> Chair, Accessibility Workgroup		Free Standards Group (FSG)
> janina@freestandards.org		http://a11y.org

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com

Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org