Re: [WSG] Keyboard accessible DHMTL navigation
Return Receipt Your Re: [WSG] Keyboard accessible DHMTL navigation document: wasLisa Kerrigan/StateDevPolicy/DSD received by: at:12/02/2007 09:44:01 AM ** Department of Innovation, Industry and Regional Development, Government of Victoria, Victoria, Australia. This e-mail and any attachments may contain privileged and confidential information. If you are not the intended recipient, you may not distribute reproduce this e-mail or the attachments. If you have received this message in error, please notify us by return e-mail. ** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Keyboard accessible DHMTL navigation
It is very important that the character encoding of any XML or (X)HTML document is clearly labeled, so that clients can easily map these encodings to Unicode. This can be done in the following ways: a.. Send the 'charset' parameter in the Content-Type header of HTTP. Example: Content-Type: text/html; charset=utf-8 To do this you will need to have access to server settings or serve your document via scripting (see Setting the HTTP charset parameter for more information). b.. For XML (including XHTML), use the encoding pseudo-attribute in the XML declaration at the start of a document or the text declaration at the start of an entity. Example: ?xml version=1.0 encoding=utf-8 ? For more : http://www.w3.org/International/O-charset Ai ling Cai Graphic Web designer B. www.goodmorning-italy.com W. www.ailingcai.com M. [EMAIL PROTECTED] C. 3406434203 - Original Message - From: Tim [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Friday, February 09, 2007 2:29 AM Subject: Re: [WSG] Keyboard accessible DHMTL navigation Yara, TABS seems to work OK for me on Netscape Mac version. Meta tags could provide a link to an accessibility statement giving keyboard shortcuts. Some Meta tags duplicated. meta http-equiv=expires content=01 apr 1995 01:10:10 gmt / meta name=robots content=noindex,nofollow / I'm don't think that the javascript is necessary and what effect will it might have on accessibility or bots who will not read it, a screenreader? The javascript at the page bottom could be linked to in the header as an external file! Why is the charset=utf-8 ? I may be wrong but isn't is better to use: meta http-equiv=Content-Type content=text/html;charset=ISO-8859-1 / Have they found a way to dismantle that concrete steel sprung monolith at UTS yet? Tim On 09/02/2007, at 12:00 PM, Yara Ryan wrote: Hi, I am have a problem trying to make a DHTML navigation keyboard accessible. http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html Currently this demo page http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html sort of works when trying to tab to each of the section tabs and there respective group links to make it work for Tab1 I added a onkeyup event to the tab that will make the group div visible when they let go of the tab key. Does any one know if this is really the right approach as it seems like a bit of a hack? Does anyone have any other suggestions that could be useful. -- Cheers, Yara Ryan institute for interactive media and learning uts t: 61 2 9514 2197 | e: [EMAIL PROTECTED] | w: http://www.iml.uts.edu.au *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** The Editor Heretic Press http://www.hereticpress.com Email [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Keyboard accessible DHMTL navigation
Hi, I am have a problem trying to make a DHTML navigation keyboard accessible. http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html Currently this demo page http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html sort of works when trying to tab to each of the section tabs and there respective group links to make it work for Tab1 I added a onkeyup event to the tab that will make the group div visible when they let go of the tab key. Does any one know if this is really the right approach as it seems like a bit of a hack? Does anyone have any other suggestions that could be useful. -- Cheers, Yara Ryan institute for interactive media and learning uts t: 61 2 9514 2197 | e: [EMAIL PROTECTED] | w: http://www.iml.uts.edu.au *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Keyboard accessible DHMTL navigation
Hi Yara, You might like to check out a roundup I did of dropdown menus with comments made on their accessibility etc.: http://www.tyssendesign.com.au/articles/css/dropdown-low-down/ On Fri, 09 Feb 2007 11:00:13 +1000, Yara Ryan [EMAIL PROTECTED] wrote: Hi, I am have a problem trying to make a DHTML navigation keyboard accessible. http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html Currently this demo page http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html sort of works when trying to tab to each of the section tabs and there respective group links to make it work for Tab1 I added a onkeyup event to the tab that will make the group div visible when they let go of the tab key. Does any one know if this is really the right approach as it seems like a bit of a hack? Does anyone have any other suggestions that could be useful. -- Tyssen Design Web print design services www.tyssendesign.com.au Ph: (07) 3300 3303 Mb: 0405 678 590 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Keyboard accessible DHMTL navigation
Yara, TABS seems to work OK for me on Netscape Mac version. Meta tags could provide a link to an accessibility statement giving keyboard shortcuts. Some Meta tags duplicated. meta http-equiv=expires content=01 apr 1995 01:10:10 gmt / meta name=robots content=noindex,nofollow / I'm don't think that the javascript is necessary and what effect will it might have on accessibility or bots who will not read it, a screenreader? The javascript at the page bottom could be linked to in the header as an external file! Why is the charset=utf-8 ? I may be wrong but isn't is better to use: meta http-equiv=Content-Type content=text/html;charset=ISO-8859-1 / Have they found a way to dismantle that concrete steel sprung monolith at UTS yet? Tim On 09/02/2007, at 12:00 PM, Yara Ryan wrote: Hi, I am have a problem trying to make a DHTML navigation keyboard accessible. http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html Currently this demo page http://datasearch.uts.edu.au/site_manager_sites/dab2007/demo_index.html sort of works when trying to tab to each of the section tabs and there respective group links to make it work for Tab1 I added a onkeyup event to the tab that will make the group div visible when they let go of the tab key. Does any one know if this is really the right approach as it seems like a bit of a hack? Does anyone have any other suggestions that could be useful. -- Cheers, Yara Ryan institute for interactive media and learning uts t: 61 2 9514 2197 | e: [EMAIL PROTECTED] | w: http://www.iml.uts.edu.au *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** The Editor Heretic Press http://www.hereticpress.com Email [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Keyboard accessible DHMTL navigation
You might like to check out a roundup I did of dropdown menus with comments made on their accessibility etc.: http://www.tyssendesign.com.au/articles/css/dropdown-low-down/ That's a great summary, John. FWIW, I use Infinite Menus. The issue of opening new windows when tabbing to submenus may be due to its habit of inserting target=_new as a default for all links. It's an annoying habit, but the ability to edit the menus with a text editor makes it easy to fix. There may also be some confusion with their pure javascript, pure CSS and combo javascript/CSS menu models. The pre CSS option should work with javascript turned off, but its code has even more complicated CSS. I get mostly positive feedback on accessibility issues with IM, but I'll definitely be exploring some of the others you describe. Ricky *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
