I was going to apply the CSS style rule {outline:none} but I read in an article that
its better for accessability purposes not to do this.
Users who cant operate a mouse rely on the outline feature to navigate using the TAB key.
I was wondering what others thought about this and other accessability issues.
To what extent do you compromise functionality or appearance in order to meet accessability requirements?
Do you have an accessability checklist for your sites?
Whether you're a seasoned veteran or a struggling beginner, Web Radiance is the web development and web design forum for you. You'll find answers to all your HTML, CSS, SEO, and Programming needs. Pull up a chair and stay awhile.
Page 1 of 1
Do you have an accessability checklist for your sites?
#2
Posted 23 April 2008 - 11:17 PM
Personally, I prefer both content quality and accessibility over polish.
#3
Posted 21 June 2008 - 03:55 AM
I saw benbacardis post in another category about
accessability so I thought I`d post his link here for posterity.
Fortunately I seem to be doing most of the things on the list already.
I especially liked the comments re CAPTCHA (my pet hate).
(Watch this if you're not sure why )
Its worth quoting from the PDF document:
"Avoid CAPTCHAs unless you have no other choice, and even then
they should be avoided."
http://cameronmoll.com/archives/2008/06/we...lity_checklist/
accessability so I thought I`d post his link here for posterity.
Fortunately I seem to be doing most of the things on the list already.
I especially liked the comments re CAPTCHA (my pet hate).
(Watch this if you're not sure why )
Its worth quoting from the PDF document:
"Avoid CAPTCHAs unless you have no other choice, and even then
they should be avoided."
http://cameronmoll.com/archives/2008/06/we...lity_checklist/
This post has been edited by Beavis: 21 June 2008 - 04:22 AM
#4
Share this topic:
Page 1 of 1


Help
This topic is locked
MultiQuote










