I changed my WordPress blog, danielgreene.com, to the Mystique theme. I love it! It has this widget on the top with links to my RSS feed, Facebook Page, Twitter profile, Flickr photostream, and YouTube channel. It has a combo widget on the right that shows recent comments, top posts, archives, tag cloud, and category lists. And it uses a beautiful font that has true italics. I like!
Blog Archives
I love my new blog theme!
The truth on interpreters for deaf at WordCamp Phoenix 2011
I was “the interpreter” who offered to coordinate interpreters for WordCamp Phoenix 2011. I wish I could remain silent, but the blog post I’m responding to has been viewed almost 900 times already and has already been sanctioned by a famous deaf blogger who I believe would think otherwise if he read my side of the story. So, before anyone else is misled, allow me to set the record straight.
I first spoke with Amanda, the conference organizer, on Thursday afternoon, January 14, and offered to interpret and coordinate. She told me the budget was $2,000 for a four–track conference which would need a maximum of eight interpreters. I figured I could get four professional interpreters to earn $50 an hour, get four students to volunteer their services pro bono, and that would still leave $400, half of which might go toward compensating me for coordinating services, and half of which might go toward gift cards for students.
That same night, I found out that Amanda had un–registered a deaf registrant because she didn’t like her attitude. I advocated for the ousted registrant, emailing Amanda, “Deaf people routinely face discrimination and have to fight for their rights. In light of this, I find the registrant’s demands assertive rather than aggressive.” I even followed this up another day and asked Amanda if she would please consider reinstating her. Amanda was immovable.
I should mention that the first deaf registrant had approached me around Thanksgiving about interpreting for WordCamp. I had said I would be interested and asked him to send me more information, but the holidays came and went before I saw an announcement from Amanda on the Arizona RID Yahoo Group. I knew how important it was for this deaf person to attend WordCamp, so I decided to provide for him even though I was not happy with Amanda’s handling of the other deaf registrant.
By the end of the week, I had offers from two other professionals and at least four other students. At this point, all I needed was one more professional if (and that’s a big “if”) there were deaf attendees in all four tracks on Saturday. Read the rest of this entry
Organizer’s attitude toward deaf, interpreters defeats her
The blog post “How Trying to Provide Deaf Interpreters for a Camp Bit Me in the Ass” paints the conference organizer as the victim, but I’m afraid it was her attitude toward interpreters and the deaf that defeated her, and it is the interpreting profession and deaf consumers that stand to lose by her misrepresentation.
I would hate for the takeaway message from any blog post to be, “Don’t provide interpreters to the deaf if you can possibly avoid it.”
Edmund Berke once said, “Those who don’t know history are destined to repeat it.” Take a look at John Pozadzides’ 2009 blog post “An Open-Source Look at the Cost of WordCamp Dallas” and the comments that ensue when someone suggests “If you cut out the T-shirts and interpreters, you would break even.” You will learn a lot about complying with the ADA and providing accessibility to a public event.
I hope these two bits of history will help people make future events better for all.
Edited January 22, 2011 for clarity.
Why I chose the Coraline theme & the Eaglefeather font
WordPress Blog Theme
The WordPress Coraline theme came out the other day, and I like it because:
- It has a “Leave a comment” link that can’t be missed. The one in the Twenty Ten theme is hard to find. I want to engage readers in conversation, and a loud “Leave a comment” or “# comments” link grants them easy entry.
- It allows for a body, feature bar, and two sidebars beneath the feature bar. This means I can feature my latest tweets. And knowing that whatever I tweet will be featured prominently on my blog might give me pause before I tweet while drunk. Not that I would ever do that!
- Like the Twenty Ten theme and the Kubrick theme before it, it allows me to have a banner image, which I think it is fun.
- I can use the right sidebar to feature my latest Flickr photos on par with my categories, tag cloud, etc. in the left sidebar.
Typekit Web Fonts
I’m also using Typekit to stylize my blog with a Frank Lloyd Wright–inspiredfont. I chose this font because: Read the rest of this entry
The Typekit Fonts Tutorial for WordPress.com (via United Stage)
For those who are in their TypeKit Editor and just want to know the CSS selectors used in the Twenty Ten theme, I am sharing this list compiled by David W. Boles. Thank you very much, David!
content, body, p, h3#comments-title, h3#reply-title, #access .menu, #access div.menu ul, #cancel-comment-reply-link, .form-allowed-tags, #site-info, #site-title, #wp-calendar, .comment-meta, .comment-body tr th, .comment-body thead th, .entry-content label, .entry-content tr th, .entry-content thead th, .entry-meta, .entry-title, .entry-utility, #respond label, .navigation, .page-title, .pingback p, .reply, .widget-title, .wp-caption-text, input[type="submit"], #access .menu-header, div.menu, #colophon, #branding, #main, #wrapper, blockquote, blockquote cite, blockquote em, blockquote i, body, input, textarea, .page-title span, .pingback a.url, h1, h2, h3, h4, h5, h6
via United Stage
