Analysis/Requirements and Changelog for [Web Accessibility Training]

Latest [Draft] Web Accessibility Training
Related page: Changelog for How to Make Presentations Accessible to All with Analysis/Requirements
~~Previous WAI resource: Planning Web Accessibility Training (changelog 2002)~~

Page Contents

Purpose
Audience
Approach
Notes and Open Issues
References & Resources
Changes
Making your presentations accessible

To Do

List of things to add/change to Topics resources when they are completed:

Business Case slides
Using WCAG 2.0 slides
Developing Websites for Older People
Relationship Between Web Accessibility and Usability
@@

Purpose

From WAI-AGE Project Deliverables:

Abstract: This resource suite includes suggested training syllabi and training resources relating to Web accessibility.
Proposal: Update the content and revise the text of the existing training resource suite to enable it to be used as a more effective resource for people interested in promoting awareness of the need for accessibility for older Web users.

Goal:

A resource to help people prepare web accessibility presentations and training in both technical and business-oriented situations.

Purpose:

Provide guidance for people new to web accessibility to make presentations
Provide guidance about topics and resources for people providing training on web accessibility
Provide suggestions and resources for people making presentations about web accessibility
Provide guidance on which WAI resources to use in different presentation and training situations
Ensure older web users are included in presenters and trainers considerations
Help people understand how to share their knowledge and experience

Audience and Messages

Primary audience

from anyone (technical or non-technical) to anyone (technical or non-technical), including:
- people wanting to suggest accessibility to their organization
- advocates for accessibility
- people providing technical web accessibility training
- people providing web accessibility awareness
- people educating decision makers about investments and policies
Example 5 (3 day hands-on workshop for content authors and web developers) is different from Examples 1-4 in that it requires a presenter knowledgeable in web accessibility. It might also be used to seek proposals for web accessibility training. As a result the later sections dealing with preparing accessible web content and developing accessible websites, have been written at a higher level to give the presenter guidance without being prescriptive, and to provide the presenter with flexibility to prepare material according to the audience needs. (EOWG 15/Mar/2010)
See also audience for Making your presentations accessible

Secondary audience:

people looking for self-study opportunities about web accessibility

Topic audiences:

everyone
web developers
web designers
web managers
website owners
accessibility advocates
web policy makers
ICT departments
procurement personnel
project managers
accessibility experts

Approach

Proposed outline:

Inviting overview/introduction that speaks to a broad audience, including
- what's inside
- how to use
How to prepare presentations and training, including
- pre-preparation (incl consideration of the audience needs)
- preparing the training (incl selecting topics to cover & logistics)
- during the training (incl being aware of people who may be unable to see or hear the presentation)
- after the training (as appropriate - follow-up, homework, resources)
- NB - just consider things that are particular to Web Accessibility and/or PWD
Collection of training topics/modules that can be mixed and matched. These topics are what someone would speak about as a presentation, or as a section of a larger training session; frameworks for building a presentation from. Based on previous material, plus some new topics:
- Current Topics (Jan 2010)
  - Introducing Accessibility
  - Guidelines and Techniques
  - Managing Accessibility
    - Business Case for Web Accessibility
    - Improving the Accessibility of Existing Websites [to be developed]
    - Involving Users in Web Projects
    - Web Accessibility and Older People [to be developed]
    - Accessibility and the Mobile Web [to be developed]
    - Web Accessibility Policy and Legislation [to be developed]
  - Evaluating Accessibility
    - Quick Check for Web Accessibility [to be developed]
    - Detailed Check for Web Accessibility [to be developed]
