WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Live Chat - ARIA recommendations and/or good examples?

for

From: Jonathan Avila
Date: Nov 14, 2014 4:42PM

> Can a mobility impaired person using Dragon "scroll"?

If the scrolling area is keyboard focusable they can give commands to move down or move up or issue keyboard commands by voice.

Earlier today I posted a blog on considerations for testing with Dragon and speech recognition software.

https://www.ssbbartgroup.com/blog/2014/11/14/considerations-for-testing-with-speech-recognition-software-such-as-dragon-naturally-speaking/

Best Regards,

Jonathan

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Joy Relton
Sent: Friday, November 14, 2014 5:25 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] Live Chat - ARIA recommendations and/or good examples?

Can a mobility impaired person using Dragon "scroll"? I know that they can command the software to "tab". Ihaven't tested with Dragon for a while but I didn't think that it scrolled.

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Ryan E. Benson
Sent: Friday, November 14, 2014 2:31 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Live Chat - ARIA recommendations and/or good examples?

Jonathan said:
In addition, to Bryan's comment, it may be useful to provide keystrokes or navigation structures to allow users of screen readers to move between
messages so that they may review what's been said. A review of how
screen readers work with programs like Skype, Lync, and AIM may be useful.

While I agree, however I would say this might be slightly overkill for people with mobility disabilities, so allowing them to tab into the container and scroll using only the arrow keys would help.

--
Ryan E. Benson

On Thu, Nov 13, 2014 at 8:51 PM, Jonathan Avila < <EMAIL REMOVED> >
wrote:

> > how this person would know that the service representative is
> responding, and then when the rep responds. So, it seems like there is
> a need to inform the customer when these events happen in a way that
> is clear, not confusing.
>
> In addition, to Bryan's comment, it may be useful to provide
> keystrokes or navigation structures to allow users of screen readers
> to
move between
> messages so that they may review what's been said. A review of how
> screen readers work with programs like Skype, Lync, and AIM may be useful.
>
> Sounds (earcons) may also be useful to provide other auditory feedback.
>
> Jonathan
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of
> <EMAIL REMOVED>
> Sent: Thursday, November 13, 2014 3:45 PM
> To: <EMAIL REMOVED>
> Subject: [WebAIM] Live Chat - ARIA recommendations and/or good examples?
>
> I'm being asked to review, for accessibility considerations, the
> design requirements for a pretty standard live chat interface on
> desktop. Tablet and smartphone are not in scope at this time.
>
> I'm clear about specifying the need for focus when the chat initially
> opens, the form fields, etc.
>
> My concerns are around how a blind customer using a screen reader
> would interact with the input field for their message, how this person
> would know that the service representative is responding, and then
> when the rep responds. So, it seems like there is a need to inform the
> customer when these events happen in a way that is clear, not confusing.
>
> (This could also be reversed, saying that the service representative
> would be the screen reader user, however the interface I'm reviewing
> is
> customer-facing.)
>
> Is this a good use of aria live regions?
>
> Also, I'd appreciate any examples of where this has been delivered
> successfully with accessibility in mind.
>
>
> Thanks,
>
>
> Judith Blankman
>
> Accessibility Strategist
> Customer Experience
>
>
>
> Wells Fargo Digital Channels Group | 550 California Street, 2nd
> floor
> | San Francisco, CA 94104
>
> MAC A0122-020
>
> Tel 415-947-6583 | Cell 415-601-1114 | Fax 415-974-7452
>
>
> <EMAIL REMOVED>
>
>
>
> > > list messages to <EMAIL REMOVED>
> > > list messages to <EMAIL REMOVED>
>