Change log: Planning a Web Accessibility Training
This page records change requests and changes made to sequential versions
of the WAI Resource Planning Web Accessibility
Training. Please send additions or corrections to [mail list to be created:
wai-eo-editors@w3.org; for now use
w3c-wai-eo@w3.org. Last updated 24
March, 2002 jbrewer@w3.org
Change requests from 24 March 2002
-
brainstorming about tutorials & templates
-
wcag techniques -- being updated, modular, able to be linked to
-
mock up page w/ explanation behind it
-
page of links w/ short info that goes out to different types of info, plug
and play examples, best practices examples, etc.,
-
drop in on a faq, w/ buttons saying "simpler" or "more technical" -- allows
them to adjust the level of answer they are looking for
-
if all in central database, can draw out, easier to maintain
-
include ud perspective somewhere
-
think about what can link to from html document as well, multiple means of
navigation
-
think how designers think, especially when they are just getting started
-
help developers figure out how to use their own tools accessibly
-
extract summaries as a start
-
ensure peer review of the materials
-
think about how to link to external materials that relate to our goals
-
template=fish, implementations of accessible code; tutorial=how to fish
-
having a way to sort the material to better match the intent of the user
-
eowg: keep figure out how to help people find the right info & tools,
better examine the user needs,
-
[ertwg dev aert, going on more in wcag now... so we also need to look at
getting people to the eval resources]
-
[tutorials great idea, can be done little piece by little piece]
-
[look at examples on ibm site, think about blank templates, useful]
-
templates mainly addressing the issue of navigability and orientation...
does not make it comprehensible for people... perceivability not well
reflected...
-
think about the audiences of whole-page templates as including those who
commission the design...contextual examples can do that...
-
template: eowg should name the fish.
-
plug and play page (less important)
-
page that drives delivery of content (industry's resp)
-
general guideline for critical formating (explanation) (eowg)
-
eowg operating as requ gathering arm, wcag how to arm.....
-
template: a framework into which you plug code, vs sample code, what you
plug in
-
don't hijack words, doesn't work
-
existence proofs, important to have
-
...bobby learning tool... eowg should look at it
-
-
http://www.w3.org/WAI/EO/Drafts/training/ra.html
-
broaden up the impact in #1, aging, etc., device independence, electric fences
etc. [OR and its impact on everyone including pwd]: start w/ clear focus
on people w/ disabilities -- and then expand it to include aging etc., and
carry-over benefits to other situations.
-
http://www.w3.org/WAI/training/ra
-
#4designing: update links to WCAG modules [LP & AG looking at those resources
to compare against the newer modules]
-
#4designing: replace link to selecting software
-
#5evaluating: point to how to evaluate for web accessibility, separate pointers
to prelim & comprehensive
-
consider adding in intros & advanced -- let people decide -- hurdle?
red flag? (text)
-
tutorial modules
wishlist.... what if we made little tutorial modules about the most
intractable design problems, take a design problem from top to toe (these
are ideas generated from EOWG discussion 02/22):
-
how to design tabbed-like navigation
-
how to design client-side image maps
-
how to design drop-down list box menus
-
how to design cascading or fly-out menus
-
how to design multicolumn layouts
-
how to design frame alternatives
-
how to design effective cross-platform css-based page layout
-
alt text demystified
-
how to design data tables with navigation aids
-
mathml in design
-
how to set up keyboard shortcuts or to expose standards
-
specifying page measurements
-
setting up an accessible forms & communicating on validations errors
-
http://www.w3.org/WAI/training/ra
-
really important to get the web page & digital format of WSTW up &
electronically available *during first quarter 2002*
-
and to edit out the inaccurate table part in WSTW
-
update the mention of pwwebspeak if possible
-
update the overview of wai & make sure links to individual slides still
work
-
add (self, friends, relatives) to prior experience qu
-
consider linking to Trace resource on Web accessibility navigation w/ Neal
Ewers, and/or negotiating for co-hosting other demonstration that would be
relevant
-
check out anamolous text decoration colors on links
-
link to aux benefits...
-
add in a discussion question under business case: "do you use pda's, do you
access the internet through wireless technologies, how do you think it can
be applicable?" (and link to explanation of why!!)
-
add in discussion question, "are you trying to reach audiences w/ low literacy
and/or second language access needs" (and link to explanation of why!!)
-
add link to selecting and using using authoring tools
-
check techniques links
-
LATER: add link to before & after under "designing"
-
LATER: add lnk to demographics
-
#2, link to preliminary review.
-
-
Rename demonstration, presentation, etc.
-
on curric page, change subst expertise at top to familiarity
-
lighten up the comment abt mats still in draft stage
-
3-day & 5-day unnecessary to mention on the page; but include in review
request
-
add: encourage these materials to be used and to give feedback on the outlines
-
eliminate redundancies
-
under heading, change heterogeneous to mixed
-
(consider, based also on additional feedback we get, adding more info on
presenter requirements (of & for presenter) for each sample curriculum)
-
example 4: shorten barriers part of outline, fix the other times, make it
clearer that selected scenarios vary according to technology discussed
-
example 5: add "ATAG... and discussing how to build these into their product
development specifications"
-
example 5: after introducing ATAG, add a discussion about the extent to which
the product specification encourage or omit ATAG-type provisions
-
example 2: finish linking resources in example 2
-
example 3: add "for example" before lynx emulator (and of course complete
the link to the emulator)
-
example 3: also add turn off graphics
-
revise nav bars: further differentiate ext nav, suite nav, internal nav --
ext nav upper right/ suite nav inverted, right, and still above header/ int
nav left, under header (important to do that skipnav)
-
on overview page: remove overview from title AND swap planning for first
link in suite nav AND make suite nav a nav box w/ title "Web Xs tr" at top
of box.
-
RETEST Fragment anchors from curriculum page are broken and performing oddly.
(Added .html before # mark, helped some, but still getting weird results.)
-
DONE Clean up outlines for each example.
-
DONE Add & link highlighted learning objectives for each curriculum outline.
-
DONE For example #3 (designers)
-
make it a hands-on workshop, for 20 people, all online
-
bring up an inaccessible site in Jaws, look at & listen to it OR show
people site in Lynx or Lynx-me
-
ask them to navigate that site with keyboard only (throw their mice over
the back of the desk)
-
introduce them to guidelines
-
show them examples of sites that do/don't implement those guidelines
-
ask them to correct the site the first site that they saw, ensuring some
basic comfort level by teaching remediation in the tools that some people
are using OR ask them to design an accessible Web site together from scratch,
perhaps with some pre-prepared content that you provide.
-
put things here that _aren't_ covered in other sample curricula
-
DONE Try adding a miniToc up front
-
DONE The order on the page makes no sense. Re-order examples.
-
DONE Recheck warning levels for the whole page: do this only with proper
experience, etc.
-
FIXED The logos don't line up right in some browser versions.
-
FIXED The Overview page no longer matches what's in the rest of the resource
suite.
-
DONE Add "primary" before learning objectives
-
DONE Move up the qualifier "heterogeneous audience - general awareness" to
the H2 element (not consensed, but try)
-
DONE Fix "minutes" on first example (they don't add up).
-
DONE Add "myth-debunking" into 20-minute general example.
-
DONE Add "business case doc" as an OR under second point in 20-minute example.
-
DONE flip the order of header content, so that topic comes before time span.
General comments
-
DONE Ensure that the training resource suite will be usable by people who
aren't experienced trainers, for example people who have a primarily technical
focus, or people who are managers and want to purchase or arrange for certain
kinds of training.
-
DONE Flip the order of the curriculum modules (put them before) and the
approaches (put after, as choices to fill out modules), within the overall
training resource suite.
-
DONE (DID THIS ON CURRIC PAGE INSTEAD) On "approaches" page (rename "modules")
add estimated times, or ranges of times, for each module.
-
DONE Nav bar names could now include: overview, objectives, curricula, modules,
tips, setup.
-
DONE If we use the term curriculum, emphasize that these are suggestions
that should be taken flexibly.
Comments on "Perspectives" page (which splits into "curricula" page and "tips"
page)
-
DONE For 2nd example, add motivators for Web accessibility, including
usability//Business Case, and go over top ten myths about Web accessibility
-
DONE Add tip: Julie Howell, RNIB: I always start with a scenario -- a real
one, something really hard-hitting, that shows unnecessary discrimination
-- for example, how is it that a blind person living in this one authority
can find any info he needs from the Web, how to take his kids to the park,
etc., and someone close by in another town can't find any of this information?
-
DONE Add tip: Julie Howell, RNIB: I like to make the presentation topical,
by refering to something going on in the news at the time, e.g. the news
item in the UK about the dot com bubble burst, for instance when Boo.com
failed, we turned this into a usability "consult your users" story.
-
DONE Add tip: Chuck Letourneau, Starling Access Services: I always look at
the local framework within which Web accessibility is being addressed. So,
for instance, I'd start by telling them what the policy requirements are
that apply to Web sites in their areas.
-
DONE Add tip: Helle Bjarno, DCVI: Why Web access is an issue. use an intro,
things happening in global society
-
DONE Overall, emphasize that you should tailor/customize your own presentation
to meet the needs of your own specific audience
-
DONE For current first example, at 1.1, add "according to local context"
-
DONE For a twenty-minute example:
-
show sections (for instance the first three minutes) of video that show asst
tech (3) or briefly discuss a scenario or two
-
motivator // different levels of motivation... (3) demogr, ud, local policy
-
quick run through before/after demo (3)
-
introduce themes and points Quick Tips OR Checklist (2)
-
brief mention of how to check sites/ use several tools (3)
-
introduce diff w3c/wai resources (how are developed; variety for diff needs)
(2 min)
-
DONE For an inserted module into a full-semester course
-
advance reading:
-
how pwd use the Web
-
(when done) business case
-
wcag guidelines
-
atag guidelines
-
during session:
-
whole WSTW video & questions etc
-
more discusion of motivators
-
introduce online curriculum for wcag & use the checkpoint layer with
links to techniques and example layer, including the multimedia einstein/car
example
-
go through the 14 guidelines
-
give them a badly designed Web site and have them fix it
-
get together, look over each others' work, discuss it
-
discuss how different auth tools facilitate or hinder production of accessible
content
-
introduce accessibility checkers and approaches
-
introduce other W3C/WAI resources including techniques
-
give them the quick tips card
-
homework afterwards:
-
follow-up work on site redesign using checklist
-
go fix their own Web sites or find one of their own choice to fix
-
DONE for a session on implementing accessibility in an existing authoring
tool (audience may include programmers and QA specialists)
-
how pwd use the Web
-
show some assistive technologies in action
-
(when done) business case
-
WSTW video
-
wcag guidelines
-
show end users' perspectives, the discrimination that they are encountering
on sites designed with other tools
-
show users of their tools
-
show several accessibility checkers in action
-
discuss conformance testing suite for authoring tools
-
have them through away their mice OR other experiential things
-
go through atag guidelines/principles/checklist of checkpoints
-
dwell on ones that are problematic
-
cover advanced techniques if relevant to particular type of authoring tool,
e.g. SMIL features if multimedia tool; SVG if an SVG player; MathML if
relevant...
-
DONE for a 10-minute senior management briefing (with timing to the minute)
-
you are called on in a meeting that you were invited to
-
before & after demo (1)
-
policy overview (2)
-
wave around the quick tips (1)
-
demographics & carry-over benefits (1)
-
run a multimedia demo for 1.5 min to blow away dull/boring myth
-
implementation plan (1)
-
myths (1)
-
Q/A (1)
-
TIPS: don't dwell on problems, dwell on solutions, and point to resources
-
(all-singing all-dancing vs... )
-
point to resources (just say that they are available)
-
NOT [ADDED NOTE "MAY ADD LATER"] add a full week (five day)
In general
-
Add skipnav (via 1px gif) before logo links
-
Try inverting foreground/background colors on "present" "demo" "discuss"
etc. BUT ONLY IF NO DISPLAY CONFLICT
-
NOT--NO CONCEPTUALLY EASY WAY ON THIS PAGE Implement access key within page
suite.
-
NOT-- CHANGE TO PRESENTAION Explain what "present" is.
-
DONE Make extnavbar float at upper right corner of the page
-
DONE Take off "training" at front of navbar
-
DONE Change "arranging" to _something_ else. Maybe "setup"?
-
DONE Be consistent about adding an introductory sentence or two to each page.
-
DONE Consistently link a whole verb/noun phrase from the first page.
-
DONE Strip off light blue background from resource text & links on
"approaches" page.
-
DONE Try light blue background on the word "resource" itself (only).
-
DONE Take background color off of intnavbar.
-
DONE Remove backlink to EOWG home & add one to WAI Resources.
-
DONE Remove "draft" notes at bottom.
-
DONE Add EOWG credit on all.
-
DONE Fix body width.
Last updated 30 January, 2002 by Judy Brewer
(jbrewer@w3.org)
EOWG Home