Re: [WSG] :hover and accessibility
Christopher M Kelly wrote: Could a JavaScript onfocus/onblur combo work for this? I've been trying to create accessible drop-down menus with CSS and JavaScript and haven't quite got it working. What do you think about this kind of menu: http://www.movingart.info/ There should be a skip to menu link, but otherwise I think it's quite accessible with keyboard and mouse. It uses :hover (and csshover.htc for IE). I'd like to know pro's and con's of this method. /Anders ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Duplicate buttons
Patrick H. Lauke wrote: well, imagine the user has a screenreader or braille display and is tabbing through the form . they end up on the first submit button, and have no way of knowing that there's more after that button, so they submit it at the first intermediate step...not good. That's not a problem. All you need to do is make sure the tab indexes are higher than than the last element. Also, iirc, setting the tab index to -1 will make it unaccessible by tabbing; just make sure you don't do that to the last one. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Can someone help me figure out some semantic mark-up, please?
Thanks for the help, guys. I've gone with the dl as suggested by
Mordechai, and the script that was in Zeldman's book (sorry, Mordechai, but
it seemed like a slightly simpler, more flexible way of doing it - or maybe
it's just that I've combed through it so often that I actually understand
what it does!).
Minor problem, however: I started by just creating a vanilla list with
hard-coded values and giving the ID for each level a number. Tested it, and
it worked beautifully. Then I put in the first level of dynamic generation
(at the top level, drawing the category names from the database) and used
the ID number for each category as the ID of the sub-dl. That worked too,
but I realised that if I just used straight numbers, then there would be
problems when I started bringing in more levels of dynamic content since
some ID numbers would be repeated (for example, the number 2 may exist as an
ID number for a Category, a Subcategory and a Section, so there would be 3
instances of ID=2 on the page and that would stuff things up). I figured
that shouldn't be too hard, and with the addition of a little text, I now
had some first-level ID's like Sub1, Sub2, etc. Now, suddenly, the system
stops working!
Can anyone tell me why this should be? Why did it work when the IDs were
just numbers, but stop working when it was a letter-and-number combination?
The example in Zeldman's book uses text as the ID of the section he's
toggling, so I'm sure that the script is meant to work with text.
The script, for those who don't have the book, is as follows:
function toggle(targetID) {
if (document.getElementById) {
target = document.getElementById(targetID);
if (target.style.display == none) {
target.style.display = ;
} else {
target.style.display = none;
}
}
}
Can anyone suggest why I'm having this problem?
Cheers,
Seona.
__
ella for Spam Control has removed Spam messages and set aside Later
for me
You can use it too - and it's FREE! http://www.ellaforspam.com
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
attachment: winmail.dat
RE: [WSG] Can someone help me figure out some semantic mark-up, please?
Well, I've found a way around the problem (used an incrementing counter
instead of the ID-number from the database, so each item has a unique ID) so
this question isn't exactly pressing any more.
I'd still love to know the answer though, if for no other reason than that
there's a good chance I'll use this script again in future and it would be
nice to know in advance if text-ID's are workable.
BTW, in answer to an earlier question about the number of items that will
eventually be in the list, about 98% of the time they will be accessing the
data across the internal network so there is still not going to be too much
of a lag (management has declared it acceptable, anyway, given that it won't
have to happen very often). And front-end users never get a page that
returns all items in the catalogue, so variable connection speeds aren't
really an issue either. :)
Cheers,
Seona.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sunday, 29 August 2004 8:50 AM
To: [EMAIL PROTECTED]
Subject:RE: [WSG] Can someone help me figure out some semantic
mark-up, please?
Thanks for the help, guys. I've gone with the dl as suggested by
Mordechai, and the script that was in Zeldman's book (sorry, Mordechai, but
it seemed like a slightly simpler, more flexible way of doing it - or maybe
it's just that I've combed through it so often that I actually understand
what it does!).
Minor problem, however: I started by just creating a vanilla list with
hard-coded values and giving the ID for each level a number. Tested it, and
it worked beautifully. Then I put in the first level of dynamic generation
(at the top level, drawing the category names from the database) and used
the ID number for each category as the ID of the sub-dl. That worked too,
but I realised that if I just used straight numbers, then there would be
problems when I started bringing in more levels of dynamic content since
some ID numbers would be repeated (for example, the number 2 may exist as an
ID number for a Category, a Subcategory and a Section, so there would be 3
instances of ID=2 on the page and that would stuff things up). I figured
that shouldn't be too hard, and with the addition of a little text, I now
had some first-level ID's like Sub1, Sub2, etc. Now, suddenly, the system
stops working!
Can anyone tell me why this should be? Why did it work when the IDs were
just numbers, but stop working when it was a letter-and-number combination?
The example in Zeldman's book uses text as the ID of the section he's
toggling, so I'm sure that the script is meant to work with text.
The script, for those who don't have the book, is as follows:
function toggle(targetID) {
if (document.getElementById) {
target = document.getElementById(targetID);
if (target.style.display == none) {
target.style.display = ;
} else {
target.style.display = none;
}
}
}
Can anyone suggest why I'm having this problem?
Cheers,
Seona.
__
ella for Spam Control has removed Spam messages and set aside Later
for me
You can use it too - and it's FREE! http://www.ellaforspam.com
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
__
ella for Spam Control has removed Spam messages and set aside Later
for me
You can use it too - and it's FREE! http://www.ellaforspam.com
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
attachment: winmail.dat
Re: [WSG] :hover and accessibility
Christopher M Kelly wrote:
Putting focus on links with the TAB
key will not invoke the :hover, thus they'll never see the submenu items.
Could a JavaScript onfocus/onblur combo work for this? I've been trying to
create accessible drop-down menus with CSS and JavaScript and haven't quite
got it working.
Setting focus via the tab key will not invoke the :hover state,
correct. That is what the :focus state is for. IE doesn't come to the
party for the :focus pseudo class, but it does treat :active in the
same way.
A quick and simple way to make sure everyone can see which link is
currently selected is like this:
a:link {}
a:hover, a:focus, a:active {}
RE: the suggestion made about udm4 - go for it, Brothercake has been
working on that for well over a year and it's a fine example.
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Can someone help me figure out some semantic mark-up, please?
On Sunday, Aug 29, 2004, at 09:09 Australia/Sydney, Seona Bellamy wrote: Well, I've found a way around the problem (used an incrementing counter instead of the ID-number from the database, so each item has a unique ID) so this question isn't exactly pressing any more. I'd still love to know the answer though, if for no other reason than that there's a good chance I'll use this script again in future and it would be nice to know in advance if text-ID's are workable. Seona, depending on the doctype you're using, ID's that are just numbers won't validate. They need to start with an alpha character - for XHTML 1 Strict, at least. But there again, if your project is for offline use, maybe validation doesn't matter... ;o) N ___ Omnivision. Websight. http://www.omnivision.com.au/ ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
