Thread Subject: Captioning not accessible to screen reader users

Return to this mailing list's archives

From: Debbie Cook
Date: Fri, Oct 27 2006 1:10 PM
Subject: Captioning not accessible to screen reader users

I know we can't resolve this easily, and it's an interesting discussion
related to whether AT needs to comply and to what extent, but for the
record, the captioning tool refreshes are not picked up by JAWS. Even doing
a page refresh in IE doesn't cut it. I litterally have to leave and return
to the page or activate a feature to get a refresh. Discovered this when I
couldn't connect to the Documentation call and decided to use the captioning
as an alternative. Tom confirms that in their tests it doesn't work with
JAWS, and that nobody cared much since the captioning is AT. So, we should
just be aware of it here in case others try to use it in this way.

From: Jim Tobias
Date: Fri, Oct 27 2006 2:30 PM
Subject: Re: Captioning not accessible to screen reader users

wow -- so this means a deaf-blind user using JAWS for braille would not be
able to participate?
has RCC been tested with other AT, like enlargers?

> -----Original Message-----
> From: Debbie Cook [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Friday, October 27, 2006 3:08 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-tools] Captioning not accessible to screen
> reader users
>
> I know we can't resolve this easily, and it's an interesting
> discussion related to whether AT needs to comply and to what
> extent, but for the record, the captioning tool refreshes are
> not picked up by JAWS. Even doing a page refresh in IE
> doesn't cut it. I litterally have to leave and return to the
> page or activate a feature to get a refresh. Discovered this
> when I couldn't connect to the Documentation call and decided
> to use the captioning as an alternative. Tom confirms that in
> their tests it doesn't work with JAWS, and that nobody cared
> much since the captioning is AT. So, we should just be aware
> of it here in case others try to use it in this way.
>
>

From: Bailey Bruce
Date: Mon, Oct 30 2006 5:10 AM
Subject: Re: Captioning not accessible to screen reader users

Debbie and Jim, any objections if I forward your messages to the folks
at Federal Relay?

The compatibility concern has been raised before but I have not heard an
update recently if they think the problem can be solved. I do not think
the characterization that quote nobody cared much unquote is accurate.
My understanding was that they were looking for a solution, but were not
going to compromise the core functionality in the meantime.

Is anyone in the tools group aware of a similar auto-scroll effect,
using HTML, that is accessible?

The discussion related to whether AT needs to comply and to what extent
should probably be directed to the Software Web subcommittee.

From: Jim Tobias
Date: Mon, Oct 30 2006 6:05 AM
Subject: Re: Captioning not accessible to screen reader users

No problem if you forward the messages.

Gregg -- have you encountered this issue before?

***********
Jim Tobias
Inclusive Technologies
= EMAIL ADDRESS REMOVED =
+1.732.441.0831 v/tty
skype jimtobias
www.inclusive.com


> -----Original Message-----
> From: Bailey Bruce [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Monday, October 30, 2006 7:09 AM
> To: TEITAC Communications Task Force
> Subject: Re: [teitac-tools] Captioning not accessible to
> screen reader users
>
> Debbie and Jim, any objections if I forward your messages to
> the folks at Federal Relay?
>
> The compatibility concern has been raised before but I have
> not heard an update recently if they think the problem can be
> solved. I do not think the characterization that quote
> nobody cared much unquote is accurate.
> My understanding was that they were looking for a solution,
> but were not going to compromise the core functionality in
> the meantime.
>
> Is anyone in the tools group aware of a similar auto-scroll
> effect, using HTML, that is accessible?
>
> The discussion related to whether AT needs to comply and to
> what extent should probably be directed to the Software Web
> subcommittee.
>
>

From: Jared Smith
Date: Mon, Oct 30 2006 7:50 AM
Subject: Re: Captioning not accessible to screen reader users

On 10/30/06, Bailey Bruce < = EMAIL ADDRESS REMOVED = > wrote:
> Is anyone in the tools group aware of a similar auto-scroll effect,
> using HTML, that is accessible?

For deaf-blind access, the timing issue becomes very difficult. You
can't really push the content to the screen and still have the screen
reader access it. You must give the user the control over the timing.
The captioning tool we've developed at WebAIM gives deaf-blind users a
static page with captions, then gives the user the option to view all
updated content or view the next X lines. I can't think of any other
way to provide real-time access. The problem is that the deaf-blind
user might get terribly behind.

I guess this does provide an argument for providing transcripts after
our meetings.

Jared

From: Gregg Vanderheiden
Date: Mon, Oct 30 2006 9:20 PM
Subject: Re: Captioning not accessible to screen reader users

Hi Jim,

Not sure what problem you are asking about. Tried to track the thread
backward but couldn't figure it out. Is this about the captioning tool we
used on GENERAL today? Or the FEDRCC tool?

Never had a screen reader user trying to use the captioning - so it hasn't
come up before. We should figure out how to do it though - and get that
info to the captioners.

Gregg


> Subject: Re: [teitac-tools] Captioning not accessible to
> screen reader users
>
> No problem if you forward the messages.
>
> Gregg -- have you encountered this issue before?
>
> ***********
> Jim Tobias
> Inclusive Technologies
> = EMAIL ADDRESS REMOVED =
> +1.732.441.0831 v/tty
> skype jimtobias
> www.inclusive.com
>
>

From: Jim Tobias
Date: Tue, Oct 31 2006 4:25 AM
Subject: Re: Captioning not accessible to screen reader users

What I meant was, it seems that no one had ever tested RCC with a screen
reader. I was curious as to whether anyone knew about that incompatibility.


***********
Jim Tobias
Inclusive Technologies
= EMAIL ADDRESS REMOVED =
+1.732.441.0831 v/tty
skype jimtobias
www.inclusive.com


> -----Original Message-----
> From: Gregg Vanderheiden [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Monday, October 30, 2006 11:09 PM
> To: 'TEITAC Communications Task Force'
> Subject: Re: [teitac-tools] Captioning not accessible to
> screen reader users
>
> Hi Jim,
>
> Not sure what problem you are asking about. Tried to track
> the thread
> backward but couldn't figure it out. Is this about the
> captioning tool we
> used on GENERAL today? Or the FEDRCC tool?
>
> Never had a screen reader user trying to use the captioning -
> so it hasn't
> come up before. We should figure out how to do it though -
> and get that
> info to the captioners.
>
> Gregg
>
>
> > Subject: Re: [teitac-tools] Captioning not accessible to
> screen reader
> > users
> >
> > No problem if you forward the messages.
> >
> > Gregg -- have you encountered this issue before?
> >
> > ***********
> > Jim Tobias
> > Inclusive Technologies
> > = EMAIL ADDRESS REMOVED =
> > +1.732.441.0831 v/tty
> > skype jimtobias
> > www.inclusive.com
> >
> >
>
>