Recently in About This Blog Category

Another fairly stream of consciousness post, sorry folks. Writing this stuff out is helping me think through it, but I promise not to take offense if you unsubscribe. In November I plan to get back to actual content, but for the next few days, it's my blog and I need to use it to think!

I've been thinking a lot lately about why creating accessibility outreach materials targeted at bloggers needs to be different than all the great materials that are out there about web accessibility in general. I definitely don't want to be duplicating effort.

Bloggers come in a wide variety of skill levels, from those who still have trouble with sending email to those who are coders and programmers. My guess is that most blogs are maintained by people on the lower end of the technical spectrum. Look at the sheer number of blogs hosted on Blogger, WordPress.com, and LiveJournal. Sure, some of those folks are coders and programmers, but most are not.

Because of this guess, I'd been conceptualizing the information I'm trying to organize as split between "things you can do when you're posting" and "things you can change on your blog overall." So far, so good. However, that line of thinking lumped in a tip like "change your text and background color" with "create skip navigation links" as "things you can change on your blog overall."

Even the most fearful of the content creator bloggers, though, is likely using a publishing tool that makes it fairly easy to change your text and background colors.

And even the hardiest of the content creator bloggers who have learned a little bit about their templates might not get how to properly use headings right away - and headings in posts often require some CSS work.

So I'm going to take a little time and reorganize the tips I've already written and pencil in the ones I think are left. Something like skip navigation links is a great idea for the content creator bloggers who have already gotten their alt text, link text, and color schemes in order, so I'm going to put that near the bottom of the list.

And when bloggers are at the technical level where they want to tackle skip navigation links, I'm pretty sure they can take care of it from one of the existing resources out there - so instead of spending time writing tutorials, I should curate the good ones and link to them.

That will hopefully mean I'm done with writing sooner and can move on to action.

(Except that, of course, TypePad updated itself and now I have to recheck how everything works.)

Allright, y'all, time to confess. When I started this blog, it was not because I wanted to blog about accessibility. There are lots of accessibility blogs. There are lots of GREAT accessibility blogs. Being read by people who already care about accessibility.

What I really want is to reach out to the bloggers who don't already care about accessibility. To do that, though, I felt like I needed to get all my information organized. If I was going to say "hey, you need to make your blog accessible!" then I should be prepared to tell them how, including instructions for their blogging platform. That's what I so appreciated about Dive Into Accessibility.

This blog basically came about as a way for me to make progress in organizing my material. A blog format tugs at your sleeve when you don't work on it for very long. Obviously it's been in fits and starts. Part of that is how long it takes to do each section of the Guide. I think it's about 6-8 hours for each section that includes step-by-steps for the various blogging platforms. I struggle with how to present it in a way that's understandable to non-technical people without dumbing it down. I struggle with what level of support will help people who have never edited HTML or CSS in their lives. It's hard to figure out where to stop - at some point, people will be interested enough in accessibility that they can "graduate" to reading the accessibility blogs I read, which are overwhelmingly targeted at geeks rather than the person who started a blog on Blogger or WordPress.com just because they liked to write.

I've also been feeling stuck because I wasn't sure what to do when I got done.

While I've been away from the blog, though, dealing with a bunch of family issues, a plan has started to percolate. The plan I'm forming, means concentrating on the basics and treating some topics as "extra credit" ideas, because the people I'm interested in reaching are often not very technical. Getting those folks to remove the major accessibility barriers seems like as good a goal as getting a small number of people to push their blogs to the bleeding edge of accessibility.

So my goal is to get the Guide done, meaning usable, by the end of the year. Then I can start 2010 in outreach mode, trying to make the blogosphere more accessible rather than just writing about it.

My question for you, my readers who are already interested in accessibility: if you had to ask people to do just 5 or 6 things, rather than 25 things, what would those things be? Where should people start?

I started this blog a year ago on Blogging Against Disablism Day. I had spoken at BlogHer 2006 about making your blog more accessible to people with disabilities, and I had been invited to speak again in 2007. I was trying to organize what I knew and what I was learning about web accessibility, but then translate it into language that would make sense to the army of non-geek bloggers out there.

Many bloggers are not web developers. Many bloggers are not web designers. Many bloggers are not technical. (That's the great thing about blogging - you don't have to be a computer geek to blog.)

And most importantly, many bloggers are using tools that already do things right.

Before asking people to make sure their blogs meet certain accessibility guidelines, I wanted to take into account what their blog tools already do. For example, sending a blogger to check and make sure their post titles are semantically marked up just seems silly. What blog tool these days doesn't do that for you? Maybe you're just trying to teach people about semantic markup, but I'd rather focus on the problem areas first and ask bloggers to fix those.

So I'm making another attempt to finish writing up a basic set of tips that bloggers can easily use to make their blogs more welcoming to people with disabilities (and those of us who can't read purple text on a black background even with our new contacts in.)

A blog is not the best format for a one-stop shop of this kind. Lucky for me, Movable Type 4.x now has Pages, so I am now organizing the tips into one guide called How To Make Your Blog Accessible. As I publish a new tip in the guide, I'll announce it on the blog. (I may also blog about a few other things in the intersection of blogging and accessibility, such as revisiting Ning.com's CAPTCHA issue to see if they've resolved it.)

Here are the updated versions of the previously published tips. I have tried to make them more compact and user-friendly than their previous incarnations.

• Choose Link Colors With Care
• Fight Comment Spam Without Locking Out Your Readers
• Break Your Posts Into Paragraphs
• Label Your Images
• Stop Mystery Meat Linkification

I'd be very glad to get any feedback or corrections, especially from the accessibility experts out there.

Hopefully, by BlogHer 08, I'll be able to point folks to a complete set of tips. What I found in the past two years is that when bloggers become aware of the issue, they make changes. They may not make all of the changes that I'd like them to, but they do care and they take steps to make their blogs more welcoming. Since the content creator ultimately determines whether a shiny new accessible website stays that way, I think that's very good news.

National Blog Posting Month, known as NaBloPoMo, begins tomorrow. Participants commit to posting every day for the month of November. While I don't think that would work for this blog, I am going to use the month of November to get back in the swing of things here at All Access Blogging. Strangely, having a baby (and pregnancy complications before the baby arrived) got me a little off track!

Thanks to everyone who has subscribed, by feed or email, for sticking around while I get it back up and running. I have some ideas about how to reformat the tips to make them easier to digest, and the release of Movable Type 4 also means more information to cover. Eventually I think the content will be migrated to a wiki for ease of maintenance, but for right now I'm going to stick with the blog format I know and love.

Welcome to NaBloPoMo!

All Access Blogging will be starting up on May 1st, which is also Blogging Against Disablism Day.

No one wakes up in the morning and says "Hmm, how can I make sure that people who are blind can't read my blog?" But some of the choices we make about setting up our blogs and adding content can create barriers for others who want to know what we have to say. This blog will show you how to make changes so that everyone can read your blog.

Do you have to be a programmer to make your blog acessible? NO! Most of these changes are easy to make.

To make it even easier, All Access Blogging will provide instructions for making these changes in the following blogging software:

• Movable Type
• TypePad
• WordPress (self-hosted)
• WordPress.com
• Blogger Beta
• LiveJournal
• Vox

We will also feature interviews, success stories that show how it can be done, and more.

So don't be afraid! Check back here May 1st as All Access Blogging begins, or sign up for our feed now so you won't miss a tip. Or if you're not a "feed" person, sign up for All Access Blogging by email.

If you have any questions, email me. I'm polishing content and prettying up the template right now, but I'd love to hear from you.