Re: making dynamic menus accessible

  • From: "Ricks Place" <OFBGMail@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Tue, 6 May 2008 08:24:01 -0400

Teddy:
Is this your site? Allot of investing features and that's what I play with. By the way, what menu tool are they using? Is it the one you mentioned in a prior post?
If that's your site, pretty nice.
Rick Farmington Mich. USA
----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Tuesday, May 06, 2008 6:43 AM
Subject: Re: making dynamic menus accessible


Hi Rick,

Please check that menu on:
http://www.tranzactiibursiere.ro/cotatii

You can jump directly to the menu using the "l" key, and you will hear:
List of 8 items (contains 7 nested lists)

(The list has 8 items, but it contains only 7 nested lists, because the first item is a "Home" item that doesn't have submenus, so only the other 7 menus have items in them.)

If you arrow down, you will hear:
. Cotatii graphic SubMenu

The menu item shows just "Cotatii" and a graphic that shows that this item has submenus, and the alt attribute of it is "SubMenu" in order to make it read like Jaws reads the standard Windows menus.

If you arrow down once more, you hear:
List of 3 items nesting level 1

This tells that the "Cotatii" menu has a submenu with 3 elements, and it also tells the nesting level, showing that these are submenus of the "Cotatii" menu. Of course, the menu items could contain other sub-menus with a higher nesting level.

After this, you will hear those 3 list elements, ended by:
list end nesting level 1

This tells that this menu ended, and a new menu begins.

Well, my site is multilingual, and it is also based on the browser language preferences, so instead of "Cotatii", you might hear "Quotes".

Octavian

----- Original Message ----- From: "Ricks Place" <OFBGMail@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Tuesday, May 06, 2008 1:27 PM
Subject: Re: making dynamic menus accessible


Hi Guys and dolls:
Teddy, where can I check out your menu control in action?
By the way, My TreeView has the Expand / collapse turned off and appears as a normal static TreeView. I'm guessing you either are getting a cached old version of the site's opening page or did not hit f5 to refresh the browser after clicking the TreeView Navigation option. By the way, my Skip Navigation hyperlink only works the first time I click it, any idea why that might be happening?
Rick Farmington Mich. USA
----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Tuesday, May 06, 2008 4:57 AM
Subject: Re: making dynamic menus accessible


Hi Jenifer,

Have you asked a sighted person to test those menus?
I guess you didn't.

Those menus are not seen as a list of lists by a sighted, but as a simple line with the top menu labels, and if a sighted person hovers the mouse over one of the menus, the menu opens just like the menus from a common Windows desktop application.

So the sighted persons don't need to parse the whole list of menu items as you told.

And from what you said I see that you don't know how other kind of menus work and how much html code they imply. Most of them use more Javascript and more HTML for creating the menus, so you can't say that too much html or javascript code should be downloaded on the visitor's computer if using this menu type.

From this point of view, maybe the menus generated by some Javascript libraries like YUI or DOJO may require less code, because the Javascript code which should be downloaded could be also used for other things, not only for creating menus, but other kind of widgets, however unfortunately the menus created with those libs are not very friendly for the blind.

So I still don't understand what kind of overloading you are talking about.

Octavian

----- Original Message ----- From: "Jennifer Sutton" <jsuttondc@xxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Tuesday, May 06, 2008 9:22 AM
Subject: making dynamic menus accessible


Hi:

Since the subject is straying far away from asp menu controls, I'm changing the subject line.

I'm talking about visual and mental overload with the menuing system you mentioned. All of those lists may be handy for a blind person, but they're one heckuva lot of text for someone's eyes to have to look through and/or for someone to process if reading visually is not their speediest method of access.

These menus are very text-heavy, and my only point is that while blind folks may love text, not everyone does.

Realizing this requires thinking outside of the blind-folks box when you're designing a Web site that requires dynamic menus. The goal should be, in my view, to strike a balance for all audiences.

If you care to research this further, the topic of dynamic accessible menus has been discussed on the WebAIM list many times.

Jennifer
 At 11:35 PM 5/4/2008, you wrote:
Why "overload"?

All the menus which are static, which don't use AJAX for retrieving dynamicly the elements of a certain menu after clicking on it, use much more html code than that menu.

I never needed to create dynamicly generated menus by Javascript, because I always need to use the same set of menus everywhere, and if I would need something different in a certain page, it is much more simple to create another template with another menu because I don't need to create a server side program that provides data with the menu elements that should be got with an AJAX request.

Octavian

__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind

Other related posts: