W3C home > Mailing lists > Public > wai-eo-editors@w3.org > May 2010

Training Suite -- Topics for Web Accessibility Presentations and Training

From: Jennifer Sutton <jsuttondc@gmail.com>
Date: Mon, 24 May 2010 11:53:08 -0700
Message-Id: <7.0.1.0.2.20100524115114.02762958@earthlink.net>
To: wai-eo-editors@w3.org
EOWG-Editors:

Everything I mention is up to editor's discretion.

Jennifer




[Draft] Topics for Web Accessibility Presentations and Training

Status: Draft in progress - updated $Date: 2010/05/03 21:44:02 $

http://www.w3.org/WAI/training/topics.html


1. In the contents, there are these three links:

8. Browser Accessibility and UAAG
9. Authoring Tool Accessibility and ATAG
10. Accessible Rich Internet Applications


Since abbreviations are used in 8 and 9, maybe it'd be a good idea to 
mention (ARIA at the end of 10.

Elsewhere, it's "WAI-ARIA," but I'm not sure what the W3C has decided 
in terms of how it's to be referenced.

2. Audience: Anyone with an interest in the web or disability or related topics

Change to:

Audience: Anyone with an interest in the web, disability, or related topics

Note: I make other suggestions about these "audience" sections with 
respect to semi-colons vs. commas.  the key is to be consistent, and 
maybe my preference for commas should be disregarded.

3.Demonstration: Show some
[link[ video of people with disabilities using the Web  - external page

Should it be "some of a video?"

Or "some of the [link] videos . . ."

4.  When they answer - ramps, curb cuts, captions, automatic
doors, elevators, etc - ask if anyone uses those accommodations other 
than people
with disabilities.

Change to:
When they answer ramps, curb cuts, captions, automatic
doors, elevators, etc[add period and comma] ask if anyone uses those 
accommodations other than people
with disabilities.

5. Audience:
  Anyone with an interest in the web or disability or ageing or related topics


Change to:
Audience:
  Anyone with an interest in the web, disability, or ageing or related topics

6. Demonstration: Show some
[link] video of people with disabilities using the Web  - external page

See my thoughts about this in Item 3 of this message. Basically, 
whatever is decided should be consistent if this repeats throughout 
the document, but I won't continue to repeat it here.

7. grand parents

Should be "grandparents."

8. [link] Videos of How People with Disabilities using ICT - external page
  - some demonstrations, some interviews (compiled by UIAccess)

Maybe change "using" to "use." Or "are using."

Maybe change:
  - some demonstrations and interviews (compiled by UIAccess)


If this is changed here, also change in Item 14 of the page.

But perhaps the link must reflect the cited page's real name.  It 
just sounds a bit awkward.

9. to an an accessible

Delete an "an."

10.  Audience:
  Web developers and others with professional responsibility for 
creating accessible online content and applications; accessibility 
advocates; ICT departments


Maybe change to:
Audience:
  Web developers and others with professional responsibilities for 
creating accessible
online content and applications, accessibility advocates, and ICT departments

11. Relate underlying technologies to accessibility (and appreciate 
WAI-ARIA as an enabler)

I wonder if there's a better word than "enabler."  ARIA is an 
"enabler" of what?

Perhaps it should say something about realizing ARIA's value?

Maybe:
Relate underlying technologies to accessibility (and realize WAI-ARIA's value

Side note:
I see different references for ARIA in the Web accessibility 
community, generally.  What has W3C standardized on, and is the term 
used consistently across these four documents?

12. UUAG,


Shouldn't it be just one U?

13.  Key points
Web accessibility depends on several components working together - 
UUAG, ATAG, WCAG
Important interaction of all the WAI guidelines in ensuring an accessible Web
Role of underlying technologies (HTML, XML, CSS, SVG, SMIL, etc.)


Why not mention ARIA in any of these points?

14.  Goal:
  Encouraging web accessibility advocates and support their efforts 
to promote inclusive design practices.

Might want to read through each goal and try to make the construction parallel.

Seems like many are active verbs, so maybe for Item 3, it should be 
"Introduce," instead of "Introduction.
"

Maybe for this one, it should be
"Encourage . . . and support"

15.  Audience: Web developers; policy makers; accessibility advocates

Maybe change to:
Audience: Web developers, policy makers, and accessibility advocates

Consider reading the "audience" definitions and trying to make them 
parallel. I tend to favor separating the audiences by commas, rather 
than semi-colons, but being consistent is ideal.

Part of why I suggest making the audiences and goals sections 
parallel is because I am wondering whether people might take this 
document apart i.e. if they were planning a presentation, their 
bosses aren't going to read all of this.  And if it's taken apart, 
then the audiences and goals sections might be closer together, so 
parallelism might become more important.

I'm not going to keep repeating these, but if there are changes, I'd 
be glad to take another look.  The document is large, so I understand 
that it's a bit hard to track, scroll, etc.

16.  Description
Techniques to use an avoid from WCAG 2 when developing

websites that will be accessible
to people with disabilities and older people.

Are there techniques in WCAG 2 that should be avoided? This makes it 
sound to me as if there are things in WCAG 2 that are wrong.

17. WCAG 2.0 are technology neutral, general accessibility principles 
that apply to all
web technologies

Maybe change to:
WCAG 2.0 consists of  technology neutral, general accessibility 
principles that apply to all
web technologies

18.  If presenting this topic as a hands-on multi-day workshop, some 
presenters have found
that a break between days can enable higher levels of participation

I'm not clear why this is specifically mentioned in this topic.

19. In here, should be "documents:"
WAI-ARIA Overview
  - describes the problems that WAI-ARIA addresses, and introduces 
the WAI-ARIA suite
of technical document

20. Is "workarounds" a word, or is it "work-arounds?"

21. Delete one of the "and"s:
Discussion: Ask what blogging and social media tools participants are 
using [and and]
discuss any accessibility issues. highlight the importance

22.  WAI-ARIA features that make help make Ajax, DHTML, etc accessible

Change to either:
"that make"
or
"that help make"

23. Care required when drawing conclusions

Most of the others in this section are "how tos," so maybe it'd be 
good to rephrase:

How to draw conclusions

24. See change in brackets:
Use of automated web accessibility evaluation tools (noting that 
while many tools
are still oriented towards WCAG 1.0 evaluation[add comma] they can 
still give a useful overview)

Maybe delete one of the "still"s.
Received on Monday, 24 May 2010 18:53:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 May 2010 18:53:55 GMT