An accessibility checklist by Aaron Cannon:
Accessibility checklist via cameronmoll.com

An article on A List Apart:

“ Three techniques for incorporating data visualization into standards-based navigation patterns.”

Accessible Data Visualization

On 456 Berea St.:

7 accessibility mistakes

Interesting articles on web accessibility, validation and the button tag:

• False accessibility claims
• CSS Validator colour warnings
• Push my button

The Internet, in theory, enables anyone from anywhere to access information. In reality all the people with dial-up connections are cut out of a lot of it. I know that in the States and Europe almost everybody has some kind of high speed connection but the rest of the world is still using dial-ups. I'm not a professional of the web but I like it because it has brought more freedom to people, more opportunities to learn.
Podcasts, videocasts,screencasts: there should always be a text version that can be downloaded by everyone.

On UXmatters: label placement in forms

“ Excessive distances between some labels and their input fields forced users unnecessarily to take more time to interact visually with the form.”

based on Luke Wroblewski's article

On Digital Web Magazine: accessible widgets for the web

When building web applications, we're working with a fairly restricted set of widgets, compared to those available for native desktop apps. The recent surge of interest in JavaScript points to a solution: we can replicate the functionality of sophisticated native widgets through some clever DOM scripting, and provide our users with exciting interfaces that bridge the gap between native apps and web apps.

On Friendly Bit: 4 tier web development

I think of the 4 tiers as content, structure, presentation and behaviour. Almost the same. The content (or data) and the structure go together since, usually, there is (for example) a title that should be placed into a <h1> tag, chapters into <h2> etc. When it all looks readable without presentation then I add the design, using CSS. I don't like to add tags to accomodate design, I try to use only the tags necessary to the structure. The last layer (behaviour) should be unobtrusive, which basically means that is not mixed up with the structure but sits in an external file. I removed all inline Javascript calls after reading
separating behaviour and structure in 2004. The point of all this is just to build a site easy to update and apply changes to.

On 456 Berea St. :
AJAX, JavaScript support and screen reader accessibility

On Quirksmode:
IE 7 and JavaScript

Accessites.org "will prove that accessible, usable websites built with universality and standards in mind need not be boring. We will show you stunning works of art crafted by some of today’s most progressive accessible web developers and designers. Join us in honoring them and the sites they meticulously and lovingly build"

Via Web-graphics: nifty corners by Alessandro Fulciniti

Yahoo's site explorer "allows you to explore all the web pages indexed by Yahoo! Search"

An essential guide to understanding and using
Web Content Accessibility Guidelines 2.0

On Digital Web: seven accessibility mistakes - part 2
link to the first part

On Digital Web: seven accessibility mistakes - part 1

Also, it's now possible to download a pre-release software of Internet Explorer 7 : Beta 2

On A List Apart:

Getting abbreviations right

“ Designing for accessibility is not just a technical endeavour like most other pursuits on the web, it involves creative problem solving and experimentation”

simplyaccessible.org

WCAG 2.0 documents via Access Matters

An interesting article on And All That Malarkey about creating color palettes and links to two more:

• Color palette tool
• CSS colors: take control using PHP