It's always kind of pathetically tragic when articles like this get posted, given the blatant mistakes in both design and semantics that tell large swaths of users -- particularly those with accessibility needs -- to go f*** themselves.

Illegible colour contrasts, broken non-semantic markup, gibberish use of numbered headings, static image inlined doing H1 + plaintext's (along with CSS image replacement's) job, DIV doing HEADER, MAIN, and FOOTER's job, BUTTON likely doing Anchor's job unless you're going to go further down the rabbit hole of "F*** accessibility" with full-on script-tardery, pixel metric declarations telling non-standard font metric users to suck it, fixed heights on elements that should be controlled by flow, failing to leverage condensed properties, presentational classes (well... class) dragging things back to the worst of 1990's development...

And this is why nubes and rubes alike get suckered into thinking they can make websites.


Warning, this article is both meant to be educational, and to vent. It may repeat things I have said in previous articles, and I’m going to keep repeating it unto you folks get it. You have a problem with repetition or “harsh language”, please just GTFO now. …


The WCAG — Web Content Accessibility Guidelines — is a complex convoluted bit of legalese reeking of “design by committee”. Despite being the jumping off point for nearly every law worldwide on the topic of web accessibility, the language of said guidelines is a barrier of entry for “normal people”…


And how I landed on the “Aventure”. No, that’s not a typo.

Back in 2008 I was in dire straights physically. As a programmer / web developer / electronics tinkerer I spent WAY too much time eating garbage and sitting on my arse. I’m only 5'4" tall and had ballooned…


Honestly most all of your examples reek of everything wrong with people half-understanding functional programming and turning it into a hot WET mess.

Much less not knowing how to polyfill properly. Take your AJAX example with the functions for nothing, variables for nothing, IIFE/SIF for nothing, etc, etc. …


Sadly, I think in this article you are being painfully naive about human nature. The sheer ignorance of Trump's base -- the same people, ALL OF THEM -- who put him in office in the first place has them yumming this shit up. …


Honestly, you sound like a lot of educators I've talked to the past ten years who have been packed full of nonsense by an industry filled with people running their mouths about things they don't understand. Sorry if that sounds harsh, but it's the truth of it. …


— edit / addendum—
And laugh being the joker I was responding to banned me from replying or reading their posts. Because of course once you start posting facts that contradict their ignorance, they have to use “but it’s your tone” as an EXCUSE to maintain the echo chamber. The…


For some time we’ve seen the rise of chaining methods and responses together. jQuery started the trend, and now with things like promises it’s risen to new heights of popularity… but to be brutally frank, it’s all such mind-numbingly overcomplicated nonsense!

Garbage that’s only further compromised code clarity and increased…


I’m preparing a quote for an potential client and they have a laundry list of complaints and issues they’ve been saddled with by their former IT director. I’ve been doing accessibility and efficiency consulting for ten years, and really what’s “wrong” with their site is nothing out of the ordinary.

Jason Knight

Accessibility and Efficiency Consultant, Web Developer, Musician, and just general pain in the arse

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store