WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Making this type of navigation accessible

for

From: L Snider
Date: Apr 14, 2015 6:11AM

Hi _mallory,

Thanks so much, that was very helpful. Appreciate it!

Cheers

Lisa

On Mon, Apr 13, 2015 at 12:12 PM, _mallory < <EMAIL REMOVED> > wrote:

> I understand that that top is not actually part of the page, but part
> of the hosting... whenever the page gets moved to its proper home
> that bit ought to go away on its own.
>
> As for advice, I believe there is now a working aria-ised tree example
> over at... I think it was open ajax alliance. They use little plusses
> and minusses but you can keep the arrows just fine.
>
> http://www.oaa-accessibility.org/example/41/
>
> One problem they have here, besides a possible issue with VoiceOver,
> is that mouse users seem to need to double-click? Which made me think
> at first that the mouse didnd't work at all at first. And on the other
> hand, most of our clients double-click on many things (but not anchors
> or X close buttons) and only user-testing would show if they tried
> single or double-clicking here.
>
> Bryan has something on the whatsock site, and it's single-clicked:
> http://whatsock.com/modules/aria_tree_from_xml_module/demo.htm
>
> If Javascript is not the strong suit, you could do it backwards:
> start with something like jQuery's Bonsai, then add in any missing
> keyboard focus and uses, aria-states, etc. I've done similar with
> plugins that were more complicated than anything I could write from
> scratch.
>
> _mallory
> On Mon, Apr 13, 2015 at 07:33:01AM -0500, L Snider wrote:
> > Hi Ryan and _mallory,
> >
> > Argh! Thanks for trying. I found the same with my testing this weekend. I
> > will have to figure out how to show you this example, without that top
> > piece getting in the way.
> >
> > Cheers
> >
> > Lisa
> > > > >