Author Archives: karlgroves

What happens when you get sued for your inaccessible website

In the United States, the primary motivator for paying attention to accessibility seems to be risk avoidance. While I’d personally rather see people work to make their ICT systems more accessible because they believe in Universal Usability, litigation (or threats thereof) is what truly gets the discussion (and budget) moving for accessibility. Some argue that […]

Five Lessons Learned from the IEP Process

May was a really big month for the Groves family. We got our county school system to agree to place our daughter in a non-public school to address her unique educational needs. She’s never been happier and more enthusiastic about school, which I largely attribute to a combination of better atmosphere and finally feeling like she […]

My testimony at the CSUN 2015 Access Board Hearing: Make Haste

My name is Karl Groves. I’ve been involved in Web Development, Usability, and Accessibility since the late 1990s. Living in the Washington DC area, and working in accessibility my professional career in this field has always involved Section 508. In 2006 I was excited to hear about the Refresh process. As a web developer, the […]

18 Years in: The basics still matter

I got into web development in the late 90s. By that time, the Web Accessibility Initiative was well on its way to trying to make the web more accessible. In that time we’ve seen the rise (and fall) of many new technologies on the web and many new devices used to consume and create web […]

To Hell With Compliance

A few weeks ago, Asa and I added a page to Tenon’s documentation that lists What Tenon Tests in reaction to questions about “How much WCAG coverage” Tenon has. I had already covered, at a high level at least, what can be tested and how quite a while ago and, while Tenon only tests a […]

You don’t have accessibility problems, you have quality problems

On my site and on Twitter, I try to exude positivity and pragmatism. I try to tone down my admittedly strong personality as a way to ensure that what I write is well received. Sometimes I succeed. For the most part I tend to frown upon random bitch sessions about how bad everything is on […]

Ridiculously easy trick for keyboard accessibility

One of the more frustrating things about accessibility is how ridiculously easy most things are to do. While most developers tend to see accessibility as nebulous and time consuming, the truth is some of the most impactful issues are actually easy to deal with. As a case-in-point: consider simple keyboard accessibility for custom controls otherwise […]

The no-CURL way to submit a request to Tenon API

A few months ago, I posted Tutorial: Creating a PHP class to use with Tenon.io. Someone asked me “What about servers that don’t have CURL? Here you go. Use the class in that post, but swap out the submit() function for this: function submit(){ $content = http_build_query($this->opts); $options = array( ‘http’ => array( ‘method’ => […]

This one secret will save you $100,000 on accessibility

I’ve historically been very critical of the various Business Case arguments for accessibility given their lack of actual evidence. There’s one business case argument that I think is rock solid: The cost of remediation. The cost of remediation actually has two faces: The actual time-on-task it takes to fix issues, of course, but also the […]

The form field validation trick they don’t want you to know

Yes, that was a purposefully click-bait headline. One of the most frustrating things for users is unclear or unintuitive form constraints. My personal pet peeve are phone number, credit card, or SSN/ EIN fields which ask for numeric-only entry. While it may very well be necessary that your field use only numeric data, you don’t […]