- Previous Topics (from 2000) with notes
  - Why Web accessibility is important (what is web accessibility)
  - Barriers, assistive technologies, and alternative access strategies
  - Business case and policy basis for accessible Web design
  - Designing accessible Web sites
    - Split into WCAG 2 Intro; WCAG 2 Migration; WCAG 2 Design
    - consider modularising Designing with scripting, ARIA, multimedia, etc
      [http://www.w3.org/2010/01/08-eo-minutes.html#action08]
    - value of good semantic markup -> Designing (@@ covered by WCAG 2.0 GL discussion?)
      [http://www.w3.org/2010/01/08-eo-minutes.html#action10]
  - Evaluating (and retrofitting) Web sites for accessibility
  - Designing accessible browsers and authoring tools
    - Split into Browsers and Authoring Tools as separate topics
  - Promoting Web accessibility
  - Finding additional resources on Web accessibility
  - Inter-relationship of the three WAI guidelines in achieving accessibility (based on essential components; draft slides) [new]
  - Involving Users (based on Involving Users in: Web Projects & Evaluation) [new]
- other topics?
  - See wish list below
Hypothetical presentation scenarios/curricula/examples of training
- Previous examples:
- Suggested examples:
  1. Web Accessibility for Management (adapt)
    - 10 minutes presentation
    - senior management
  2. Introducing Web Accessibility (adapt)
    - 20 minutes presentation
    - audience could be heterogeneous [non-technical/technical, managers/owners, users/advocates]
  3. Accessibility from a Users Perspective (new)
    - 1 hour presentation
    - non-technical users & advocates
    - includes adaptive strategies; what a good site should have; initial testing; contacting
  4. Accessibility for Web Design Students (adapt)
    - 2 hour lecture as part of web design course
    - college/university students
    - intro; components; WCAG; evaluation
    - adapt from current example
  5. Accessible Website Development (new)
    - 3 day hands-on workshop
    - website developers (no prior knowledge assumed)
    - intro; how PWD use; bus case; components PLUS hands-on WCAG 2.0 based around site components like semantics, forms, tables, CSS, etc; PLUS evaluation, and inroduction to ARIA and ATAG
- Other possible Examples:
  1. Accessibility Introduction for Web Developers (3 hour hands-on workshop)
    - 3 hour hands-on workshop
    - web developers (familiar with basics of web accessibility)
    - introduction and practical guidance and resources
    - demonstrations and activities - WCAG & evaluation
    - adapt from old example
      [old outline: Accessible Web design - Web designers - three-hour hands-on workshop]
  2. Writing Accessible Web Content / Accessible copy writing (1 day interactive workshop) [new]
    - for website content writers & developers (no prior knowledge assumed) and for CMS users who don't know 'pointy brackets';
    - includes [intro; how PWD use; bus case]; appropriate interpreted WCAG 2.0 material (e.g. semantics, colour, contrast, multimedia, links, tables, etc etc); initial eval techniques
    - see also notes from Alan and Suzette to WAI-AGE about this Example as a Topic
  3. Purchasing an Accessible Website (1 hour presentation) [new]
    - for website managers/owners & purchasers/procurers;
    - includes intro, business case & authoring tools) [needs material we don't have]
  4. Web Accessibility for Usability Professionals (1-day hands-on) draft started by Shawn
    - for people with usability/user-centered design training and experience, who are new to accessibility
    - 1-day hands-on workshop titled, "Integrating Accessibility into Usability Practice"
    - provide participants with the knowledge and resources to successfully include participants with disabilities throughout user-centered design (UCD), especially in evaluation and usability testing
- Some other ideas from EOWG 5/Feb/2010 and TF 10/Feb/2010 and EO 12/Feb/2010:
  - how to make successful accessible forms (including accessibility and selling stuff)
  - accessibility features of operating systems and browsers (for users; for developers)
  - advocacy aspects of what you do with authoring tools and browsers, and meeting ATAG/UAAG. (Include the topic of components for web accessibility)
  - website evaluation workshop (possibly develop when EO refreshes the Evaluation suite) - HIGH EO PRIORITY
  - accessible email
  - accessible social media
  - accessible video
  - intro to Scripting with WAI-ARIA
  - overlap with mobile web design
  - accessibility & older users
  - using assistive technology for web developer
  - web accessibility and accessibility advocacy

Notes and Open Issues

Open issues - September 2010

Address Questions in Topics to be sure there is guidance about the answers and ensuing discussion
Minor copy-edits pending
Recheck all WAI reference links, especially those that use .php extensions

Notes

Make audiences aware of web accessibility as a people-related issue, not just a technical activity
- people with disabilities and older people
- disability can happen anytime / we're all getting older
Role of all three guidelines in achieving accessibility
Broader benefits of accessibility beyond people with disabilities
Breadth of WAI resources
Topics to capture: introducing web accessibility; developing policy; developing websites; evaluating websites;
Coverage is technical and business aspects
- People looking for how to use accessible websites should be directed to Better Web Browsing (draft)
Value of involving PWD and older people in training (or at least videos of users)
Touch on future devices/directions - stargazing/razzle-dazzle - future research/investigation opportunities and accessibility [http://www.w3.org/2010/01/08-eo-minutes.html#action11] (see also WAI-AGE research opportunities)

Wish List

Potential New Topics:
- Accessibility for Content Editors/Authors/Writers
  [http://www.w3.org/2010/01/13-waiage-minutes.html#item03; Alan Chuter & Suzette Keith]
- Selecting Accessible Authoring Tools and CMS's
  [http://www.w3.org/2010/01/13-waiage-minutes.html#item03]
- Benefits of WCAG 2 presentation (just incorporate in other topics as per EO 22-Jan-10)
- New Topic Category - User Perspective related stuff (when added to WAI navigation)
Provide sample answers for the Questions included as suggestions to presenters (see Ian Pouncy's WBS suggestion)
Consider adding icon to indicate technical reports as appropriate

Open issues - May 2010

Is a 'starter' resource still required?
What are the current needs of our audience?
Is the scope of 'short presentations' through to 'full-day training' still appropriate?
Do we expect the resource primarily to (from existing Overview and Curricula pages) ...
- be used by experienced trainers?
- with expertise in W3C's Web accessibility solutions"?
What connection do we make with accessibility of non-W3C web technologies from Adobe, Microsoft, etc?
How do we address the Curriculum on Web Content Accessibility Guidelines that was developed in 2000?
Could we develop a matrix or filter (a la Eval Tools) to help people select materials depending on their interests?

References & Resources

WAI-AGE task force and EOWG Discussions:

Internal references

WAI-AGE Project Deliverables: Web Accessibility Training Resource Suite
- Rationale: It is currently significantly outdated, but has the potential to be useful in supporting training efforts by organizations interested in providing training on Web accessibility, whether they be user organizations or developers, as the scope of possible training objectives and linked training materials is potentially broad.
Existing WAI resource Overview: Planning Web Accessibility Training [2000]
- lots of internal resources linked from this suite - will all need checking
- Previous Changelog for Planning a Web Accessibility Training
  - consider 2002 change requests
WAI Presentations pages
BAD - Before and After Demo site [Draft]
- A multi-page resource from W3C that shows examples of Web accessibility on a realistic website.
Web Accessibility for Usability Professionals (1-day hands-on workshop) draft started by Shawn
And most other WAI resources!

External Resources (curriculum & tutorials)

Opera Web Standards Curriculum
- A series of articles/tutorials to promote the use of web standards, accessibility or user-centric design. Accessibility seems to have been generally taken into account, and there are some specific Accessibility units. There are also a few that could be improved (e.g. LongDesc). Each article concludes with a series of questions to test understanding (e.g. for accessibility basics & navigation menus). Also includes a Glossary of Terms.
Design for All for eInclusion - DfA@eInclusion NB. developed within the European Design for All eAccessibility Network (EDeAN)
- Dissemination
- Deliverables, including "Exemplary Training Modules on eAccessability for industry training (PDF)"
- Middlesex University Digital Inclusion Masters - "focuses on the social and ethical issues and the technological aspects of ensuring equality of access to ICT and the benefits from using ICT"
WaSP interactive Curriculum
- Twelve accessibility modules provide "a foundation in designing accessible web sites, which apply Universal Design concepts to accommodate individuals with visual, auditory, speech, motor control, and cognitive disabilities". Includes a series of discussion questions and examination questions.
Accessibility Institute (Uni Texas) - closed on August 29, 2008
- How-to's and Demos plus the Art of ALT (online lessons)
Web Accessibility Evaluation Curriculum (Support-EAM, 2006)
- "The objective of this curriculum is to provide a unified training resource for Web Accessibility evaluators who want to do evaluation of websites against an evaluation methodology that has been harmonised at a European level and in the context of Web Accessibility certification." WCAG 1.0 based.
Dive Into Accessibility
- 30 days to a more accessible web site by Mark Pilgrim (2002) - see Table of contents for a list of the topics. Getting a little dated but still some good sections such as Using real headers.
Implementation Guidelines for Web-Based Information and Applications 1.0
- 2-day hands-on workshop is designed for web content developers to learn how to use web standards to create web resources that are more accessible to everyone. Inlcudes WCAG 1.0, WCAG 2.0, S508, usability. (Dept Human Services, Illinois)
Introduction to Designing Accessible Websites
- 8 session online course from HTML Writers Guild
Complete Web Accessibility Suite
- CD-based course from WebAIM
Online Courses
- WCAG 2.0 Tutorial - "reviews the entire set of guidelines, offers suggestions on creating web sites which conform to these guidelines, and shows ways to determine if a web site is conformant with the guidelines" (Tom Babinszki, 2009)
- Understanding Web Accessibility - Certificate Course is aimed at Web content developers (ATRC and others)
- Web Accessibility Tutorial - Section 508 based, but good material otherwise (Jim Thatcher)
- Guide to Web Accessibility - CD based instructional materials, plus examples, simulations, videos, and other accessibility resources (WebAIM) [NB: pre WCAG 2.0]
Demo videos
- One Thumb to Rule Them All - YouTube (assistiveware, 2007) - demonstrates gaming with just a thumb switch
- Refreshable Braille and the Web (Roger Hudson, 2009)
- Web Sites that Work (WAI/RNIB, too old)
- Various videos on Yahoo and YouTube, etc
- Videos of How People with Disabilities use ICT (UIAccess)
- ... and many more
Presentation tips
- Delivering presentations, Prepare great slide decks & Additional Tips (Chris Heilman)
- Better Beginnings: how to start a presentation (Creating Passionate Users blog)
- Creation of Learning Materials (TechDis)
- Accessibility potential of presentation software (TechDis)
- Accessible Presentation Techniques (TechDis)
- Documentation checklist - accessible documents in Microsoft® Powerpoint (IBM)
- Handouts -See it Right (RNIB)
Additional accessibility tutorials - see Tutorials below

Change Requests and Edit Notes

Notes:

See References section above for links to meeting minutes and e-mail input
See also the changelog for "Making your presentations accessible" below

Changed August 2012

Topics

Migrating to WCAG2 section - first bullet under "what this topic covers" - "Accessibility is fundamentally still the same - the basic goals of accessibility have not changed" reworded to "Acknowledgement that the basic goals of web accessibility have not changed"
WAI-ARIA section - additional bullet: "Reminder that HTML 5 does not make WAI ARIA redundant"

Workshop

Added cautionary note at start about experience of presenter:
"These materials are meant to give structure to your own accessibility knowledge and help you to teach others. They are meant to be used freely, with acknowledgement of the source. You may adapt them as needed. If you are the "accidental accessibility expert" and are new to accessibility yourself, however, you are wise to prepare.
It is important and valuable to your colleagues and communities to share accessibility information. Understand your own level of knowledge and remember that no one knows everything about accessibility. While you will certainly want to become very familiar with the materials you are presenting, you are likely to have certain areas where your expertise is stronger than others. If you are unsure of some concepts or techniques, you may want to seek support on the WAI Interest Group list or one of the other related community groups. Be very open with your audience about your background and level of expertise. You are sure to get questions and requests for more information as you present these materials and it is fine to admit when you don't know the answer. In fact, a question that you do NOT know the answer to is often a great opportunity to explore additional WAI Resources with your audience."

{wording needs to be confirmed after 17 Aug EO meeting discusses}
Important Notes section under 'additional notes for presenters':

add an additional bullet: "Draw illustrative examples from sites and material that are relevant to the participants backgrounds, e.g. government, commerce, etc."
expand second bullet with "Seek feedback at the end of each day and adjust remaining material as appropriate."

Changed late September 2010

most issues raised from August 2010 survey addressed - some held over to EO consideration 2012 (see above)

Changed 16 September

Presentations
- Removed inline links to references in outlines (archived inline links version of Presentations)
Workshop
- Removed inline links to references in sample session outlines (archived inline links version of Workshop)
- Added new sub-section with specific links to Understanding and Techniques instead as needed
- Added more guidance to the "Important Notes" section about the experience needed to present the material and about customizing the workshop for the audience
Topics
- Updated links and considered editorial suggestions from EOWG August Survey
- 'Suggestions for Speakers' dropped for Topic 4 (Promoting Web Accessibility)
  - consider adding some back in in later versions
Overview
- Considered considered editorial suggestions from EOWG August Survey

Changed 20 August

Considered and accommodated some of Jennifer Sutton's editorial feedback for 2nd EOWG Survey

Changed 17 August

Additional editorial and presentational changes for 2nd EOWG Survey

11 August 2009

Considered Feedback from EOWG - see EOWG Review: Training Resource Suite (May 2010)
added reference to Creative Commons licence and Attribution Requirements
Topics:
- Clarified that these are just building blocks, with resources, to get started with
- Reorganized topics as Goal, Description, What this topic covers, Resources for developing the topic, Tips for speaker
- Resources includes Primary resources, Additional resources, Handouts
- Tips includes Demonstrations, Activities, Discussion points, etc
Presentations:
- Table presentation dropped in favor of indented lists
- Reorganized as Scenario, Notes, Audience outcomes, Sample outline
- Sample Outline includes Topic link at top level bullet
Workshop:
- Clarified instructions that this needs adaptation and the development of slides and activities
- Sessions condensed and restructured as Audience, Objectives, Outline, Related topics

3 May 2009

Replaced old Training Suite with new (draft) Training Suite at http://www.w3.org/WAI/training/
Incorporated actions from EOWG 30 April 2010:
- DONE - updated titles and H1s
- DONE - reverted to the term "topics" rather than "modules"
- DONE - updated the navigation terms
- DONE - accommodated EO discussion regarding workshop session names
- DONE - adjusted 'target audience' for workshop
- OPEN - skim EO minutes for suggestions not recorded as actions (some done - recheck for others)

27 April 2009

Split Example Presentations and Example Workshop into separate files
Refined structure of Example Workshop:
- Overview; Schedule; Sessions; Notes
- Sessions - audience; objectives; outline; related modules
- Tightened session objectives and outlines

23 April 2009

Examples - Example 5
- restructured in line with WAI-AGE TF discussion (21 April)

20 April 2009

Examples
- Example 5 technical topics split and expanded in line with Eg.5 Agenda
- Questions:
  - should the session about Managing Web Accessibility (Day 3 - Session 5) be moved to Day 1 morning?
  - should the recap Session at the end of Day 2 be fitted in after a reduced Session 6 (site navigation)?
  - hands-on exercise suggestions required for some technical sessions

15 April 2009

Examples
- restructured Examples 5 with learning objectives, a sample agenda, and sample session outlines
- target audience clarified
- learning objectives written for workshop overall (by audience) and also for each session
- sessions dissagregated further with what was "accessibly design and development"
- links back to Eg5 agenda (which links to sessions) added for internal navigation
Overview
- condensed in line with TF discussion from April 7

29 March 2009

Examples
- rearranged and reformatted Eg.5 reflecting TF 24 March 2010 suggestion to swap column order and rename columns
- Incorporated actions from EOWG 26 March 2010:
  - DONE - all Egs.: upgraded "See the followingTopics for resources, notes, and other details:" to H3s
  - DONE - Eg.5: changed name
  - DONE - Eg.5: add note that a follow up session may be required for content authors
  - DONE - Eg.5: for Day 2/3, break table into modular rows and add time weightings
  - DONE - Eg.5: change 'attendees' to 'target audience' to leave participation more open
  - DONE - Eg.5: added a mini table of contents for guidance to readers
  - Drafted an Agenda for Eg.5 to indicate coverage and timing 'in brief'
Overview
- updated to reflect Topics and Examples
- linked to How to make your presentations accessible (draft)

22 March 2009

Examples
- refined Example 5 outline and condensed the learning objectives

17 March 2009

Examples
- updated all examples to be Topic-based rather than Learning-based
- Incorporated actions from EOWG 12 March 2010 related to Example 5:
  - DONE - higher level of outline than in other examples as Eg.5 will be presented by people who know about accessibility, but are looking for what might be appropriate to include, and will also be used by workshop procurers who are seeking information on what might be included
  - DONE - specify that certain groups would (not might) attend certain sections
  - DONE - break table outline up to clearly indicate the audiences
  - DONE - mix and match concepts, tools, eval, techniques, and practice thoughout
  - DONE - drop ATAG (or just metion) and play down ARIA (introduce and give resources to follow up)

10 March 2009

Tips
- Incorporated prevous tips (as appropriate) into Topics 'tips and suggestions'
- Will point to WAI's Advice for Presenters on the presentations page until we develop a dedicated page for this
- Dropped Tips (prep.html) from navigation
Examples
- Refined 3-day example somewhat; tightened other examples
- Ensuring Examples and Topics have matching material
- Started changing Outline presentation from Learnings to Topics structure (TF 10 March 2010)
Topics
- Reviewed Resources and condensed
- Reviewed handouts

3 March 2009

Topics (with assistance from Sharron 24/Feb)
- Sharpened 'description', 'audience will learn' and 'key points for speaker' sections
- Reformated Goal and Audience
- Added 'questions for audience' in some Topics
- Refined references
Examples
- trialled various presentation formats for the Outline with feedback from EOWG and WAI-AGE

23 February 2009

Examples
- Outline format options separated for consideration (scenarios-tf.html), inlcuding trialling grouping the outline bullets under headings from 'the audience will' or 'learning objectives' EOWG 19 Feb 2010
- Outline format options removed from Examples file for content clarity
- Example 5 enhanced

22 February 2009

Examples
- [open] Consider grouping outline bullets under headings from 'the audience will' or 'learning objectives' EOWG 19 Feb 2010
  Tried with Example #3 for discussion [in scenarios-tf.html]
- [DONE] check wording of "see details in topics" (EO 12/Feb notes) -> "See resources, notes, and other details in these Topics" EOWG 19 Feb 2010
- [DONE] present topic links as list under subsection of 'audience will' EOWG 19 Feb 2010
- [DONE] drop 'presentation' from EG names (1-3) & use style 3 with "()" instead of "-" EOWG 19 Feb 2010
- [open] consider the organisation of the outlines with DL and multiple DDs (needs testing) EOWG 19 Feb 2010
  awaiting testing results; Wayne's testing suggests this may not suit all text-to-speech users

17 February 2009

Examples
- Outlines drafted for first four Examples and different presentation formats considered (<OL>, <DL>, <TABLE>)
- [DONE] short presentations not to have formal learning objectives but some 'what the audience will learn' drawn from topics EOWG - 12 February 2010
- [open] for EG4 (lecture) & EG5 (multi-day workshop) try preparing 'formal learning objectives' EOWG - 12 February 2010
- [in progress] for 'accessibility for end users' example add mention/pointer to UN convention & applicable policies EOWG - 12 February 2010
- [DONE] make example titles less 'title' like EOWG - 12 February 2010
- [open] think about making "See details in the Topics" clearer EOWG - 12 February 2010
General
- [Noted] add a tip (or other note) that often different groups might attend different part of a longer session with overlapping attendance EOWG - 12 February 2010
- [DONE] add to list for future E.g.s - 1 day on "evaluating websites for accessibility" and noted as possibility to complete after EO updates the Evaluation Suite documents EOWG - 12 February 2010
- [DONE] add to list for future E.g.s - 1 day on "using AT for web developers" EOWG - 12 February 2010
- [DONE] the "Writing Accessible Web Content" example should be for CMS users who don't know 'pointy brackets' EOWG - 12 February 2010

11 February 2009

Examples
- Example 1 redrafted
- Examples 2-7 outlined

9 February 2009

Topics
- restructured post EOWG discussion 5/Feb
- 1st three topics refined with new structure
Examples
- suggestions from EOWG discussion 5/Feb are recorded above
- introduction drafted
- work started on example #1

3 February 2009

Topics
- Learning Objectives added for all topics
- Key Points refined to be complementary to LOs
- Completed annotation of resources and splitting for 'additional' and 'handouts'
- Goals, Audiences, and Descriptions refined
- Topics numbered for ease of reference

29 January 2009

Topics
- new "Improving the Accessibility of Existing Websites" topic drafted
- new "Accessible Rich internet Applications" topic partially drafted
- Goals being rewritten as "what the learner will gain"
- Ongoing annotation of resources and splitting for 'additional' and 'handouts'

27 January 2009

Topics
- new "Accessibility and the Mobile Web" topic drafted
- new "Web Accessibility and Older People" topic drafted

26 January 2009

Topics
- new "Web Accessibility Policy and Legislation" topic drafted
- additional general wordsmithing

25 January 2009

Topics
- new "Getting Started with Web Accessibility Evaluation" topic drafted
- new "Detailed Web Accessibility Evaluation" topic drafted
- [DONE] deleted "Finding Additional Resources" topic (EO 22/Jan/10 a01)
- [DONE] rename "Scripting and WAI-ARIA" topic to "accessible rich internet applications"
- [DONE] add new topic "Web Accessibility Policy and Legislation" (EO 22/Jan/10 a02)
  - primarily referencing the developing policies, the international policies page, business case, referencing the UN convention
- [DONE] added "Improving the Accessibility of Existing Websites" as a new topic under the Managing group (EO 22/Jan/10 a03)
- [DONE] added "what someone would speak about as a presentation, or as a section of a larger training session. frameworks for building a presentation from" to definition of a topic in CL; was already part of topics.html (EO 22/Jan/10 a04)
- [DONE] split Evaluating topic into Preliminary Eval + Conformance Eval (EO 22/Jan/10 a05)
- [DONE] annotate resources as appropriate, to indicate if they are sufficient background for a presentation (e.g. benefits of WCAG 2.0, or details for you to pick from (e.g., WCAG Techniques)(EO 22/Jan/10 a07)
- [DONE] update changelog "other topics?" section based on today's discussion (EO 22/Jan/10 a08)
  - updated Topics in Approach + moved remainder to 'wish list' in Notes
- [open] reconsider topic grouping when "User..." nav in place (EO 22/Jan/10 a09)
- subsume "Web Accessibility Standards Harmonization" into "Web Accessibility Policy and Legislation"
- [DONE] CSS - consider no space after the <h3>s (EO 22/Jan/10 a10)
- [open] I {shawn} think not link to old resources "Accessibility Features of HTML" CSS, SMIL, SVG (EO 22/Jan/10 a11)
- [DONE] edit "Provide a quick introduction to web accessibility and who is affected by poor accessibility." in a multi-day training, you might do a long intro to web accessibility. Also "poor accessibility" does not work (can trigger "poor people with disabilities"). (EO 22/Jan/10 a12)
- [DONE] move Handouts as a subhead under Resources (and leave Resources at the end so it stands out) (EO 22/Jan/10 a13)
- [DONE] consider rewording the "Goals" as "Outcomes" ??? (EO 22/Jan/10 a15)
  - e.g., instead of "To introduce the methods for preliminary and conformance reviews for web accessibility, and the importance of testing with users." (which is trainer focused) -> "Participants will know the basics of..."
  - Sharron offered to take an initial pass as sample
- [DONE - new subsection added for Learning Objectiveness] consider writing the Key Points as learning objectives (EO 22/Jan/10 a16)
  - Sharron offered to take an initial pass as sample

20 January 2009

Topics
- restructured as discussed in EO 15/Jan/10 and as appropriate for each topic:
  - goal, audience, description, key points, [demonstration], [exercises/activities], resources, [handouts]
- organised topics by WAI information architecture (as a trial for groupings)
- split Designing Accessible Websites into Intro to WCAG 2; Migrating to WCAG 2; Designing with WCAG 2
- inserted place-holders for
  - Scripting and WAI-ARIA
  - Accessibility and the Mobile Web
  - Standards Harmonization

15 January 2009

Tips
- Noted the potential removed of all general presentation and training guidance, leaving just what fits in the scope of "specifically for web accessibility presentations"
- Added a placeholder for potential guidance on making presentations themselves accessible

14 January 2009

changed Preparation Tips > Tips for Presentations
Topics
- renamed 'page contents' to 'list of topics'
- moved intro para above the list of topics
- recorded TF suggestions for new topics
- reorganised Promoting
- added opening discussion questions to Introducing & Business Case
- added issue of tool reliance + tools not being up-to-date to Evaluating
- renamed Involving Users In Web Accessibility to Involving Users In Web Projects (better for translation)
- added the idea of working with working with local/regional groups to Promoting

13 January 2009

Scenarios
- Added a 'learning objective' and 'topics drawn upon' to each scenario
- Cleaned out 'added'/'subtracted' markup to make them flow

11 January 2009

Topics
- Added introductory paragraphs to all topics
- Promoting Web Accessibility - added 1:1 advocacy situation [EO idea #1]; added research opportunities [EO idea #8]
- Business Case for Web Accessibility - added mainstreaming of accessibility [EO idea #6]
- Designing Accessible Websites - 'websites' expanded to include web applications; merger of technologies (browser with authoring tool) mentioned [EO idea #9]
- Accessibility of Browsers and Authoring Tools - split into separate topics [EO idea #3] and placed after Components of Web Accessibility - added 'underlying technologies' (as well as referencing the older Accessibility of HTML/CSS/SMIL/SVG docs) [EO idea #10]
- Promoting - added 'opportunities'
Preparation
- added introductions to each subsection
- added 'impart experience'
- added "what does the trainer get from it" [EO idea #2]
Changelog
- added some ideas to the Approach and Notes sections above from EOWG 8/Jan

4 January 2009

Updated "scenarios" draft with new material

31 December 2009

Updated "topics" draft
Commenced "scenarios" draft flagging old/dated material

24 December 2009

start of drafted pages and page components
- Overview
- Preparation
- Topics

work plan

Overview:
- review Planning Web Accessibility Training for ongoing appropriateness in line with current audiences
- expand the introductory material to better explain "how to use" and "who it's for" (applies to each current page)
- update all references from WCAG 1.0 to WCAG 2.0
- update W3C resources (e.g. Alternative Web Browsing to Better Web Browsing [draft]
- add in new WAI resources such as presentations, handouts, business case, BAD, etc
- Wish list: identify a selection of robust and authoritative external resources to link to in place of Curriculum for WCAG
Detailed:
- Consider the audiences for this material
- Consider the scope of the material and outlines
  - Short presentations though to multi day training?
- Review the listed Goals and Objectives on http://www.w3.org/WAI/training/lo.html
  - Audience needs – still relevant? Any additions?
  - Learning objectives – still relevant? Any additions?
- Review the sample curricula on http://www.w3.org/WAI/training/cr.html
  - Review the six sample curricula for relevance in 2010 and currency of materials
  - Are these curricula and scenarios still relevant?
  - Does the 'audience' matter, or is it more about the topic and length of presentation?
  - Are there any other situations/scenarios where guidance would be an advantage?
    - e.g. policy developers?
  - Should we consider adding multi-day curricula?
- Review the modules on http://www.w3.org/WAI/training/ra.html
  - Review all outlines (incl ‘demo’, ‘present’, disseminate’, discuss’, ‘exercise’ sections) for currency and validity
  - Are the eight modules still all relevant? Do they need expanding?
    e.g. Tools should discuss blogs and other web-based authoring tools for creating user generated content
  - Are there additional modules that should be provided? e.g.
    - experiential module?
    - scripting and WAI-ARIA?
    - Involving user?
    - Others?
  - Review all resources - add WAI resources; consider external resources
- Review the Tips page - http://www.w3.org/WAI/training/pe.html
  - Is this still relevant?
    - If ‘yes’ it needs updating – can we collect progressively? (e.g. ask for contributions on an ongoing basis)
    - Consider dropping from this revision.
- Review the Setting Up advice on http://www.w3.org/WAI/training/ad.html
  - Update the ‘equipment’ and ‘accessible formats’ suggestions
  - What W3C materials are relevant?
  - Can we point to advice for accessible presentations? (including accessible PPT?)

Additional external resources

Specific aspect tutorials/materials:
- Involving Users:
  - Just Ask (UIAccess)
- Forms:
  - Accessible HTML/XHTML Forms (Accessify, 2004) - Ian Lloyd
  - Prettier Accessible Forms (A List Apart, 2006) - Nick Rigby
  - Making Compact Forms More Accessible (A List Apart, 2006) - Mike Brittain
  - Creating Accessible Forms (WebAIM, undated)
  - Usable and Accessible Form Validation and Error Recovery (WebAIM, undated)
  - Accessible Forms (WebUsability, 2004) - Roger Hudson
  - Accessible Forms using WCAG 2.0 WebUsability (2008) - Roger Hudson
  - Making accessible forms Part 1 and Part 2 (Webcredible, 2005)
- Links
  - Writing good ALT text (GAWDS, undated [2003?]) Simon Willison
  - Links and Hypertext (WebAIM, undated)
  - Simple, accessible external links (Maxdesign 2005) Russ Weakley
  - Navigation Accessibility 1: Menus and Links (WebUsability, 2004) - Roger Hudson
- Images
  - Creating Accessible Images (WebAIM, undated)
  - Writing effective ALT text for images (Webcredible, 2006)
  - This isn't just alt text; this is really great alt text (Nomensa, undated) Léonie Watson
- Headings & Semantic markup
  - Creating Semantic Structure (WebAIM, undated)
  - Headings and Lists - are you using them correctly? (Nomensa, 2006)
  - Importance of HTML Headings for Accessibility (YouTube, 2008) gringochapin
- Scripting
  - Creating Accessible JavaScript (WebAIM, undated)
  - Understanding Progressive Enhancement and Progressive Enhancement with JavaScript (A List Apart, 2008) - Aaron Gustafson
  - Accessibility of Rich Internet Applications (WebAIM, undated)
- Tables
  - Accessible Data Tables (Maxdesign, 2005) Roger Hudson & Russ Weakley
  - Creating Accessible Tables - data tables (WebAIM, undated)
- CSS
  - Progressive Enhancement with CSS (A List Apart, 2008) - Aaron Gustafson
- Captions
  - What are web captions? (Nomensa, 2009) Léonie Watson
  - Web + Multimedia (NCAM, undated)

Making your presentations accessible

Changelog for How to Make Presentations Accessible to All with Analysis/Requirements

Site Navigation