In my previous article on the topic of accessibility I outlined a number of do’s and don’ts in regards to coding and design. Accessibility issues don’t start and end there and those advocating FOR accessibility can often be their own worst enemy.
Probably one of the biggest issues is the…
A friend of mine used to joke that
HTML is already responsive. Designers are the ones screwing that over.
It’s a strange notion, but mostly correct. If you write vanilla HTML with proper semantic markup, flow and natural wrapping behaviors give you a page that is at least USABLE on…
Now, just a word of warning, you've got a lot of problems I'm about to explain to you. …
I’ve had a number of folks recently ask my opinion of the “Pure” CSS framework, as if my answer isn’t obvious given my opinion of ALL front-end frameworks. …
Of why HTML / CSS Frameworks just recreate everything wrong with HTML 3.2!
I was browsing “Tailwind Components” looking for some examples, two or three simple ones to do rewrites of, when I hit the motherload. …
In my constant belittling of the laughably inane dunderheaded chazerei known as CSS Frameworks, one thing that respondents — even those who don’t like my bashing their favorite pet media darlings — seem to like is the rewrites.
They not only clearly illustrate why idiocy like Tailwind are incompetent crap…
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…
