Author Archives: karlgroves

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 […]

(re) Announcing A11yBuzz.com

On July 30, 2011 I posted My Challenge to the Accessibility Community: We Need an Accessibility Body of Knowledge in which I lamented: The fact that there is no single source to get good, clear, peer-reviewed information on this topic is, in my opinion, a very huge barrier which prevents “outsiders” from participating in accessible […]

One. Simple. Question. (and a follow-up)

Several weeks ago, Bryan Garaventa made a post to the WAI-IG mailing list. The email thread went somewhat sideways, because some list members didn’t “get it” but it died down quickly enough. AccessIQ reignited the issue, wondering “…do web accessibility professionals have a sense of humour?” My response? Clearly the answer is NO. Even when […]

Longdesc – Where are the alternatives?

Non-text Content is “any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language”. Mostly what comes to mind when discussing non-text content are audio/ video content, images, or other graphical content not necessarily image-based. WCAG 1.1.1 Calls for alternatives for […]

Feature misuse !== feature uselessness

Ugh. Longdesc. For those who don’t follow such things, the fight over the longdesc attribute in HTML5 goes back to (at least) 2008. Back then, the WHATWG was also considering eliminating the alt attribute, the summary attribute, and table headers. Ian Hickson’s blatant and laughable egotism led him to believe he knew more about accessibility […]