What you might want to do is to conditinalize the label style based on
@medium. There is a separate style sheet for @medium audio which
should be respected by screen readers.
You should also test that your implementation works for Safari with
Voice-over enabled, because I believe that is a more standards-based
implementation than JAWS, so potentially more broadly applicable.
On Jun 15, 2009, at 14:38, Henry Minsky <[email protected]>
wrote:
I'm trying to implement some of the accessibility API (just
setAADescription) for DHTML, and am wondering
what is the API is for enabling and disabling accessibility, either
globally or on individual views/sprites.
Views have a setAccessible method that calls sprite.setAccessible,
and in swf that is implemented as
/** Turns accessibility on/off if accessible == true and a screen
reader is active
* @param Boolean accessible
*/
LzSprite.prototype.setAccessible = function(accessible) {
var a = LzBrowserKernel.isAAActive() && accessible;
//Debug.write('setAccessible', LzBrowserKernel.isAAActive(), a,
this);
// turn off ugly _focusrect
_root._focusrect = 0;
_root.spriteroot.accessible = a;
}
What does this do? It seems like there's a global flag from
LzBrowserKernel, plus there's a canvas
'accessible' flag, right? Is this method only supposed to be called
on the canvas(sprite)? Or
is there supposed to be enable and disable for each view's
'accessible' behavior?
--
Henry Minsky
Software Architect
[email protected]
