[A11ybok] Gap Analysis Process

[bill]

I fully support this:

- "I'd like to propose a process for doing gap analysis for the A11yBOK idea."

- "I'm a big fan of the Delphi Method, so this will be Delphi-like  (see
http://en.wikipedia.org/wiki/Delphi_method)"

Me too. Although it's generally used to solicit and hone the opinions of experts, I think this could result in some good ideas. I suggest that we aim less for accessibility experts, and more for mainstream web developers, ie people who tend to NOT go to CSUN

- "The Rules:
1. Refrain from thinking of this in a W3C/ WAI context.  Don't focus
on what they do/ do not have. Focus on what you think a BOK should
have, irrespective of who supplied it"

Exactly! Envision the 'To Be' state you'd like to see. It's only in the second step ('As-Is') that you want to look at what currently exists:

Gap Analysis = To-Be  minus As-Is

Once the To-Be is sketched, then fleshed, out, step 2 is a kind of environmental scan (what exists), step 3 is the gap analysis, and then step 4 is the prioritized and massaged roadmap for moving forward.

Bravo Karl.

BTW, I've just sent the following tweet from CRODisabilities:

Web Developers: What do you need in an #Accessibility Body of Knowledge? #A11y #WCAG #WAI #Delphi @karlgroves Respond: http://ow.ly/1Izk4P


Cheers

Bill Shackleton

www.twitter.com/CRPDisabilities<http://www.twitter.com/CRPDisabilities>
==================================
"We are called to be architects of the future..
 Not its victims"            R. Buckminster Fuller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://a11ybuzz.com/pipermail/a11ybok_a11ybuzz.com/attachments/20120316/e430694e/attachment.html>