[wai-eo-editors] <none>

EO Editors:

Comments on:
DRAFT. Content last updated: 16 December 2009. [

1.  Consider also contacting organizations that do a good job of 
making their website
accessible and easy to use by people with disabilities and older 
users, to acknowledge
and encourage their efforts.
Organations . . . their web sites . . . mixing singular and plural.

2.  Doubled the:
It is best to figure out the the person responsible for the web page 
or application

3. Typo, brackets;
Clearly describing where the problem occurred and what the problem 
is, and also [inlcuding]

4. It appears as if sentences are starting with "e.g."
Provide details about what you were trying to do, and why it was 
difficult or impossible
to do it.
Examples of problem descriptions:
Doesn't "e.g." signify examples, so it's not necessary? Look for 
possible similar other occurrences when using "e.g."

5.  Edits in brackets:

Ask that the organization reply to you. Include [information about] 
how you want them to contact you.
If you are comfortable, include a phone number in case they want [add 
to] learn more about
the problem.

6.  Two points:
Considering legal action, for example, based on web accessibility 
requirements in
anti-discrimination regulations

6.1.  Worth adding at the end of the sentence "in your country?"

6.2. Maybe we have it, and I've missed it, and/or maybe it's too 
complicated, but isn't there a page within WAI that has links to 
relevant legisltation around the world?

Worth including that, if not there already?

7.  although they may not being doing it well yet. And there

Change "being to "be."

8. Edits, brackets:

Then[,] if you can learn with [change where the organization is to 
what (or how much) the organization knows with respect to] accessibility,
it will help you follow up more effectively.

Note my parenthetical is suggesting a choice, rather than wording, per se.


Received on Friday, 18 December 2009 13:27:08 UTC