E-mail List Archives
Re: Braille Display
From: glen walker
Date: Apr 17, 2018 10:33AM
- Next message: Mallory: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message: Birkir R. Gunnarsson: "Re: Fieldset/legend as label for textbox or textarea?"
- Next message in Thread: L Snider: "Re: Braille Display"
- Previous message in Thread: Kakarla Meharoon: "Braille Display"
- View all messages in this Thread
WCAG itself doesn't require you to test on any particular platform or
technology. How you want to verify you're compliant is up to you.
Depending on budget and personnel, various screen reader and browser
combinations can catch a lot of issues. Commonly, I've seen JAWS/IE,
NVDA/Firefox, VoiceOver on iOS. That leaves out Chrome (with either
Chromevox or JAWS/NVDA) and VoiceOver on the Mac. If you know your
audience will be using Macs, then testing VO on that platform would be a
good idea. I've only tested a few times with a refreshable Braille device
but they have caught things that a screen reader hasn't. We had a page
with temperatures and the degree symbol was not the correct ascii code for
Braille. I forgot what it was reading as but we fixed it. Visually, and
for the screen reader, it didn't make a difference, but for the Braille
device, it did.
Glen
On Tue, Apr 17, 2018 at 6:21 AM, Kakarla Meharoon < <EMAIL REMOVED>
> wrote:
> Hi
>
> As per WCAG, we need to test with Braille display also ??
> > > > >
- Next message: Mallory: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message: Birkir R. Gunnarsson: "Re: Fieldset/legend as label for textbox or textarea?"
- Next message in Thread: L Snider: "Re: Braille Display"
- Previous message in Thread: Kakarla Meharoon: "Braille Display"
- View all messages in this Thread