E-mail List Archives

Re: JAWS Screen Reader (and Word)

for

From: Emma Duke-Williams
Date: Oct 16, 2006 2:20AM


Using proper headings etc., (rather than just making the text bigger)
is also invaluable dyslexic students (or anyone for that matter) who
wants to see an outline of the sections.
(And it makes generating a table of contents much easier).

Emma

On 10/12/06, Joshue O Connor < <EMAIL REMOVED> > wrote:
> Hi Rebecca,
>
> >> >> Just bear in mind that only the very latest versions of screen
> readers will
> >> >> be able to pick up structure in a Word document.
>
> Yes thats right. Its only since version 7 (JAWS) that it will recognise
> a Word documents structure. Thanks for the reminder, as it points out an
> important lesson in all of
> this, that many can be left behind using older versions of UA's, so no
> assumptions should be made.
>
> Having said that, it is a step in the right direction.
>
> Josh
>
> Rebecca Ballard (Without a Mouse) wrote:
> > > Just bear in mind that only the very latest versions of screen
> readers will
> > > be able to pick up structure in a Word document.
> > >
> > >
> > > Rebecca
> > >
> > > Sign up for regular tips and tricks at www.withoutamouse.com/newsletter.
> > > Check out my new blog at www.withoutamouse.com/blog
> > > Thinking about Broadband? Check out www.withoutamouse.com/broadband.
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: <EMAIL REMOVED>
> > > [mailto: <EMAIL REMOVED> ] On Behalf Of Joshue O
> Connor
> > > Sent: 12 October 2006 11:33
> > > To: WebAIM Discussion List
> > > Subject: Re: [WebAIM] JAWS Screen Reader (and Word)
> > >
> > >
> >> >> I believe the best way to assist
> >> >> visually-impaired readers of Word documents would be to use the same
> >> >> principles of applying structured markup (identifying headings,
> lists,
> >> >> tables, etc.) as is recommended for HTML.
> > >
> > > Eoin is right. Also if structural documents are created in Word they can
> > > then be exported (problems with MS HTML not withstanding) as fairly
> > > accessible HTML docs.
> > >
> > > Josh
> > >
> > > Eoin Campbell wrote:
> >> >> I'm not a JAWS expert, but I believe the best way to assist
> >> >> visually-impaired readers of Word documents would be to use the same
> >> >> principles of applying structured markup (identifying headings,
> lists,
> >> >> tables, etc.) as is recommended for HTML.
> >> >>
> >> >> Word has plenty of built-in styles such as Heading 1, Heading 2, List
> >> >> Bullet, which can be used to apply structure to a document.
> >> >> JAWS can use these structure styles to assist readers in navigating
> >> >> around the document.
> >> >> Using named styles consistently will also allow users apply their own
> >> >> preferred Word template (with larger fonts, for example), so that
> they
> >> >> can view it in a way that suits them.
> >> >>
> >> >>
> >> >> "DONALD WONNELL" < <EMAIL REMOVED> > wrote:
> >> >>
> >>> >>> Is there any way to emphasize certain points on a Word document
> >>> >>> written in textonly for the visually challenged audience? Don't
> want
> >>> >>> to have unusually burdensome text for people to have to access.
> >>> >>>
> >>> >>> Heard underlining or bold text makes it harder for JAWS to read in
> >>> >>> some versions, in others has no effect so there would be no
> advantage
> >>> >>> to using it. At one time all caps was said to be easier for screen
> >>> >>> readers to pick up. Please give me any info you may have on this.
> >> >>
> > >
> > >
> > > ********************************************************************
> > >
> > > NOTICE: The information contained in this email and any attachments is
> > > confidential and may be privileged. If you are not the intended
> recipient
> > > you should not use, disclose, distribute or copy any of the content
> of it or
> > > of any attachment; you are requested to notify the sender immediately of
> > > your receipt of the email and then to delete it and any attachments from
> > > your system.
> > >
> > > NCBI endeavours to ensure that emails and any attachments generated
> by its
> > > staff are free from viruses or other contaminants. However, it cannot
> > > accept any responsibility for any such which are transmitted. We
> therefore
> > > recommend you scan all attachments.
> > >
> > > Please note that the statements and views expressed in this email
> and any
> > > attachments are those of the author and do not necessarily represent the
> > > views of NCBI
> > >
> > >
> > > ********************************************************************
> > >
> > >
> > >
> > > Address list
> > > messages to <EMAIL REMOVED>
> > >
> > >
> > >
>
>
>
>
> ********************************************************************
>
> NOTICE: The information contained in this email and any attachments
> is confidential and may be privileged. If you are not the intended
> recipient you should not use, disclose, distribute or copy any of
> the content of it or of any attachment; you are requested to notify
> the sender immediately of your receipt of the email and then to
> delete it and any attachments from your system.
>
> NCBI endeavours to ensure that emails and any attachments generated
> by its staff are free from viruses or other contaminants. However,
> it cannot accept any responsibility for any such which are
> transmitted. We therefore recommend you scan all attachments.
>
> Please note that the statements and views expressed in this email
> and any attachments are those of the author and do not necessarily
> represent the views of NCBI
>
>
> ********************************************************************
>
>
>
>
>
>


--
Blog: http://www.tech.port.ac.uk/staffweb/duke-wie/blog/