RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)
Hi Mathew, http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp I have a bug report... tested against FF 3.6.4 and IE6 (no bug under Chrome 5.0.376) Steps to reproduce: - click on background - tab to focus first menu item - hit enter to display sub-items - tab through to the second menu - hit enter to display its sub-items (the first menu closes) - hit shift-tab to go back to the first menu The bug is either one of a) the first menu shouldn't open as the second menu is active, or b) that the second menu stays open. Thanks for the step by step, but unfortunately I cannot reproduce (in neither one of these browsers). Could somebody confirm the issue following the steps above? Thanks. As a side note, there is something strange in these steps as the first menu should close before you can even hit enter on the second one. Are you sure you do not have your mouse cursor over the first tab while checking the menu? Because that would explain what you describe. -- Regards, Thierry www.tjkdesign.com | www.ez-css.org | @thierrykoblentz *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] that old IE6 thing...
I know this was a recent discussion, and I don't want to revive an already well worn subject, but I just noticed something amazing on a multi user blog site I manage. Two blogs, same base domain, same template, same environment, same university. Blog 1: Audience: Librarians IE6: 42.2% Firefox (all versions): 23% Blog 2: Audience: Students IE6: 9.8% Firefox (all versions): 40.5% Proving once again, that knowing your audience is key. (and perhaps that librarians are a bit slow to upgrade ;) -- Andrew Harris and...@woowoowoo.com http://www.woowoowoo.com ~~~ * ~~~ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)
Sorry Thierry I only took a quick look at the page and didn't read it fully. Mike -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Thierry Koblentz Sent: 29 June 2010 17:34 To: wsg@webstandardsgroup.org Subject: RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu) Hi Mike, Sorry to say this but the keyboard friendly version: http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp Only fires, via keyboard, on Articles E-K in IEv8 or Firefox. This is by design. Keyboard users could not reach these pages if they were not focusable at least from the parent page. The About this solution section says: Note that keyboard users cannot skip the sub-menu related to the current page. This is because this sub-menu is exposed to SE (Search Engines) and thus accessible to keyboard users when JS is off. The sub-menus open via the *enter key*, this is to allow keyboard users to skip sub menus so they are not forced to tab through all the menu items. If the menu is accessible, it is *because* the sub menu related to the page itself *is* focusable (it is not styled with display:none). What this menu is missing though is a arrow pointer for *discoverability*. I have a title in there, but I think it's pretty useless (for 99.99% of users). If I had time, I'd add arrows and ARIA roles too. -- Regards, Thierry www.tjkdesign.com | www.ez-css.org | @thierrykoblentz *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** This is a confidential email. Tesco may monitor and record all emails. The views expressed in this email are those of the sender and not Tesco. Tesco Stores Limited Company Number: 519500 Registered in England Registered Office: Tesco House, Delamare Road, Cheshunt, Hertfordshire EN8 9SL VAT Registration Number: GB 220 4302 31 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
FW: [WSG] CSS Expandable Menu
As a follow-up to my original email, the following methods have been very well designed from the accessibility point of view: http://juicystudio.com/article/ecmascriptmenu.php http://www.456bereastreet.com/archive/200705/accessible_expanding_and_co llapsing_menu/ A further example worth considering: http://www.splintered.co.uk/experiments/16 Thanks again for all the helpful posts regarding this topic. Grant *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Is it still necessary to encode ampersands?
On Jun 25, 2010, at 5:10 AM, David Dorward wrote: This is fair. You ask for free support, but provide test data that doesn't pass basic, automated QA tests. It doesn't really motivate people to help. Actually it's not always fair. There are many kinds of validation errors, an experienced developer should be able to tell from the generated error codes whether the problem is caused by the error; an experienced developer also should be able to tell from the layout, CSS and the markup whether the person who asked for help is a newbie (thus has no knowledge of validation and require you, the experienced developer to educate him/her) or simply doesn't care his/her markup; one can then decide whether to help or not. Internet is so big and so small world, if you are in a list long enough you can pretty much tell who is in a list to seek quick fix from other every time he/she runs into yet another same IE problem, or is in the list to better/improve his/her skill, and you, the experienced developer can then make a better decision whether to help the person or not. That being said, if one sees an error page and doesn't get motivated to help, and unable to differentiate what those errors are, the best approach might be just don't say anything instead of posting a fix your validation error! message! Just my 2 cents! If I ask how to make the facebook like button shows up in IE browser, should you tell me to fix the validation error first or should you ask me to hunt down Mark Zuckerberg first? :-) tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Is it still necessary to encode ampersands?
On Wed, Jun 30, 2010 at 12:34 PM, Nancy Johnson njohnso...@gmail.comwrote: I think you said it very nicely. The sites I am work on, one agency designs and gives initial html mock-up and we hook it up to an CMS system and the client adds content. Could it be managed better? yes, but that is the way we work. The validator doesn't handle javascript, and although I do my best to use external files, there on times which I find that the js needs to be inline and that causes some validation issues. The links with event handlers don't seem to validate. Owners chose the friendly URL's. Owners add content, the pages are flexible enough for them to add their own html coding and there are errors in their coding as well. Currently, not one error has to do with the CSS or how the html coding is handled. Raises another question. How does one handle inline javascript these days? Because of the dyanmic nature of a site sometimes the JS can't go in external URL's Links with eventhandlers. etc. *I find that adding into these meta tags into the header can solve the inline validation issues sometimes, depending on the doctype. * *meta http-equiv=Content-Style-Type content=text/css / meta http-equiv=Content-Script-Type content=type /* -- Susan R. Grossman susan.r.gross...@gmail.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Out of Office AutoReply: WSG Digest
I will be out of the office until Wednesday, July 7. Please leave a message and I'll get back to you then. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Is it still necessary to encode ampersands?
If you use XHTML doctype, you can add CDATA comment, this will prevent possible
validation errors.
Example:
script type=text/javascript
/* ![CDATA[ */
jQuery(document).ready(function(){
jQuery(ul.sf-menu).superfish();
});
/* ]] */
/script
I mostly work on Magento projects these days that use inline script heavily,
experience show that lack of CDATA comment doesn't always trigger validation
error.
tee
On Jun 30, 2010, at 1:42 PM, Susan Grossman wrote:
Raises another question. How does one handle inline javascript these
days? Because of the dyanmic nature of a site sometimes the JS can't
go in external URL's Links with eventhandlers. etc.
I find that adding into these meta tags into the header can solve the inline
validation issues sometimes, depending on the doctype.
meta http-equiv=Content-Style-Type content=text/css /
meta http-equiv=Content-Script-Type content=type /
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
