E-mail List Archives
Thread: Trouble with a menu in Druple
Number of posts in this thread: 16 (In chronological order)
From: Ritz, Courtney L. (GSFC-7200)
Date: Fri, May 13 2016 9:06AM
Subject: Trouble with a menu in Druple
No previous message | Next message →
Hello all,
Many apologies if this has already been discussed, I haven't had a chance to dig through the archives yet.
My organization's developers have migrated a lot of our sites to Druple. They're using an expandable-collapsible menu which they refer to as a "hamburger?" menu.
Anyhow, lately, my experience has been that I cannot see the menu at all using JAWS in IE. I can't expand or collapse it or anything. There's a "toggle navigation" button but I can't activate it with the keyboard.
In Firefox, I get all the menu links as if all the menus were expanded. While that makes for a huge list of links, it's better than having nothing at all.
Has anyone encountered this in Druple, and is there a fix or another menu that might work? I'm clueless when it comes to Druple, but I can pass any suggestions on to our developer folks.
Courtney
From: Mike Barlow
Date: Fri, May 13 2016 9:25AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Does the menu work at all in IE even without JAWS? If not then I'd address
that problem first before trying to get it working for JAWS.
*Mike Barlow*
Web Application Developer
Web Accessibility/Section 508 SME
Lancaster, Pa 17601
Office: 732.835-7557
Cell: 732.682.8226
e-mail: = EMAIL ADDRESS REMOVED =
On Fri, May 13, 2016 at 11:06 AM, Ritz, Courtney L. (GSFC-7200) <
= EMAIL ADDRESS REMOVED = > wrote:
> Hello all,
>
> Many apologies if this has already been discussed, I haven't had a chance
> to dig through the archives yet.
>
> My organization's developers have migrated a lot of our sites to Druple.
> They're using an expandable-collapsible menu which they refer to as a
> "hamburger?" menu.
> Anyhow, lately, my experience has been that I cannot see the menu at all
> using JAWS in IE. I can't expand or collapse it or anything. There's a
> "toggle navigation" button but I can't activate it with the keyboard.
> In Firefox, I get all the menu links as if all the menus were expanded.
> While that makes for a huge list of links, it's better than having nothing
> at all.
>
> Has anyone encountered this in Druple, and is there a fix or another menu
> that might work? I'm clueless when it comes to Druple, but I can pass any
> suggestions on to our developer folks.
>
> Courtney
> > > > >
From: Ritz, Courtney L. (GSFC-7200)
Date: Fri, May 13 2016 9:41AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Hi again,
I found out that the menu they're using in Drupal is actually called Superfish. When you have any responsive themes on websites and the menu compresses to three bars instead of an actual menu its called a hamburger (because it kind of looks like a hamburger)
Can Superfish be made accessible?
From: Ritz, Courtney L. (GSFC-7200)
Sent: Friday, May 13, 2016 11:07 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Trouble with a menu in Druple
Hello all,
Many apologies if this has already been discussed, I haven't had a chance to dig through the archives yet.
My organization's developers have migrated a lot of our sites to Druple. They're using an expandable-collapsible menu which they refer to as a "hamburger?" menu.
Anyhow, lately, my experience has been that I cannot see the menu at all using JAWS in IE. I can't expand or collapse it or anything. There's a "toggle navigation" button but I can't activate it with the keyboard.
In Firefox, I get all the menu links as if all the menus were expanded. While that makes for a huge list of links, it's better than having nothing at all.
Has anyone encountered this in Druple, and is there a fix or another menu that might work? I'm clueless when it comes to Druple, but I can pass any suggestions on to our developer folks.
Courtney
From: L Snider
Date: Fri, May 13 2016 10:00AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Hi Courtney,
Yes, Superfish menus can be made more accessible. It takes a bit of doing,
but I know people who have done it (no clue what version of IE they were
testing though, not sure how EDGE would work with it).
Cheers
Lisa
On Fri, May 13, 2016 at 10:41 AM, Ritz, Courtney L. (GSFC-7200) <
= EMAIL ADDRESS REMOVED = > wrote:
> Hi again,
>
> I found out that the menu they're using in Drupal is actually called
> Superfish. When you have any responsive themes on websites and the menu
> compresses to three bars instead of an actual menu its called a hamburger
> (because it kind of looks like a hamburger)
>
> Can Superfish be made accessible?
>
> Courtney
> >
>
From: Moore,Michael (Accessibility) (HHSC)
Date: Fri, May 13 2016 10:44AM
Subject: Re: Edge Accessibility was (Trouble with a menu in Druple)
← Previous message | Next message →
Speaking of MS Edge. Does anyone have any up to date info on current accessibility support in Edge? I know that it was taking a while to work out the bugs with JAWS, NVDA and Window Eyes.
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
From: Cliff Tyllick
Date: Fri, May 13 2016 10:48AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Courtney, Drupal sites are customized by adding individual modules to what is called the core code. The core code itself includes a connection of modules that are essential to creating a basic site. Modules not included in core are called contributed modules.
To be able to answer this question, I would need to know which module they are using to produce this menu. It might also be necessary to know which theme is producing the site's look and feel. (There are core and contributed themes, too.)
Once the problem is identified, then your developers must determine what's wrong:
' Something they did (or failed to do)?
' Something intrinsic to a core module (or theme)?
' Something from a contributed module (or theme)?
Of course, if they overlooked something or did the wrong thing, they need to fix your website. But the other two involve working with whoever develops the code.
If it's a core module or theme, they should see if this issue has already been reported as an issue for Drupal core and, if not, report it:
https://www.drupal.org/project/issues/drupal?categories=All
If it's a contributed module or theme, they should go to the module or theme's page on drupal.org and, if the issue hasn't been reported, report it.
Part of reporting the issue is to include a suggested fix, if they know one. By using free open source software, they are implicitly agreeing to help improve that software for everyone who uses it.
Your developers can broaden their resource base by joining Drupal groups that are relevant to their work. For example, the Accessibility (https://groups.drupal.org/accessibility), Mobile (https://groups.drupal.org/mobile), and Usability (https://groups.drupal.org/usability) groups might be interested in this topic and participate in fixing the issue.
By adding the issue to the appropriate queue and using the Drupal communities to touch base with other people who face the same problem, your developers can get the most out of Drupal, build their expertise quickly, and help make Drupal a better experience for everyone.
Good luck!
Cliff Tyllick
Accessibility Coordinator
Texas Department of Aging and Disability Services
512-438-2494
= EMAIL ADDRESS REMOVED =
Sent from my iPhone
Although its spellcheck often saves me, all goofs in sent messages are its fault.
> On May 13, 2016, at 10:25 AM, Mike Barlow < = EMAIL ADDRESS REMOVED = > wrote:
>
> Does the menu work at all in IE even without JAWS? If not then I'd address
> that problem first before trying to get it working for JAWS.
>
> *Mike Barlow*
> Web Application Developer
> Web Accessibility/Section 508 SME
>
> Lancaster, Pa 17601
> Office: 732.835-7557
> Cell: 732.682.8226
> e-mail: = EMAIL ADDRESS REMOVED =
>
> On Fri, May 13, 2016 at 11:06 AM, Ritz, Courtney L. (GSFC-7200) <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> Hello all,
>>
>> Many apologies if this has already been discussed, I haven't had a chance
>> to dig through the archives yet.
>>
>> My organization's developers have migrated a lot of our sites to Druple.
>> They're using an expandable-collapsible menu which they refer to as a
>> "hamburger?" menu.
>> Anyhow, lately, my experience has been that I cannot see the menu at all
>> using JAWS in IE. I can't expand or collapse it or anything. There's a
>> "toggle navigation" button but I can't activate it with the keyboard.
>> In Firefox, I get all the menu links as if all the menus were expanded.
>> While that makes for a huge list of links, it's better than having nothing
>> at all.
>>
>> Has anyone encountered this in Druple, and is there a fix or another menu
>> that might work? I'm clueless when it comes to Druple, but I can pass any
>> suggestions on to our developer folks.
>>
>> Courtney
>> >> >> >> > > > >
From: Jared Smith
Date: Fri, May 13 2016 11:00AM
Subject: Re: Edge Accessibility was (Trouble with a menu in Druple)
← Previous message | Next message →
> Speaking of MS Edge. Does anyone have any up to date info on current accessibility support in Edge?
This comprehensive summary was published yesterday -
https://blogs.windows.com/msedgedev/2016/05/12/accessible-ux-with-html5-and-uia/
Jared
From: Cliff Tyllick
Date: Fri, May 13 2016 11:03AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Courtney, your developers should start with the issue queue for bug reports the Superfish module:
https://www.drupal.org/project/issues/superfish?categories=1
I see several that might be related to the problem you are experiencing. The issue they have in common is that other modules that also control navigational menus override one or more of the settings in Superfish.
It does look like the module is actively maintained and the maintainer responds to issues relatively quickly. That said, just about anybody who is anybody in the world of Drupal is at DrupalCon in New Orleans this week, so responses might take longer than normal.
Best to you,
Cliff
Cliff Tyllick
Accessibility Coordinator
Texas Department of Aging and Disability Services
512-438-2494
= EMAIL ADDRESS REMOVED =
Sent from my iPhone
Although its spellcheck often saves me, all goofs in sent messages are its fault.
> On May 13, 2016, at 11:00 AM, L Snider < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi Courtney,
>
> Yes, Superfish menus can be made more accessible. It takes a bit of doing,
> but I know people who have done it (no clue what version of IE they were
> testing though, not sure how EDGE would work with it).
>
> Cheers
>
> Lisa
>
> On Fri, May 13, 2016 at 10:41 AM, Ritz, Courtney L. (GSFC-7200) <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> Hi again,
>>
>> I found out that the menu they're using in Drupal is actually called
>> Superfish. When you have any responsive themes on websites and the menu
>> compresses to three bars instead of an actual menu its called a hamburger
>> (because it kind of looks like a hamburger)
>>
>> Can Superfish be made accessible?
>>
>> Courtney
>> > > > >
From: Moore,Michael (Accessibility) (HHSC)
Date: Fri, May 13 2016 11:05AM
Subject: Re: Edge Accessibility was (Trouble with a menu in Druple)
← Previous message | Next message →
Thank you Jared, that was timely.
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
From: Morin, Gary (NIH/OD) [E]
Date: Fri, May 13 2016 11:19AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Hi, Lisa - when you say that Superfish is or can be accessible, to who? Persons with dexterity impairments and use speech recognition software? Persons who are blind or sight impaired?
From: L Snider
Date: Fri, May 13 2016 3:40PM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
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
On Fri, May 13, 2016 at 12:19 PM, Morin, Gary (NIH/OD) [E] <
= EMAIL ADDRESS REMOVED = > wrote:
> Hi, Lisa - when you say that Superfish is or can be accessible, to who?
> Persons with dexterity impairments and use speech recognition software?
> Persons who are blind or sight impaired?
>
>
From: Morin, Gary (NIH/OD) [E]
Date: Fri, May 13 2016 4:10PM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
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 ADDRESS REMOVED = ]
Sent: Friday, May 13, 2016 5:41 PM
To: Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = >
Cc: WebAIM Discussion List < = EMAIL ADDRESS 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
On Fri, May 13, 2016 at 12:19 PM, Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
Hi, Lisa - when you say that Superfish is or can be accessible, to who? Persons with dexterity impairments and use speech recognition software? Persons who are blind or sight impaired?
From: L Snider
Date: Fri, May 13 2016 4:20PM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
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 ADDRESS 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 ADDRESS REMOVED = ]
> *Sent:* Friday, May 13, 2016 5:41 PM
> *To:* Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = >
> *Cc:* WebAIM Discussion List < = EMAIL ADDRESS 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
>
>
From: Birkir R. Gunnarsson
Date: Fri, May 13 2016 5:03PM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ]
>> *Sent:* Friday, May 13, 2016 5:41 PM
>> *To:* Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = >
>> *Cc:* WebAIM Discussion List < = EMAIL ADDRESS 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.
From: L Snider
Date: Sat, May 14 2016 8:02AM
Subject: Re: Trouble with a menu in Druple
← Previous message | Next message →
Oh and I just saw this, which is great! WordPress developers are looking
for people to test it with speech recognition software. We are making
progress!
https://make.wordpress.org/accessibility/2016/05/13/20th-wordpress-accessibility-test-add-media-with-speech-recognition-software/
Cheers
Lisa
On Fri, May 13, 2016 at 5:20 PM, L Snider < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ]
>> *Sent:* Friday, May 13, 2016 5:41 PM
>> *To:* Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = >
>> *Cc:* WebAIM Discussion List < = EMAIL ADDRESS 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
>>
>>
>
From: Morin, Gary (NIH/OD) [E]
Date: Mon, May 16 2016 8:49AM
Subject: Re: Trouble with a menu in Drupel
← Previous message | No next message
Dragon has definitely come along way! Here at the NIH, we're getting ready to roll-out Microsoft Office 2016, as part of Office 365. I was able to accomplish nearly all tasks within Outlook 2016 without once using the keyboard! Granted, there has been some âuser error' in the past ⺠and my own learning, but I'm sure that neither Dragon nor Microsoft Office were up to this a couple of years ago. Just clearly reinforces that both AT vendors and âmainstream' software firms need to work with one another as they each further develop their products, to remain compatible and to improve the accessibility and usability of each companies' products.
I agree â this list is awesome, I look forward to reading it every day! Not a day goes by that I don't learn something that stretches my knowledge.
Gary
http://508.nih.gov
From: L Snider [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Friday, May 13, 2016 6:21 PM
To: Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = >
Cc: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Trouble with a menu in Druple
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 ADDRESS REMOVED = <mailto: = EMAIL ADDRESS 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 ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >]
Sent: Friday, May 13, 2016 5:41 PM
To: Morin, Gary (NIH/OD) [E] < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >>
Cc: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS 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