WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Help with Echo accessibility


From: Carin Headrick
Date: Oct 25, 2010 8:00PM

He said he was using Firefox. Firefox doesn't work with VO. So I thought
maybe I could help him get it to work with Firefox and JAWS to compare
the difference. That was all.


On 25/10/2010 9:15 PM, Ron Stewart wrote:
> You use JAWS and sorry to say what that does have to do with an accessible
> interface?
> As I have stated so many time before this is one of the major problems when
> content creators try to use JAWS as their measure of accessibility. What you
> get is a measure of JAWS accessibility which has very little to do with
> actual measurements of the accessibility and the functional usability of a
> given interface from an UAI level.
> Each screen reader will deal with the user interface differently and if it
> does not work as you expected then that is a design error not an
> accessibility problem.
> -----Original Message-----
> [mailto: <EMAIL REMOVED> ] On Behalf Of Carin Headrick
> Sent: Monday, October 25, 2010 8:31 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Help with Echo accessibility
> But I use JAWS and can press enter on them and they work for me. So what
> makes the way VO handles them different than JAWS?
> On 25/10/2010 4:45 PM, Patrick Burke wrote:
>> Not much to go on, but the critical code in question is apparently
>> drawn in from somewhere else& does not show up with View Source. The
>> whole thing is a wild festival of Javascript.
>> The only clue I can give is that "Post"& "Cancel" are announced (by
>> Jaws in Windows) as buttons. "Follow"& "Echo" (with its sublist of
>> options nearby) are only reported as "clickable", but not as buttons
>> or links. So it would appear that the Echo system has defined mouse
>> events for these items& left out keyboard access. Device-independent
>> event handlers are usually best.
>> Patrick
>> At 01:28 PM 10/25/2010, Carin Headrick wrote:
>>> You said you also had trouble hitting reply from within a thread, right?
>>> I'm one of the blog authors, and I have felt helpless to help her, so
>>> for now, we've been sending her comments to her manually by email. But
>>> human errors do tend to happen.
>>> Really hopin' for some info so we can also pass it on to Echo since we
>>> kinda pay for their service.
>>> Carin
>>> On 25/10/2010 11:42 AM, Ro wrote:
>>>> Hi folks,
>>>> If there are any Apple users with Leopard or Snow, can I get your help
>>>> with something? One of my favorite blogs uses Echo's commenting
>>>> system. To follow comments, you can just click "follow", enter your
>>>> email, and then you can reply to comments by email. It's really nice,
>>>> but since one of the latest Safari updates, the word "follow" does
>>>> nothing. I've tried using group mode in Leopard to no avail.
>>>> The Echo CEO actually suggested I get a PC user to enter my email
>>>> address for me. Wow. He says it works from on his Mac OS 10, which is
>>>> great but he's not using Voiceover. Can someone go check it out, just
>>>> arrow down until you find the comment field, keep going until you hear
>>>> "follow", click it and see if you get an option to enter an email? I
>>>> want to know if this is something weird with my computer alone before
>>>> I respond to the Echo guy some more.
>>>> If you're so inclined also, if you think you might know what the
>>>> problem is and if there's a fix, that would be great too because then
>>>> I could tell them.
>>>> I was hoping I'd never have to bring this here, but I don't know what
>>>> else to do.
>>>> Here's a post to test the comments:
>>>> http://vomitcomet.blogspot.com/2010/10/i-got-world-series-i-wanted.html
>>>> Thanks in advance...
>>>> ~Randi and Guide Dog Jayden
>>>> http://raynaadi.blogspot.com/
>> --
>> Patrick J. Burke
>> Coordinator
>> UCLA Disabilities&
>> Computing Program
>> Phone: 310 206-6004
>> E-mail: burke<at> ucla. edu
>> Department Contact: <EMAIL REMOVED>