Comments on: Code notes: Expanding and collapsing lists http://rishida.net/blog/?p=86 News of changes to my main site, and W3C related posts. Thu, 05 Aug 2010 18:29:35 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: site admin http://rishida.net/blog/?p=86&cpage=1#comment-6678 site admin Mon, 02 Apr 2007 19:51:44 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6678 Hi Derek, Thanks for the suggestion. It just so happens that I have implemented exactly what you suggest already, and will upload the new version soon. Hi Derek, Thanks for the suggestion. It just so happens that I have implemented exactly what you suggest already, and will upload the new version soon.

]]> By: Derek Featherstone http://rishida.net/blog/?p=86&cpage=1#comment-6677 Derek Featherstone Mon, 02 Apr 2007 19:25:42 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6677 You might also want to reconsider the positioning of hidden content off-left. Going off-left rather than display:none means that a sighted keyboard user will be tabbing through a load of links that they can't see on the page. This can be very confusing. Using display:none removes the "hidden" content from the tab flow, but off left doesn't. This means to get from one of your triggers to the next - you have several tab stops instead of just one. You might also want to reconsider the positioning of hidden content off-left. Going off-left rather than display:none means that a sighted keyboard user will be tabbing through a load of links that they can’t see on the page. This can be very confusing.

Using display:none removes the “hidden” content from the tab flow, but off left doesn’t. This means to get from one of your triggers to the next – you have several tab stops instead of just one.

]]> By: site admin http://rishida.net/blog/?p=86&cpage=1#comment-6648 site admin Fri, 30 Mar 2007 07:25:23 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6648 Hi Patrick. Thanks for the comments. re a elements: ah, that's why. Ok I'll look at putting them in when i get a moment (which may not be for several days). re open/close buttons: yes, i ummed and ahhed a lot about that. In the end i decided that I didn't want to force the page owner to write their own page-specific javascript, so i did it the way i describe, but i know it's a problem if ever you have styling turned off. hmm... Hi Patrick. Thanks for the comments.
re a elements: ah, that’s why. Ok I’ll look at putting them in when i get a moment (which may not be for several days).

re open/close buttons: yes, i ummed and ahhed a lot about that. In the end i decided that I didn’t want to force the page owner to write their own page-specific javascript, so i did it the way i describe, but i know it’s a problem if ever you have styling turned off. hmm…

]]> By: patrick h. lauke http://rishida.net/blog/?p=86&cpage=1#comment-6647 patrick h. lauke Thu, 29 Mar 2007 20:16:42 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6647 although it'a very old and does something subtly different, you could have a look at http://www.splintered.co.uk/experiments/31/ although it’a very old and does something subtly different, you could have a look at http://www.splintered.co.uk/experiments/31/

]]> By: patrick h. lauke http://rishida.net/blog/?p=86&cpage=1#comment-6646 patrick h. lauke Thu, 29 Mar 2007 20:12:59 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6646 also, instead of having the open/close buttons in the markup and unhiding them via js, a cleaner approach would be to leave them out of your markup and generate them via javascript in the first place - no javascript, no generated buttons. also, instead of having the open/close buttons in the markup and unhiding them via js, a cleaner approach would be to leave them out of your markup and generate them via javascript in the first place – no javascript, no generated buttons.

]]> By: patrick h. lauke http://rishida.net/blog/?p=86&cpage=1#comment-6645 patrick h. lauke Thu, 29 Mar 2007 20:10:28 +0000 http://people.w3.org/rishida/blog/?p=86#comment-6645 problem is, though, that unless you're generating proper A elements (or use some further trickery to make an element focussable), your final example is completely keyboard-inaccessible. problem is, though, that unless you’re generating proper A elements (or use some further trickery to make an element focussable), your final example is completely keyboard-inaccessible.

]]>