Regrets wit comments on QT: EOWG: Components & WAI guidelines cards

The main reason developers have problems with WCAG 2.0 is because it is 
user centered not technology centered.  I remember my first reading 
thinking, "That's good but what do I do with tables?".  The Sufficient 
Techniques have tables, forms, frames, titles, labels and any other 
thing you could want. 

I will be writing a web page based on the guidelines that links to the 
techniques via a plain English description of the success criteria.  A 
pull-back page might also be interesting.  For example start with 
"table" and pull back isolated the techniques that pertain to tables and 
then pull back to guidelines via success criteria.  (The categories 
could be compatible with WCAG 1.0 or US Section 508).  I've done the map 
from 508, but my article is currently unreadable.

Just as the guidelines quick tips are grouped by the POUR layer.  The 
techniques card could be grouped by Object layers == Tables, Lists, 
(Headings, labels and Titles), Navigation, Scripting / Objects, Non-Text 
static and time-based media.

The Techniques card might be a transitional card form technology 
centered to user centered.  The principles could be the permanent. 

When I first read the 2.0 I was lost because my technology handles were 
gone.  Now I think adaptable Guideline 1 means - semantic structure 
which means tables, lists, headers...

This isn't just out of my imagination.  I have trained about 200 web 
developers over the past two years, and know what bothers them.  They 
like detail and categories.  We are changing their categories and we 
need to give them easy mnemonics to the old details.  Developers are 
comfortable with technical details changing, but they resist a new 
categorization.  The nice thing about 2.0 is the categories are based on 
human physical needs.  They change about as fast as natural selection. 

How many sets of cards do we make. 2 at first.  Principles and Techniques.
The principles don't change for a long time.  The techniques change 
frequently.

About other cards.  When I leaned c there was a card from ATT.  I threw 
out my manual and just used my cheat card.  Cheat card are always good.  
We can easily make accessible versions.  So a ARIA, MOBILE, Accessible 
Math cheat card might be perfect.  We can make as many as demand permits.

Lets start wit the first two.  First principles, second techniques.  
Let's do it quick.  We don't have to be prefect.  These are memory 
joggers.  The Guidelines and Techniques speak for themselves.

Sorry, I have to miss tonorrow.  This is my last official duty as the 
Academic Technology Accessibility Coordinator.  I'm back to plain Wayne, 
computer geek.



Wayne

Received on Friday, 6 June 2008 02:06:51 UTC