WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Alt text in Word 2016: Indicate null image & which box to type in

for

From: L Snider
Date: Jan 19, 2017 11:00AM


Hi Bevi,

Thanks so much for that information. I am wondering if the new version of
Word would make a difference here, do you know off hand?

Cheers

Lisa

On Thu, Jan 19, 2017 at 11:04 AM, Chagnon | PubCom < <EMAIL REMOVED> >
wrote:

> IIRC, some of these JAWS with Word behaviors are errors, not the final
> intended response, especially numbers 5 and 6 in Michael's list, using
> quick keys mode.
>
> Again, we must build content to meet the standards, not the weird
> behaviors of assistive technologies. The standards say "Alt-Text" not
> "Title."
>
> Otherwise we'll go crazy because JAWS reads something one way, NVDA
> another, Voice Over another...we'll never get anything published and fully
> accessible!
>
> AT manufacturers are required to meet the same standards. That's why they
> are standards!
>
> If Quick Keys in JAWS isn't giving the correct response, then its customer
> base -- JAWS users -- must cite them on this.
>
> --Bevi Chagnon
>
>
> On Thu, Jan 19, 2017 at 8:50 AM, Moore,Michael (Accessibility) (HHSC) <
> <EMAIL REMOVED> > wrote:
>
> > The behavior that I get with Word 2013 and JAWS 17, admittedly a
> > little out of date, is somewhat bizarre.
> >
> > My test document has three images. All images are placed in-line with
> > the text
> >
> > 1. Picture with title and description
> > 2. Picture with title only
> > 3. Picture with description only
> >
> > 1. In edit mode reading by line nothing is announced for any of images
> > JAWS just says blank.
> > 2. In edit mode reading by word the title is announced if it is present.
> > 3. In edit mode reading by character the title is announced if
> > present. If only the description is present the description is read
> > and the first word of the description is announced in the voice used for
> the title.
> > 4. In edit mode reading using say all. Both the title and description
> > are read and JAWS tells you which is the title and an which is the
> > description unless only a description is present. In this case JAWS
> > just reads the description. Also in this mode the title and
> > description are read twice for each image and the size of the image is
> announced.
> > 5. In quick keys mode reading by paragraph. JAWS will only announce
> > the title and ignores the description. Thus if only a description is
> > present JAWS will announce "blank" for the image.
> > 6. In quick keys mode reading by graphic. JAWS will only announce the
> > description and ignores the title. Thus if only a title is present
> > JAWS will only tell you that a picture is present.
> >
> > JAWS Keys used for reference:
> >
> > In edit mode - moving forward through the document Reading by line use
> > the down arrow Reading by word use control+left arrow Reading by
> > character use left arrow Reading say all go to the top of the page
> > control+home then insert+down arrow.
> >
> > To get to quick keys mode use insert+z Reading by paragraph use the p
> > key Reading by graphic use the g key
> >
> > I am not sure what all of this means in terms of what to recommend a
> > best practice for graphics is word documents. Just that life as a JAWS
> > user can be interesting. If the document is to be converted to PDF or
> > HTML for publication use the description field. This will save you
> > from having to enter the alt text again. If you all collaborating on
> > the document with a screen reader user (JAWS or other) I would ask
> > them how they would prefer the graphics to be labelled.
> >
> > Mike Moore
> > EIR (Electronic Information Resources) Accessibility Coordinator Texas
> > Health and Human Services Commission Civil Rights Office
> > (512) 438-3431 (Office)
>
> > > > >