WAI Site Potential New & Revised Content and Illustrations

Version: 2004.08.12
Note: This Web page is a working draft and should not be referenced or quoted under any circumstances.

on this page:

illustrations for Web site and presentations:
table of new pages and notable revisions

Components of Web accessibility illustration

latest version: http://www.w3.org/WAI/EO/Drafts/UCD/components
requirements and changelog: http://www.w3.org/WAI/EO/changelogs/components

Standards harmonization illustration

purpose & use:

illustrate issues surrounding standards harmonization, specifically:
- [@@ issues addressed in Why Standards Harmonization is Essential to Web Accessibility]
for presentations
for WAI site to accompany Why Standards Harmonization is Essential to Web Accessibility

misc thoughts:

probably same style, layout, etc as components illustration
showing lots of demands for features in authoring tools, with lots of small accessibility ones, versus one big accessibility one
...

WCAG1.0 Priorities & Section 508 illustration

purpose and use:

illustrate relationship between WCAG1.0 Priority Checkpoints and Section 508 1194.22 paragraphs. want to show the overlap to help people who want to implement both. also to show the fragmentation.
presentations
WAI Web site (stand alone) ... although, might want to wait to put it on the Web until have more detailed explanation, which might take some time

version 2:

start of an svg version
neither of above work: judy thinks venn makes it look like 508 1194.22 takes best of WCAG. shawn thinks box version would be hard to show overlap.
to venn, add to title "and Section 508 1194.22 Overlap"
put all WCAG checkpoints & 508 paragraphs in the circles or boxes, showing relationship between each. in SVG can zoom out to get big picture and zoom in to get details
note on scale: the size of the circles & boxes is proportional to the number of checkpoints or paragraphs: WCAG 1.0 has 16 P1 checkpoints, 30 P2 checkpoints, 19 P3 checkpoints - and Section 508 1194.22 has 16 paragraphs. the overlap of the circles is approximate: of 16 P1 checkpoints: 11 P1 map very closely to 508 paragraphs, 2 P1 are related to 508 paragraphs, and 4 P1 are not covered at all in 508; 508 roughly overlaps with 4 P2 and 4 P3 checkpoints.
fyi, (note) an early incarnation previous version

W3C Recommendation Track Process

illustrate w3c rec track process, as described in: W3C Process Document 7 W3C Recommendation Track Process

OLD example from old process:

WCAG1.0 Techniques illustration

latest version: http://www.w3.org/WAI/EO/Drafts/sketchpad/wcag-flow
about: http://www.w3.org/WAI/EO/changelogs/overviewpages#wcag-flow

Business case illustration

purpose & use:

catchy illustration to go along with Presenting the Case for Web Accessibility
probably just an animal with three carrots dangling in front and a stick in back. carrots labeled"social factors" "financial factors" "technical factors" and stick labeled"legal and policy factors"
for presentations
- probably also want separate carrot & stick image for decorating individual "slides")
for WAI site to accompany Presenting the Case for Web Accessibility
- maybe interactively expand to more details
- link from carrots and stick to appropriate page of Presenting the Case for Web Accessibility and probably WAI Policy page

misc thoughts:

probably same style as components & standards harmon illustration (perhaps Japanese anime! or perhaps black & white "scratchboard")

Web page with things labelled

illustration to jump off to "tutorial" - that is, a Web page with an image, a data table, a form, a frame, etc. that links to directions for making each accessible

WCAG2.0 Principles illustration (LOW priority)

accompanying graphic for WCAG2.0 principles (Perceivable, Operable, Understandable, Robust)
not sure what this would look like, just some nice little thing to have for presentations ..

WCAG1.0 Priorities illustration (LOW priority)

accompanying graphic for Priorities, just some nice little thing to have ...

Table of new pages and notable revisions [old version]

page	priority	effort	notes
home page (major revision)	required		redesign & rewrite content
intro & navigation pages (new)	required		e.g., probably replace http://www.w3.org/WAI/Resources/ and add maybe 1-5 of them intro to web accessibility - includes "components" [listed below] nav pages to resources? guidelines & techniques? etc. intro pages for WCAG [maybe same as listed below], UAAG, ATAG, [maybe technologies], WAI groups About WAI is an "intro page" [listed below]
Introduction to Web Accessibility (new)	high	high	illustrated one page overview. (not sure how relates to illustrations above and to Getting Started page?)
getting started page (rewrite)	high	medium	probably munge with Intro Web Accessibility. redesign to be more user-task-based rather than document-based. include more specific direction.
Components of Web Accessibility (new)	high		probably within Intro to Web Accessibility. page with textual explanation to go along with Components illustration above (wish list interactive graphic showing authoring tools, user agents, assistive technologies, content developers users,... and probably link to the guidelines)
"cover page"s for /TR/ docs (new)	high?	medium-high	we can't change or add anything to the "TR" pages, which are the guidelines, techniques, and such. cover pages would provide WAI site navigation and basic introduction before dumping users into the technical docs. might also help w/ searching issues
QuickTips page (major revision)	high?	medium	change this to also be an interactive intro for Web content accessibility, e.g., link each item to the appropriate details in WCAG
About WAI page (revision)	medium		restructure & rewrite to be more user-task-centric and less organization centric dependency: will require heavy input from Judy
Using WCAG 1.0, Checklist, Techniques (new)	medium		page with textual explanation to go along with WCAG illustration above
Intro page to online overview slide show (new)	medium	easy little approval	(mostly moving content from the first slides explaining how to use it to a "regular" web page and including easy download instructions (probably just link to all.htm)
Curriculum (revise interface to)	medium		@@move out of this list, EOWG deliverable@@ especially the examples not sure how this falls under WSTF versus curriculum interface design...
overall FAQ (new?)	medium	high	@@move out of this list, EOWG deliverable@@ mostly pulling from other docs; however, likely to need lots of review and approval
[Why Web Accessibility ? or Benefits of ? or ?] ( new)	low		page with textual explanation to go along with Components illustration above (wish list graphic showing three carrots & a stick, labeled & linking to pages in Presenting the Case for Web Accessibility resource suite and Policies relating to Web accessibility)
...

See also: Features matrix which includes things such as search

Retiring Pages

Calendar of conferences - very outdated. do not link from redesigned site. possibly revive in future, but not in foreseeable]

Document Information

@@ to do: check acronym tags, HTML & access check & validation

Editor: Shawn Lawton Henry. Last updated $Date: 2005/03/24 01:29:54 $ by $Author: shawn $

Copyright © 1994-2003 W3C ^® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.