Comments on: Paradigmed Vision http://chaplainandrews.com/paradigmed-vision Mon, 08 Mar 2010 11:56:28 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Weekly Digest: Catching Up, Speaking San Francisco, Future Post Mixup, Talking to Blogger Talks, and More « Lorelle on WordPress http://chaplainandrews.com/paradigmed-vision/comment-page-1#comment-105 Weekly Digest: Catching Up, Speaking San Francisco, Future Post Mixup, Talking to Blogger Talks, and More « Lorelle on WordPress Thu, 13 Mar 2008 00:39:13 +0000 http://chaplainandrews.com/paradigmed-vision#comment-105 [...] ease of including accessibility standards in your blog and website with a quote from the post. And Chaplain Andrews wrote: We don’t think about it enough, but there are many people out there who use special [...] [...] ease of including accessibility standards in your blog and website with a quote from the post. And Chaplain Andrews wrote: We don’t think about it enough, but there are many people out there who use special [...]

]]> By: Lorelle http://chaplainandrews.com/paradigmed-vision/comment-page-1#comment-13 Lorelle Sun, 10 Feb 2008 17:47:37 +0000 http://chaplainandrews.com/paradigmed-vision#comment-13 I could have given you all the answers when this issue first came up, and, like I do with all of my blog challenges, I didn't. And you learned something special, didn't you. This is the reward I get for offering these blog challenges. A chance to open up the eyes of someone who thinks they know what they are doing, and find out that they are missing the whole point, much like your own work. :D Years ago, I found statistics that claimed 25% of web users were disabled in some way, often requiring special equipment to access the web. Today, with such equipment and programs more easily accessible - the web is accessible to even greater numbers of the disabled. We have to remember them when we blog, no matter what we blog about. Most of the errors on your blog were simple mistakes in coding. The real killers are the mistakes or errors which stop search engines from flowing nicely through our coded web pages, and ignoring the disabled. I'm glad you got on the ball and fixed both of these issues. While it doesn't show on the surface, those who run into the underlying code and require it to be "equal access" are going to adore you. Thanks. You are the reason I keep offering these blog challenges. Now, if I could just get bloggers to work harder on editing their blog posts for writing errors... :D I could have given you all the answers when this issue first came up, and, like I do with all of my blog challenges, I didn’t. And you learned something special, didn’t you.

This is the reward I get for offering these blog challenges. A chance to open up the eyes of someone who thinks they know what they are doing, and find out that they are missing the whole point, much like your own work. :D

Years ago, I found statistics that claimed 25% of web users were disabled in some way, often requiring special equipment to access the web. Today, with such equipment and programs more easily accessible – the web is accessible to even greater numbers of the disabled. We have to remember them when we blog, no matter what we blog about.

Most of the errors on your blog were simple mistakes in coding. The real killers are the mistakes or errors which stop search engines from flowing nicely through our coded web pages, and ignoring the disabled.

I’m glad you got on the ball and fixed both of these issues. While it doesn’t show on the surface, those who run into the underlying code and require it to be “equal access” are going to adore you.

Thanks. You are the reason I keep offering these blog challenges.

Now, if I could just get bloggers to work harder on editing their blog posts for writing errors… :D

]]>