From: Richard Tobin on
In article <D.Gray-ECF0CD.14130318012010(a)nntp-serv.cam.ac.uk>,
Dorian Gray <D.Gray(a)picture.invalid> wrote:

>No, I meant the opposite of "Good work Real". Real is offering a player
>to Mac OS X users. You would think they would make sure their download
>page doesn't hang the standard browser on OS X.

It shouldn't be *possible* to hang the browser.

-- Richard
--
Please remember to mention me / in tapes you leave behind.
From: James Jolley on
On 2010-01-18 15:30:34 +0000, Ben Shimmin <bas(a)llamaselector.com> said:

> James Jolley <jrjolley(a)me.com>:
>
> [...]
>
>> Nothing in principle, but accessibility is a serious issue and mno
>> amount of asking the BBC seems to solve anything. The "play" buttons
>> for the streams aren't being seen via VoiceOver, because it uses flash
>> I am guessing and Adobe aren't prepared to make flash accessible. It's
>> all complicated isn't it?
>
> Good news:
>
> * Adobe *are* aware of accessibility issues, there *is* support for
> screen reading technologies in Flash, and there's even a
> flash.accessibility package. [1]
>
> Bad news:
>
> * Most Flash developers have probably never been to the link below.
>
> b.
>
> [1]
> <URL:http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/accessibility/Accessibility.html>

Thanks
>
for this. I've bookmarked it and will send on to anyone who may need to
understand the situation.

Best

-JAmes-

From: Ben Shimmin on
James Jolley <jrjolley(a)me.com>:

[Flash and accessibility]

> Thanks for this. I've bookmarked it and will send on to anyone who may
> need to understand the situation.

You're welcome.

For what it's worth, Flash does by default (ie. without a developer having
to write any code) support things like tabbing between different elements
on the stage, pressing return to select them, and so on. I'm not sure why,
but many people don't realise this. (Of course, problems come when you
have more esoteric layouts where the interactive elements are not laid out
such that tabbing between them would make any sense.)

So you might think that you could just add a few descriptive labels and
you'd be well on your way to making your Flash stuff accessible. Sadly,
Adobe, in their infinite wisdom, have decided to tie their accessibility
support into Microsoft's Active Accessibility platform, which means if
you're using a Windows screen reader like JAWS, you're in luck, and if
you're using a Mac, you're screwed. At least, that's my understanding,
anyway.

b.

--
<bas(a)bas.me.uk> <URL:http://bas.me.uk/>
`It is like Swinburne sat down on his soul's darkest night and designed an
organized sport.'
-- David Foster Wallace, _Infinite Jest_, on American football
From: James Jolley on
On 2010-01-18 20:47:02 +0000, Ben Shimmin <bas(a)llamaselector.com> said:

> James Jolley <jrjolley(a)me.com>:
>
> [Flash and accessibility]
>
>> Thanks for this. I've bookmarked it and will send on to anyone who may
>> need to understand the situation.
>
> You're welcome.
>
> For what it's worth, Flash does by default (ie. without a developer having
> to write any code) support things like tabbing between different elements
> on the stage, pressing return to select them, and so on. I'm not sure why,
> but many people don't realise this. (Of course, problems come when you
> have more esoteric layouts where the interactive elements are not laid out
> such that tabbing between them would make any sense.)
>
> So you might think that you could just add a few descriptive labels and
> you'd be well on your way to making your Flash stuff accessible. Sadly,
> Adobe, in their infinite wisdom, have decided to tie their accessibility
> support into Microsoft's Active Accessibility platform, which means if
> you're using a Windows screen reader like JAWS, you're in luck, and if
> you're using a Mac, you're screwed. At least, that's my understanding,
> anyway.
>
> b.

Yes, that's the exact situation. It's a concern, and what I think I now
meant by adobe not doing enough. JAWS and Window-eyes do support flash
perfectly fine.

Best

-JAmes-

From: Dorian Gray on
In article <1jcir1x.194ymqlu6baibN%peter(a)cara.demon.co.uk>,
peter(a)cara.demon.co.uk (Peter Ceresole) wrote:

> I downloaded the pkg with both browsers, and it worked both times.
> However, as I said
> later, the display in Safari was the pig's ear that you report while in
> Firefox it was fine.

Wait, I don't understand what you're saying. All I'm saying is that
<http://www.real.com/mac/realplayer> (which I am directed to from
real.com in order to download the free Mac player) hangs Safari 4.0.4 on
OS X 10.4.11, well and truly, in the way I described.

Is your experience the same, or not?

P.S. I just noticed that even <http://www.real.com> hangs Safari in the
same way!
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Prev: Web page problem
Next: cured my sluggish 3G iPhone