Tutorials/Feedback/Cover Page

From Education & Outreach
The work on this deliverable has primarily moved to Github. If you can, leave your comments as issues there. This wiki page is still monitored.

Quick fixes

Typos, wording suggestions and things that generally not need EOWG input/concensus.

  • delete selecting tools link 1. We previously discussed moving the WCAG and other links to the bottom of the page so they don't lead people off the page before they read it all. For the same reason, I'd suggest moving the link to "Selecting and Using Authoring Tools for Web Accessibility." from the middle of the page. 2. I'm not sure how important that resource is in the context of these Tutorials -- e.g., others may be more important such as Involving Users. 3. Finally, that resources is way out of date and I think we do not want to point it to -- so best just to remove it. {Shawn, 11 July 2014}
    • Made the change {Eric, 2014-Jul-19}
  • delete 'inclusive'. Current wording: "Web authoring tools, including Content Management Systems (CMS), WYSIWYG editors, word processors, and other tools, can help you create content that is accessible and inclusive as shown in these tutorials." Maybe delete "and inclusive" here. It adds an additional idea without explaining it. Or maybe link it to http://www.w3.org/WAI/users/ -- but then it might be a distraction.

{Shawn, 11 July 2014}

    • Made the change {Eric, 2014-Jul-19}
  • minor punctuation - oops, I read

    Web authoring tools, including Content Management Systems (CMS), WYSIWYG editors, word processors, and other tools, can help you create content

    wrong as

    Web authoring tools, Content Management Systems (CMS), WYSIWYG editors, word processors, and other tools can help you create content

    so I deleted the comma after 'other tools' - but now I see it belongs there. Maybe the sentence would be easier to read with parenthesis like:

    Web authoring tools (Content Management Systems (CMS), WYSIWYG editors, word processors, etc.) can help you create content

    {Shawn, 11 July 2014}
    • Made the change {Eric, 2014-Jul-19}
  • Suggested rewording for the second sentence of the first paragraph:

Current: "We designed these tutorials to help websites to reach the widest possible audience and make the web a better place at the same time."
Proposed: "We designed these tutorials to help the web community build websites which will reach the widest possible audience and make the web a better place at the same time."
Rationale: at a first read, I thought there was an error at "help websites" because usually one helps people.

    • We have made changes to this sentence {Eric, 2014-Jul-19}
  • Suggested rewording in a bullet point:

Current: "Project managers will gain understanding of accessibility approaches to help with project planning."
Proposed: "Project managers will gain understanding of accessibility approaches which will ensure that accessibility is addressed early."
Rationale: Just to be more precise about accessibility being included early in a project otherwise it could sound like accessibility helps with project planning.
Great work, guys/gals! {Vicki, 2014-May-14}

    • We have made changes to this sentence {Eric, 2014-Jul-19}
  • Minor edit: 1st paragraph, 2nd sentence: every day should be "everyday" {Paul, 2014-May-30}
  • Suggested rewording of 1st paragraph, 2nd sentence:
    • FROM "We’ve designed these tutorials to help people..."
    • TO "These tutorials are designed to help people..."{Paul, 2014-May-30}
      • We have made changes to this sentence {Eric, 2014-Jul-19}

Comments

Comments on the current incarnation of the tutorial, can be longer and may require EO.

  • Comment {Name, 2014-Month-Day}

Proposals

Proposals for new sections and examples can go here.

  • Comment {Name, 2014-Month-Day}

Done

Quick Fixes

Comments

Proposals