Introduction
Rian has worked on accessible WordPress themes and plugins like the accessible Twitter to WordPress plugin used on this site available on her GitHub repository. She is available @RianRietveld she offers WordPress and web development services at RRWD Web Development. When I asked her some questions, Rian replied: “I answered the questions twice, serious and not serious, you pick the answers you need.” So I leave it to you to pick the answers you prefer to read.
Shoe Size?
My shoe size is 9.5 American size, 40 European size. (Maybe time for standards for shoe sizes too?)
Alternate answer: Ha, great! A girl can never have enough shoes. These please: Dune Pump Calm.
Pride?
The most rewarding of the accessibility work is the response and gratitude I get from disabled web users. I’m proud to contribute to a more accessible internet.
Alternate answer: Proud of the fact that after a few posts I’m bombarded with questions of users who think I’m the one to ask for basic WordPress advice and solve all their problems for free.
Biggest Challenge?
The single most challenging aspect is getting a grip on the complexity of it all. Solving problems in HTML/CSS/PHP/Javascript for all the different browsers and assistive technology and all different kinds of disabilities. Hard like proper programming for Internet Explorer version 6, times 100.
Alternate answer: Trying to overcome my shyness, to discuss and disagree with people that know way more than I (well, actually, that’s a serious answer too.)
Change Most Needed?
I think with the Make WordPress Accessible group things are going into a good direction. But the main problem is the lack of knowledge with programmers. So… education, information and a few essential guidelines for plugin/theme developers in the codex?
Alternate answer: Plugin and theme developers should be required to show their work to their mother or grandmother, maybe then they’d discover, for example, that a grey site with grey characters is pretty hard to read when you’re older.