Shame on you EPSN!
I just came across some HTML this morning that had FORM FIELDS inside of an Ordered List.
<form action=”" method=”post”>
<label for=”firstName”>First Name</label> <input id=”firstName” type=”text” />
I have never seen this done and I wanted to see if anyone understood the methodology or if it served a true purpose towards Accessibility?
Is it compliant?
Does it break any guidelines or priorities?
Is it symantec?
Is it Screen Reader Clutter?
P.s. I know HTML and CSS junkies like this for formatting.
Imagine having restricted or limited motor control and you need to use the keyboard to navigate your way around internet. Now image that every web developer out there disabled the nice little outline feature that shows you what object you are focused on. Links, Forms, Etc…
If you can’t see where you are on the page how you going to know where you are going?
I was reading a great post on www.seo-news.com and they had one paragraph that simply puts some truth to how Accessibility could be good for an ROI.
Accessibility And Standards
Site accessibility is an integral part of good website design, but it should also be considered an important factor in any SEO strategy. Using standards based code for your website will help to ensure that anybody that wishes to access and view your website will be able to do so. It will also mean that the spiders used by search engines will be able to access and index your pages effectively ensuring that you get the full credit for your site.
Read the whole thing at www.seo-news.com!
So with out getting into a huge post I just wanted to point out that having a website that works for people that use the mouse and or people that can only use the keyboard doesn’t mean it is accessible. Keep in mind, for it to be truly accessible it needs to be perceivable, operable and understandable for visual, motor/mobility, auditory, and cognitive disabilities.