I normally keep my work life separate from my personal life, which for me, includes my blog. While I love my job and take pride in my work, it’s not my entire life. But I digress – the reason I mention this at all is to say that, for once, it’s time for me to talk about work on my blog.
I work as a Digital Products Assistant at The MIT Press. I’ve been there about a year now, and I still have to explain to everyone (including people I work with) what my job actually entails – which is, in a word, ebooks. I convert them from print book formats (using some basic HTML/XML and CSS coding), send them out to vendors (like Amazon, so you can read them on your Kindle), and spend the rest of my time figuring out what to do when things go wrong. That last one takes up about 60% of my work day.
Anyway, recently I’ve become interested in another aspect of publishing that no one understands: accessibility. It’s closely tied to ebooks, in that people are asking how we, as publishers, can make our digital content accessible to those who can’t read our print books. As you might expect, it’s not a simple question. In addition to trying to educate my coworkers at the Press, I’ve been trying to learn the basics of this myself.
And somehow, because of my interest in accessibility, I now have the opportunity to lead a workshop at ebookcraft, a conference held annually in Toronto specifically for ebook developers (like me). This is completely terrifying, but also amazing (but mostly terrifying, if I’m being honest). Luckily I have the support of my entire department, my friends and family, and one of my peers at Michigan Publishing, who is much more experienced and wise than I am.
One of the best things about me being so interested in learning about accessibility is that I have the opportunity to share information with others who feel just as lost as I did not too long ago. Recently I wrote a blog post about some of the basics of accessibility in publishing, and if you’re curious, you can read it here.