EOWG Home
Change log: Getting Started: Making a Web Site Accessible
This page records change requests and changes made to sequential versions
of the WAI Resource Getting Started: Making
a Web Site Accessible. 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 5
October 2001 by Judy Brewer
(jbrewer@w3.org)
-
flip language codes around, and re-test
-
remove individual language names from top of page, and set up a translation
page
-
go back through other WAI translation page and clean them up, make them more
consistent
-
recheck the language code question for denmark -- should be da not dk --
unless en-us etc
-
add title attribute w/ info about translation links
-
fix broken link to technical questions section
-
PURSUE a way to notify people that they're about to land on old material
(wrt to curric)
-
Henk will do Dutch version
-
Sylvie and Jean-Marie will do French version
-
add lang= in HTML markup itself
-
fix broken links on evaluation section
Comments are on draft at:
http://www.w3.org/WAI/EO/Drafts/gettingstarted.html
-
**JB do all changes by night of 29 Sept & then notify Helle & Sylvie
(placeholder for DK & FR translation)
-
PURSUE comment to translations folks that untranslated doc names are weird...
-
PURSUE get more of wai translations on general w3c translations pages
-
PURSUE add w3c translations link to standard wai nav div
-
PURSUE advocate for inclusion of ready link to translation resources throughout
w3c site
-
PURSUE add links to translation by using proper language name in own language,
followed by English
-
PURSUE medium term develop a publicly visible technical assistance list to
point to; periodically organize the responses on that into a loose rolling
faq
-
PURSUE recommend updated design for conformance page
-
DONE develop a sub-section on wai contacts page
http://www.w3.org/WAI/contacts.html
providing more detail on how to get tech help
-
DONE try to remove a few more of the redundancies in language
-
DONE try to reduce a few of the listings, so the page is not so overwhelming
-
DONE put in a direct link to the example page in the curriculum
http://www.w3.org/WAI/wcag-curric/oversam.htm
-
DONE move online overview down to additional resources
-
DONE take example index from curric and put it right under quick tips
-
DONE remove w3c search link if continues to be broken
-
DONE An initial introduction to resources for people new to Web accessibility.
-
DONE move out guidelines to lower down
-
DONE flip quick review & evaluation overview
-
DONE fix missing class on techniques link
-
DONE clear up first acronym link to wcag
-
DONE throw out the link to the software guidelines
-
DONE don't point people to the archives (or point people to there as the
last place)
-
DONE change "technical questions" to a link under additional resources
-
DONE additional resources: prune it down to guidelines, tech assistance,
wai online overview, wai resources
NOTE: Changes below were incorporated into new draft at
http://www.w3.org/WAI/EO/Drafts/gettingstarted.html
-
NOT change header to "what wai documents are translated"
-
NOT change question to "is there an accessibility logo?"
-
PURSUE review and update FAQ for WCAG
-
PURSUE recommend logo collection page under QA activity
-
DONE wrt FAQ, change phrase to "introduces guidelines"
-
DONE move FAQ to before checklist
-
DONE add a reference to ATAG FAQ as well as ATAG
-
DONE add reference to existing tools list under how to build
-
DONE add more information about what they'll find when they go to the review
page
-
DONE clean up presentation: regularize types of phrases and places resources
in a more predictable location in the phrases
-
DONE put scannable keywords at beginning of phrases
-
DONE keep phrases
-
DONE provide some kind of brief introduction at top
-
DONE try grouping the content more cleanly, but don't eliminate all the subheads
-
DONE lead in to quick tips should be clearer or moved
-
DONE translated versions -- should reference translations of this document
-- also, translation availability should be listed at the top
-
DONE add note about translation availability of this document under the header,
once available
-
DONE to add contextual links to available collections of translations of
other resources that are mentioned
-
DONE to eliminate question about translations
-
DONE add link to wai ig for technical questions// emphasize public// archived//
joining page
-
DONE annotated resource listing
-
DONE if drop question format, and use key words, would say on words, e.g.
"more about wai" instead of "how can i learn more about wai"
-
DONE be more cautious in pointing to logo -- need to be compliant
-
- set up a tickler log for related changes
-
ROUGHLY DONE try setting off some of the resources in a box or boxes, without
listing every resource that we have
-
ROUGHLY DONE batch one: pwd, checklist, faq; batch two: prelim eval; batch
three: guidelines + curric
-
DONE change WCAG to WCAG 1.0
-
DONE keep it simple
-
DONE pointers to other info (eventually point implementation plan)
-
DONE improve the headers
-
DONE clean up the reference to authoring tools, and move it up the list
-
DONE add a pointer to translations page
-
DONE point first to the checklist, then the faq, then guidelines
-
DONE try setting up some introductory "if's" e.g. if you're not familiar
w/ pwd use of Web, go to... it is helpful to get an initial understanding
of the requirements
-
DONE change wording under eval to do a prelim review and point them to the
relevant section
-
DONE add resource nav bar
Last updated 21 September, 2001 by Judy Brewer
(jbrewer@w3.org)