The Web should be made accessible to as many people as possible, regardless of any disabilities they might have.
When you use an icon or other graphic instead of text for buttons, make sure there is real text for users who cannot see the image.
How to use CSS only to customise radio buttons and checkboxes.
It can be useful to know if images are enabled in the browser, so that you can adjust your CSS and JS to make sure that the page is still usable even if images aren’t loaded.
Using a select element for navigation in narrow viewports is not an ideal solution. Here is an alternative technique that uses real links and is fully stylable.
If you want to hide visible content only from screen readers in order to give users a better experience, aria-hidden may be an option.
CSS generated content is announced in some - but not all - screen readers, so use with care.
When using the HTML5 sectioning elements, make sure the document outline created by the headings is backwards compatible.
The placeholder attribute is meant to give the user a nonessential hint before filling in a form field, not replace the label element.
In page links do not work as expected (or as in other browsers) when activated by keyboard in WebKit browsers like Safari and Chrome.
Some CSS intended for visual media types only has unexpected and semantic effects on screen readers.
A way of styling the closed state of select elements without sacrificing accessibility.
The number of people browsing the web without Flash Player installed is non-negligible, so if you use Flash it is worth your time to give them a better impression.
When you use the table-related display properties of CSS to get the display properties of a table, some screen readers will treat the non-table markup as a real table.
Many developers expect screen readers to ignore visual styling of semantic HTML elements. They mostly do, but with list items their behaviour is hit-or-miss.
HTML5 allows links to contain block level elements instead of just inline elements. This can be useful but there are currently potential usability issues with screen readers.
Hiding content with display:none hides it from all users, including those who use screen readers. Be aware of this when deciding how to hide content visually.
A quick walkthrough of the accessibility improvements in Mac OS X 10.7 Lion that stood out most to me.
In this brief and easy-to-read book, Aaron Gustafson does an excellent job of explaining what progressive enhancement is and how to apply it in your daily work.