Comments on: Blog Challenge: Testing Your Blog’s Accessibility

By: LocustoAukcije

LocustoAukcije — Tue, 19 Apr 2011 21:51:38 +0000

This is a topic that is often neglected in webmaster world. Most people don’t consider that having a valid code might make your content accessible to a certain person or not.

By: Breezy’s Wordpress » Blog Archive » Daily Digest for 2009-03-23

Breezy’s Wordpress » Blog Archive » Daily Digest for 2009-03-23 — Tue, 24 Mar 2009 14:21:22 +0000

[...] Blog Challenge: Testing Your Blog’s Accessibility « Lorelle on WordPress « Daily Digest for 2009-03-22 [...]

By: dani

dani — Tue, 30 Sep 2008 13:40:37 +0000

I found the updated w3c markup validator is not as strict as validome..cmiiw

By: darran

darran — Mon, 16 Jun 2008 12:50:25 +0000

I am proud to say my blog is XHTML Strict 1.0 valid. And I am benefiting from all the search engine queries too!

By: Paradigmed Vision ¦ chaplainandrews.com

Paradigmed Vision ¦ chaplainandrews.com — Sun, 10 Feb 2008 07:27:50 +0000

[...] working on a weekly challenge that I do for Comic Book Day, I was issued a challenge to get my site accessible for people with [...]

By: chaplainandrews

chaplainandrews — Sat, 09 Feb 2008 16:03:41 +0000

Update: Through looking at my validation and working with some friends from my authority blogger forum…I’ve removed the errors down to 9 by removing the widgets. It is at about 32 errors right now, because I’m trying to fix them. Point is most of the errors are in the widgets themselves.

By: chaplainandrews

chaplainandrews — Thu, 07 Feb 2008 23:36:32 +0000

Busted! Ouch:) Thank you for the links–It looks like I have my work cut out for me.

By: Lorelle VanFossen

Lorelle VanFossen — Thu, 07 Feb 2008 22:56:02 +0000

@ chaplainandrews: If I understand you right, the CSS errors are from widgets you don't use. So remove the calls for the Widgets. Clean them out of the Theme. Open up the theme's template file which hosts the widgets and remove the code that calls them. How to Install, Configure, and Use WordPress Plugins and Finding Your CSS Styles in WordPress may help. Or edit your styles.css or whatever stylesheet these Widgets use with those styles and change the colors to be different. One red, the other green. :D Or ignore them. If they aren't being used, these kinds of errors are minor compared to other accessibility issues like titles in links and ALT descriptions in images. I tested your blog's front page for HTML errors and found over 100. These all need to be fixed, but this isn't the challenge as much as it is looking at how your blog will work across all browsers and uses.

By: Impaired Vision

Impaired Vision — Thu, 07 Feb 2008 22:44:15 +0000

[...] Many times, we don’t seem to see these people–and we may not be able to tell who they are, if they are not totally vision impaired–but they are living in the world of the unknown and doing it fearlessly. Many of them are reading our blogs and comments. We need to make our blogs as accessible as possible. [...]

By: chaplainandrews

chaplainandrews — Thu, 07 Feb 2008 22:08:40 +0000

I found five Warnings for the Same colors for color and background-color in two contexts (.tagged a:hover and a:visited) on all five, in flicker widgets that aren’t used. They are carry over from the original non-modified “cutline” theme.

Not bad from a guy that has no clue what I’m doing–I just do what I’m told. And I don’t know how to fix these problems.