Recap: The web accessibility basics

Today, I am just quickly going to recommend you an old, but all-time reader favorite post of mine I published 4 years ago. And it is as current today as it was then, and most of it already was in the year 2000. Yes, I’m talking about the basics of web accessibility.

tagged with: #A11y, #Css, #Html, #Webdev

Call to action: HTML needs more native rich widgets

Over the weekend, this post by Dave Rupert made the rounds, and I totally agree with what he is saying.

tagged with: #A11y, #Accordion, #Html, #Webdev, #Widgets

The web accessibility basics

I’ve been asked again and again over the years what the absolute basics of web accessibility are. And while I always thought that it is not so difficult to find resources about these basics, the recurrence of that question prompted me to finally write my own take on this topic. So here it is, my list of absolute web accessibility basics every web developer should know about.

tagged with: #Alttext, #Colorcontrast, #Formlabeling, #Graphics, #Html, #Htmlaccessibility, #Wcag, #Websemantics, #Webstandards

A follow up to my Easy ARIA tip

Community member Ben Millard has pointed out in a recent blog post that roughly the same as shown in my example can be achieved using regular HTML 4 by embedding the input into the label. Thanks for that info, Ben! It is very useful and shows that some of the techniques that have been available for years escape even us gurus sometimes. But then, we don’t dig through every W3C doc on a regular basis, either.

tagged with: #Firefox, #Html

Easy ARIA tip #2: aria-labelledby and aria-describedby

Sorry it took me so long to get back to it, but here it is, my second tip on the usage of some easy ARIA markup to make your sites more accessible.

tagged with: #Aria-describedby, #Aria-labelledby, #Attribute, #Html

Easy ARIA Tip #1: Using aria-required

Inspired by a conversation I had with Aaron the other day, I’m starting a mini series about easy accessibility improvements you can accomplish using ARIA, but which do not require you to implement a whole widget. Some ARIA attributes also work on plain old standard HTML elements and can easily improve accessibility within supported browsers and screen readers. On browsers that do not support these attributes (yet), they are ignored and do not break your page just because that attribute is there.

tagged with: #Aria-required, #Attributes, #Html