I first wanted to say thanks to Derek and Graham for providing all this
really great info.
Not that I'm fussed and purely playing devil's advocate but I cannot
help but see some kind of irony in having an accessibility guideline
document in .doc format. It's like the righteous word scribed on the
devil's stationery or something, I can hear the indignant echoes of the
do not send .doc files argument [1].
I did want to comment that the form error in the label suggestions
Derek gave have really got me thinking about how my CMS returns users
to forms and alerts them. I was simply having the form errors at the
top of the page and changing the appearance of the relevant field's
label. This is clearly not good enough for screenreaders and until
listening to (WE05 podcast) and reading the examples I had not thought
through to a good solution. I presume that what would be best would be
a combination of a message like
"Please check the errors indicated in the form below"
...at the top of the form and have the "this must not be blank" on the
relevant field(s)?
Thanks,
Nick
[1] http://www.google.com/search?q=do+not+send+word+.doc+files
Hi all,
January this year, when I was still working for Telstra I rewrote their
Universal Accessibility Guidelines document
http://www.telstra.com.au/standards/docs/accb_03001.doc. You may be
interested to have a look at the section on forms and the examples I
wrote
there.
Regards
Graham Cook
UA Oz
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Derek Featherstone
Sent: Tuesday, 11 October 2005 10:56 AM
To: [email protected]
Subject: RE: [WSG] simplyaccessible.org
On 10/11/05, Terrence Wood wrote:
Agreed, you are absolutely correct. Doh! I didn't acutally check the
source code, no wonder my earlier post was confusing. Sorry Derek.
No worries...
If anyone *is* interested in replicating Dereks layout without the
extra div's try this:
<snip />
for what it's worth - I did try using that at certain points, but
generally preferred to add in explicit divs to provide another hook for
styling. YMMV - I also preferred to place each "row" in a block level
element so that without author styles each form field and its label is
still on a row of its own, though that use case may not be as
important.
Now then, I'd better get back to it so that I can post the second round
of examples... :)
Cheers,
Derek.
--
Derek Featherstone [EMAIL PROTECTED]
tel: 613-599-9784 1-866-932-4878 (toll-free in North America)
Web Development: http://www.furtherahead.com
Personal: http://www.boxofchocolates.ca
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
