Comments on: Too much accessibility - FIELDSET LEGENDS

By: Bim

Bim — Wed, 24 Sep 2008 04:20:39 +0000

Tom, we’re in accord on that, if there were a standard length of words to use in a LEGEND, screen readers and their users would have a much better chance of dealing with them appropriately, and web authors would have some chance of getting it right. Do you think any body would be prepared to decide what the standard should be, and do you have a view on how many words a LEGEND should have as a maximum?

By: Bim

Bim — Wed, 24 Sep 2008 04:10:25 +0000

Phil, I think that AT should do what it does now, which is repeat the LEGEND at each form control that it relates to, or at least be capable of doing so. This behaviour helps people keep track of where they are in a form. It would also be nice if there was a verbosity setting to change this to read, perhaps in a different tone, just at the first form control covered by a LEGEND, for people who find it difficult to tolerate the repetition. The different tone would then inform users when they reached a different group of form controls, covered by a different LEGEND.

What’s your own view?

By: Tom

Tom — Sat, 20 Sep 2008 23:43:46 +0000

I totally agree with you about what a legend should contain. However, I think it becomes problemmatic when we try to code for screen readers. Instead, when we code to accross-the-board standards, we might encourage screen reader developers to adjust their products to a set of standards.

By: Phil Teare

Phil Teare — Wed, 03 Sep 2008 20:47:53 +0000

Would you rather AT only read it once? Is there a good reason for it not to only read it once? (If you’ve said so above, sorry, I’m writing this in a hurry and haven’t got my AT to read it al for me…)

Great practical advice though! Thanks Bim.

By: kuppu

kuppu — Sat, 08 Dec 2007 13:09:22 +0000

can we able to do fieldset for a single row containing more elements

By: J.Sexton

J.Sexton — Wed, 27 Jun 2007 23:00:31 +0000

Very good point, I will contact Dolphin to see if anyone has previously requested such a feature. Like you said, its already available for tables so why not forms?

I’ll post their response back here.

By: Bim

Bim — Wed, 09 May 2007 18:01:07 +0000

That’s a very good point. You would have thought that this should be possible, it’s similar to what happens in tables. Users don’t have to listen to headers on every cell they land on, they can query for it when they want it.

By: Yecril

Yecril — Wed, 09 May 2007 15:33:38 +0000

What the screen reader really should do is to read the legend once at the beginning and read it on demand in the middle.

By: Tim

Tim — Thu, 30 Nov 2006 05:33:11 +0000

Thanks, I thought I was sort of there with a simple accessible form but I was not sure why before you explained it to me, thanks:

Does having a “tabindex” help form navigation when using JAWS or any other text reader?

I could only get “tabindex” to work in Netscape, Mozilla and Firefox ignores them on Mac OSX

http://www.hereticpress.com/Dogstar/Publishing/ContactHP.html#skipnav

thanks

Tim

By: Thierry

Thierry — Thu, 30 Nov 2006 05:03:04 +0000

Thanks, I had no clue.