WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Trouble with a menu in Druple

for

From: Birkir R. Gunnarsson
Date: May 13, 2016 5:03PM

Sounds like:
a. The triggering element for the menu is not keyboard accessible
(needs both onclick and onkeydown for keycode 13 to expand and
collapse submenu).
b. Does not use aria-expanded to show the visible state of the submenu and
c. it sounds like the submenu is only hidden off-screen, probably
until the triggering element receives focus.

These are guesses based on your description and limited experiences I
have had with it a year or two ago.
If you could provide a link to a working page where this menu is used,
more questions could be answered.



On 5/13/16, L Snider < <EMAIL REMOVED> > wrote:
> Hi Gary,
>
> I was really glad you asked that question, because I should be more
> specific-as we both know accessible can mean so many things! I totally
> agree with what you said below, and it is important to be reminded. Today I
> was talking about videos and sign language...many people forget about sign
> language when talking about videos, but also documents...As well, many
> people with dyslexia or ADD use screen readers, so it is really important
> to get the details right!
>
> I want to research more about speech recognition, because the tools have
> become so much better (I used Dragon when it came out, and it wasn't
> pretty...) that I think way more people are using it daily. I don't see
> much out there on it, so thanks for sharing on the list. This list is
> awesome!
>
> Cheers
>
> Lisa
>
>
>
> On Fri, May 13, 2016 at 5:10 PM, Morin, Gary (NIH/OD) [E] <
> <EMAIL REMOVED> > wrote:
>
>> Hi, Lisa – my question about Superfish was really meant to be rhetorical –
>> to raise the issue that the word "accessible" is used without clear
>> definition or clarification, as if everyone agrees with what it means –
>> typically, in terms of ScreenReaders and vision loss, assuming no one else
>> with any other impairment or disability needs to be considered.
>>
>>
>>
>> As a speech recognition user, keyboard navigation doesn't really help –
>> not unless each keystroke or key combination is mapped to an oral command.
>> My point, hopefully ‘of course', is that not everyone who's disabled is
>> blind/sight impaired, and not everyone who uses AT is using vision-related
>> AT.
>>
>>
>>
>> W/best regards,
>>
>>
>>
>> Gary
>>
>>
>>
>> *From:* L Snider [mailto: <EMAIL REMOVED> ]
>> *Sent:* Friday, May 13, 2016 5:41 PM
>> *To:* Morin, Gary (NIH/OD) [E] < <EMAIL REMOVED> >
>> *Cc:* WebAIM Discussion List < <EMAIL REMOVED> >
>>
>> *Subject:* Re: [WebAIM] Trouble with a menu in Druple
>>
>>
>>
>> Hi Gary,
>>
>> Great questions, thanks. The people I know who have worked on it for their
>> own websites concentrated on screen reader users (I can't tell you which
>> ones they tested as that part I don't know). I can say that I have read
>> that the menus seem to work well with keyboard navigation right out of the
>> box.
>>
>> I was looking at it about 2 years ago and decided to go with PVII instead:
>> http://projectseven.com/products/index.htm
>>
>> No endorsement on either of them, but PVII have been accessibility
>> friendly for years (they were pretty good for limited dexterity, screen
>> readers, no js, keyboard only). Only problem was that PVII doesn't do a
>> module, so Superfish is easier to install because of it....
>>
>> I would love to know if anyone has tested Superfish with speech
>> recognition software, as that I have not seen anywhere.
>>
>> Sorry I wasn't clear, I should be more specific-thanks for the reminder!
>>
>> Cheers
>>
>> Lisa
>>
>>
> > > > >


--
Work hard. Have fun. Make history.