WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: no paragraphs in divs

for

From: Jonathan Avila
Date: Jul 27, 2015 7:54AM


> I've noticed NVDA will treat text that is broken into multiple lines is treated as separate lines. Which kinda sucks when you have something like a button where the text wrapped to two lines; sometimes it sounds like two separate links/buttons when it's in fact one.

This can happen with JAWS to for links and headings when they become very long. But I suspect NVDA is more prone to this because it puts text and interactive controls on the same line until there is a block level element like a div or paragraph to break the content. I like how JAWS separate out interactive controls on separates lines with the arrow keys. While this may not be semantically accurate it is much easier to hear, select, and interact with the control.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of _mallory
Sent: Monday, July 27, 2015 2:16 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] no paragraphs in divs

On Sat, Jul 25, 2015 at 11:02:28PM +0100, Patrick H. Lauke wrote:
I've noticed NVDA will treat text that is broken into multiple lines is treated as separate lines. Which kinda sucks when you have something like a button where the text wrapped to two lines; sometimes it sounds like two separate links/buttons when it's in fact one.

_mallory

> On 25/07/2015 22:04, Guy Hickling wrote:
> >Assistive technology reacts to
> >paragraphs (eg screen readers may pause very slightly, and/or change
> >inflexion, at the end of a paragraph, but they don't do that for
> >divs. Your
> >3 sentances would have been run together.
>
> Just doing some very cursory testing, this isn't quite accurate.
>
> Doing a simple "read all" with NVDA and JAWS in Firefox and IE,
>
> <div>foo</div>
> <div>bar</div>
>
> is read out exactly the same (same pause, inflection) as
>
> <p>foo</p>
> <p>bar</p>
>
> For what it's worth, a notable inflection (to denote the end of a
> sentence) isn't caused by the presence or absence of a <p> element,
> but rather punctuation. Again
>
> <div>foo.</div>
> <div>bar.</div>
>
> and
>
> <p>foo.</p>
> <p>bar.</p>
>
> are announced the same, now both with a lowering/inflection to signify
> the end of a sentence.
>
> P
> --
> Patrick H. Lauke