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.


From Education & Outreach
Revision as of 07:04, 18 July 2013 by Shadi (Talk | contribs)

Jump to: navigation, search

Nav: EOWG wiki main page

References and related wiki pages

Open Issues - General

Big Picture Approach

For discussion 19 July

  • Comment {Name}
  • On this first homepage of the image tutorials, may be change the alt text in the navigation menu. Actually called "current page" Images. Prefer "current topic or tutorial" to make it clear that you are in the images topic. {Sylvie, 28 June}
  • It may be useful to add a note after the list of the pages included in the tutorial, saying that you can either read the different pages in the proposed order and clicking on "next page", or choose in the list to read on the types of images that meet your situation. So if you don't use complex images, you don't need to read it. {Sylvie, 28 June}
  • [closed] The Tables FAQ page is not an FAQ - there are no questions! These are great tips, though. Should we rename this page to "Tips", "Recommendations", or something else? {Paul - July 11}
    Reply: Apologies, the Tables FAQ page isn't complete, I plan to change some of the tips to FAQ. I should have removed the prior content (when the page was called "Tips". Will do that now. Thanks. {Bim - June 12}

[closed] For discussion on Friday 28 June

New approach applied to Images tutorial:
After our meeting last Friday, see minutes 21 June we've tried to balance the needs for brevity and detail, so the Images tutorial pages have been reorganized. Please compare this with another section, such as Tables tutorial. Does the new approach satisfy the variety of needs for everyone in the diverse target audience (developer, trainer and manager)?

  • [closed] Restructure and presentation is better/clearer, but maybe the landing page is too bald now :) {Andrew, 28 June}
    Thanks Andrew, the landing page now includes the concepts, users can now read as far down the page as they want but get short information and links to other pages near the top of main content. {Bim - June 12}
  • [closed] I still prefer the images section even if it has been reorganized. I like the overview page. I added some comments below specific to the images tutorial. {Sylvie, 28 June} {Thanks Sylvie, I've now moved your other comments 12 June meeting topic.) {Bim & Shawn - June 12}

What to call these things?

Full name

Latest draft:

  • overall title: Web Accessibility Tutorials - Guidance on how to create websites that meet WCAG (which is currently in the latest draft)
  • topic titles: Accessible Forms; Accessible Images; Accessible Tables; etc.


  • for SEO, this has "how to" and "WCAG" in main title and "accessible [topic]" for topic titles {EOWG telecon 26 April}
  • Whole websites - or the component parts? Just a thought: websites can be huge whereas the tutorials cover very specific design features. Is it possible to convey that the tutorials cover common problems in bite sized pieces rather than suggesting that you are learning about accessibility of whole websites? I would propose using 'webpages' rather than websites in the subtitle. Although I'm not sure if that is a good solution, but is at least a more modest and achievable goal? {Suzette}
  • comment {name}

  • overall title: Accessibility Tutorials - Guidance on how to create websites that meets WCAG (which is currently in the latest draft)
    • need "web" in there somewhere. either:
      Web Accessibility Tutorials - Guidance on how to create content that meets WCAG or
      Accessibility Tutorials - Guidance on how to create web content that meets WCAG {Shawn}
    • my vote is for the latter - prefer the shorter title, longer sub-title {Howard - May 2}
    • I prefer the first with "Web accessibility..." {Vicki - May 3}
    • [done, per EOWG telecon discussion] The term "websites" now replaces "content" in the longer title, see the starting page for example {Bim - May 7}

    Short name

    This should be a single word describing the type of resource so that the user knows what they will find. It will also be part of the URI. Recent suggestions:

    • For me tutorials was fine, but OK for another brainstorming. {Sylvie 20 June}
    • I've seen these types of documents referred to as "articles" at WebAIM and elsewhere. {Howard, 27 June}
    • Comment {Name}
    Previous short name suggestions

  • "Naming the notes" section of the Analysis page
  • 26 April EOWG minutes
  • e-mail thread
  • 12 April EOWG minutes

Your Return on Effort

For example, see this draft section in Images, yet none for Tables

What are the pros and cons of including this section? relationship to Business Case?

  • On the page Basic concepts the heading title "your return on effort" is not really clear to me. {Sylvie, 28 June}
  • comment {name}


  • Link pointing to next page is much better but still needs to be more prominent - perhaps a large graphic arrow (with alt text). {Howard, 27 June}
    reply: Sounds like a plan. Let's bring it to the group once the overall approach and naming is agreed. As these links are generated dynamically by PHP script, any change will cascade across all pages as soon as it's been applied. {Bim - July 12}
  • [closed] I find the What to do, Why, How, Conformance very hard to read because of the tight spacing — both the line-height and the space between sentences. I realize that I need things more spaced out than "common" so would appreciate other perspectives on this. {Shawn 20 June}
    reply: If the new approach is approved these lists will disappear. Do let me know if you have difficulty with any others though. {Bim - July 12}

Open Issues - Topic Specific

[moved] About these Tutorials


Should we not include "Providing a summary" since summary is deprecated in HTML5?


Under "Overview", "Clear Structure" links to page with the header "Structure". Keep terms/issue consistent.


Topics in progress

  • Images
  • Tables
  • Forms
  • Carousels
  • ...

Possible Topics

  • Components - focused tutorials using different technologies (HTML4, HTML5, WAI-ARIA, ...)
    • Forms: input elements, form layout, pull-down menus, error messages, ...
    • Tables: layout tables, simple data tables, complex data tables, ...
    • Images: decorative images, charts and diagrams, photos, illustrations, ...
    • Page titles and headings
    • Navigation: in-page navigation, on-site navigation, cross-links, ...
    • Keyboard control: device independence, tab order, reading order, ineffictive use of tabindex (or should this be under "Navigation"?) ...
    • Information structure: (prime content first)in page titles, labels, headings, links, ...
    • Widgets:
      • sliders
      • accordions
      • menus
      • dials
      • carousels
      • date pickers
      • tab panels
      • tree controls
      • modal dialogs
      • star rating selectors
      • ...
    • ...
  • Technologies - explanatory resources on different technologies (HTML4, HTML5, WAI-ARIA, ...)
    • WAI-ARIA:
      • landmarks
      • roles
      • active regions
      • application: when to use, when to avoid
      • ...
    • HTML5:
      • sections
      • menu
      • making compatible with older browsers / issues with AT (Howard)
      • ...
    • ...
  • Audiences - explanatory resources on optimizing website accessibility for different audiences
    • People with cognitive disabilities
    • Keyboard users (with and without vision)
    • Older people
    • People with low vision
    • ...
  • Contexts - explanatory resources on applying WCAG2 in different contexts and situations
    • mobile websites
    • mobile web applications
    • content for digital TV
    • ...

See also: Easy DD potential topics

Archived Notes

Terminology: code or markup?

Pros, cons, considerations?

26 April EOWG minutes

  • support for "markup" — "markup" is more technically correct. non-developers might not know that term, and might know "code" — however, target audience for this is people who ought to know "markup". also, we'll use "code" for things like JavaScript I assume? {Shawn}
  • in Easy Checks we say "headings need to be "marked up" in the web page "code" (e.g., HTML)". Perhaps use similar approach. In the first instances, say something like: "website code, called "markup", e.g., HTML" — then use "markup" throughout {Shawn}
  • my vote is for "markup" - more precise. Code is a very broad term.{Howard May 2}
  • comment {name}

Headings in Concept pages

Each topic starts with a concepts page (forms, tables, images) that currently has two sections headed:

  • Summary
  • Who benefits

Ideas for these headings?

26 April EOWG minutes

First heading:

  • Overview {Bim, Anna Belle}
  • What's in this tutorial (probably not, just brainstorming :-) {Shawn}
  • What you need to do (probably not, just brainstorming :-) {Shawn}
  • comment {name}

Second heading:

  • Rationale {Bim}
  • What are the benefits? (I like rationale too but maybe a little fancy a word){Howard - May 2}
  • comment {name}

Other comments:

  • it's not clear that there are other pages. perhaps have a sentence at the end of the first section something like: "This Forms tutorial covers: [subtopic linked], [subtopic linked], and [subtopic linked]. {Sylvie & Shawn}
  • the links at the bottom of each page to the next page/topic are easy to miss and the menu indicating other sections is off to the left - also easy to miss. The [subtopic] approach sounds promising but would like to see how it would look {Howard - May 2}
  • comment {name}


(deleted this timestamp check)