WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDF Multiline H1 JFW announces tag for each line

for

From: Moore,Michael (Accessibility) (HHSC)
Date: Dec 11, 2015 7:19AM

I don't really even consider this to be a problem. The screen reader that I am most familiar with (JAWS) only announces "heading" multiple times when you are reading line by line. If you move by paragraph the heading is announced and the whole thing is read. I believe that the same is true for reading by sentence but I don't navigate that way very often.

If when reading by line the screen reader did not announce that the next line was also a heading of the same level the user is left to guess whether they are in the body or the heading. I think that most experienced users are very familiar with this behavior and expect it.

I frequently observe that we sighties are very quick to suggest ways in which the screen reader ATs should be changed to meet our expectations. This things are not built for us. I would hope that the folks at Freedom, GW Micro, Dolphin, and NVDA pay more attention to their real customers than to us when it comes to changing the behavior of the software and adding new features. We should confine our bug reports to instances when the screen reader fails to support standards, and let the folks who depend on the technology suggest changes in how that support is implemented.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Faulkner
Sent: Friday, December 11, 2015 7:48 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] PDF Multiline H1 JFW announces tag for each line

Hi Cliff, this comment by James Teh (NVDA developer) on similar behaviour related to links may be helpful in explaining why it occurs

https://www.paciellogroup.com/blog/2011/06/html5-accessibility-chops-block-links/#comment-790



--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 11 December 2015 at 13:44, Cliff Tyllick < <EMAIL REMOVED> > wrote:

> Should we file bugs?
>
> Cliff Tyllick
>
> Sent from my iPhone
> Although its spellcheck often saves me, all goofs in sent messages are
> its fault.
>
> > On Dec 11, 2015, at 12:56 AM, Steve Faulkner
> > < <EMAIL REMOVED> >
> wrote:
> >
> >> On 10 December 2015 at 23:26, James Bailey < <EMAIL REMOVED> > wrote:
> >>
> >> It seems to me JAWS should announce the heading level once and then
> >> read title Any thoughts?
> >
> >
> > This is observed behaviour across a range of screen readers and
> > formats (does same in HTML with h1-h6). There is nothing that you
> > can do about
> it.
> >
> > --
> >
> > Regards
> >
> > SteveF
> > Current Standards Work @W3C
> > <
> http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3
> c/>
> > > > > > archives at http://webaim.org/discussion/archives
> > > > > archives at http://webaim.org/discussion/archives
> >