- Similar posts for '508':
- Accessibility in Video Games - Physical
- Writing - Thoughts once done
- Accessibility: Look at What's Out!
- Accessibility in Video Games - Hearing
- Accessibility: Video Games
- Similar posts for 'writing':
- What is a tech reader?
- Katie writes: Kids Code!
- What I learned from NaNoWriMo 2013
- Writing and Mental Health
- 11/18/14 - Katie learns Angular.js
- 11/17/14 - Teaching Python in your PJ's
- 11/10/14 - Why not self-publish?
- 8/22/14 - My return to Pokemon
- 8/18/14 - What is a tech reader?
- 7/14/14 - Flask + git: Easiest workshop ever
- 7/8/14 - Katie writes: Kids Code!
- 2/7/14 - Rune Factory 4: *What* romance options?
- 12/31/13 - Looking back, looking forward
- 12/11/13 - Your wiki is a dump
A light in the dark!
20 January 2012
So, things went sort of dark on this blog, didn't they? It's for a good cause, I assure you. I'm writing a book.
Okay, you've probably heard that before. I know I have. I've had to sit through the elevator pitches for someone's cyber-steam-anti-punk novel-no-wait-graphic-novel opus many a time. This is a real book, though, with a contract and EVERYTHING.
Sadly, it's not about a cyber-steam-anti-punk heroine with pluck and nerve and awesome boots. I'll get around to that book, one day. What my book is about is accessibility and 508 compliance. Long story short, '508' refers to a US Federal law mandating that all applications and websites created for the Federal government be accessible to all people, in spite of their disability. Short story even shorter: All the stuff for all the people.
It's a topic that I was dropped into when I started working on a government contract, and found that meeting 508 was causing our applications to be delayed over and over. It was easier just to learn it and do it right the first time. The more I learned about it, the more fascinating I found it to be, though, and I found myself picking over other open source projects and getting irritated that more people couldn't make accessible websites.
I don't plan on letting the blog go fallow until May, when the book is due, but I will be racheting down the posting to a comfortable "When I can get to it" pace. On the upside, I do plan on writing about writing, to hopefully encourage more of you out there to join me in writing tech books. The world needs more tech books that focus on teaching (a blog post is coming up about how we learn), because we do the next generation of developers a disservice when we insist that they can just bounce around on the Internet to pick up what they need. We also do ourselves a disservice, because you know we'll end up having to fix their crap code.