Accessibility doesn’t have to be scary
Maybe you’re aware of accessibility and its benefit to everyone. You think it’s an excellent idea and you’d love to incorporate it into your projects and workflow. But you don’t know where to begin. It seems overwhelming. There’s too much information and you feel like your brain’s going to explode.
Start with an accessibility audit
The first step toward making your Genesis child theme accessible is to perform an accessibility audit. An audit will give you an idea of where the problems are along with appropriate references to web standards, as well as suggestions for fixing them. You could run your theme through an automated testing tool, but because of the nature of automated tools, there’s a lot that will be missed. So the best option is to perform a manual audit.
But what if I don’t know how to do a manual audit?
Don’t worry if you don’t know how to do an accessibility audit of your theme. That’s why I’m here.
Accessibility has been part of my workflow ever since I started developing for the web in 1998. I’ve also worked for the leading screen reader manufacturer, Freedom Scientific, in a support role which included everything from helping users install Jaws and get their settings configured to helping web and application developers ensure that their products were accessible. And I’ve been developing with WordPress and the Genesis framework for a long time.
OK, so how much is this going to cost me and what do I get?
I like to be straight with people, and I believe in transparent pricing that is based on the value you receive as a client and not an hourly rate. So I’ll give you the price first, and then explain what that includes.
An accessibility audit of a Genesis child theme costs $1500 U.S., and includes all of the following:
- Initial testing with all major screen readers: (Jaws for Windows, Window Eyes, System Access, Dolphin, and VoiceOver).
- A report, in Microsoft Word or PDF format, which contains all accessibility problems, where they are likely coming from, (the child theme itself or the framework or WordPress), applicable references to the WCAG2.0 standard, commentary on how screen reader users will interpret what they’re interacting with, and suggestions on how to repair the problems.
- A separate spreadsheet with the problems, the references, and the suggested fixes.
- Another separate file with code examples
- An hour of support so you can ask questions about your audit or about how to implement the suggested changes
- A future cost savings of at least $100,000 because you’ll be able to avoid remediation later on.
What if I have questions before I decide to buy an audit?
If you have any questions before you make a decision to purchase an audit, please feel free to call me at (615) 669-7036, or use the form below to send me a message.