-
☆ A M B ☆
- 1,231 Posts
Hey folks,
Could someone tell me which would be the best way to validate and test to see if you site meets accessibility standards? I have used google and the tests are some what non user friendly.
My site validates using W3C validator but that’s only testing to see if the structure of the coding is correct, am i right?
I’m wondering which tools you professionals use for testing your sites, if you do at all.
Thanks!
Ross
A also use the tools from the developers toolbar for FF for this. it is very handy.
-
MODX Staff
- 2,502 Posts
There are absolutely NO automated tools for fixing accessibility issues. These tools can point to issues in your code that you should look at but some are just plain silly.
Some will tell you that you need a non-null value for alt for an image but if the image is a decoration that doesn’t add information or other value to the content it will be annoying and extraneous for users. In addition most validators have no way to tell if they contrast is too low, if people with colourblindess can use the site if the text is too small.
That being said, use the HTMLValidator Extension for Firefox has a decent checker but you need to review the site for many different types of accessibility and usability.
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
-
☆ A M B ☆
- 1,231 Posts
Thanks all for your replies.
I generally only use W3C HTML, CSS validation and link-check... would you think that is good enough for an automated check of your site and then get a group of individuals to check it out for real life evaluation?
The MODx community makes an excellent "group of individuals to check it out for real life evaluation"...
Website: www.mercologia.com
MODX Revo Tutorials: www.modxperience.com
MODX Professional Partner
-
MODX Staff
- 2,502 Posts
Again, Accessibility can only check certain things but it is up to you to ensure that the results are useful to the end user. Learning or reading the Accessibility guidelines is a good step another is to do the validation and with the errors try to make changes that make sense. Again most Accessibility software can’t make logic decisions for you.
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub