Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


Difference between revisions of "Main Page"

From Education & Outreach
Jump to: navigation, search
(Archive:)
(Misc:)
Line 85: Line 85:
 
* [[UAAG review]]
 
* [[UAAG review]]
 
* [[ATAG review]]
 
* [[ATAG review]]
 
==Misc:==
 
* [[alt guidance]]
 
* [[Procurement Resources]] to be seeded on WAI-Engage Community Group wiki
 
* [[WAI-ARIA Overview]]
 
* [[Situational terminology]]
 
* [[Easy DD]]
 
* [[WAI in the community]]
 
* [[Liaisons with WPDocs, CGs, etc]]
 
* [[Resource update & SEO]]
 
* [[RD Symposia Design]]
 
* [[WCAG basic]] - short summaries of requirements
 
* [[mugs]]
 
* [[Style]]
 
* [[WAI Website Redesign]]
 
* [[Letter about Easy Checks]]
 
  
 
==Archive:==
 
==Archive:==

Revision as of 18:12, 5 June 2014

EOWG wiki

See the W3C WAI Education and Outreach Working Group EOWG home page for information about EOWG and our work.

Main Things

wiki & github stuff:

WAI-ACT

Training related

Promotion and Outreach:

Document updates:

Evaluation pages:

Technical Document Review

Notes:

  • EOWG review of technical documents should focus on understandability, approachability, and ease-of-use. Look at the introduction, abstract, background, use cases, and other such sections. You can usually skip the technical sections.
  • Make sure the Overview page is linked early in the Introduction and in the Abstract, as appropriate.
  • Have a pretty high "filter" — that is, we usually will comment only on significant issues and not bother with minor things.
  • Remember these are technical specifications/standards and have a different audience, format, and purpose that EO docs.
  • (If you have comments on technical aspects beyond the education & outreach perspective, please submit them yourself.)
  • Please write your comments as we would submit them as formal EOWG comments to the public-comments list.
    • Clearly indicate where in the document your comment applies. Provide a link to where it is in the document.
    • Briefly describe the issue.
    • Provide suggestion for revision. (EOWG can help refine this, but please provide a draft.)
    • See EOWG - Comment effectiveness e-mail
    • (Optionally, you can include additional notes for EOWG consideration or discussion.)

Reviews:

Archive: