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 11:34, 22 May 2013 by Shawn (Talk | contribs)

Jump to: navigation, search

Nav: EOWG wiki main page


Open Issues - General

Big Picture Approach

Is this the right format? Presentation? Level of coverage? etc.

  • comment {name}
  • comment {name}

What to call these things?

Final proposal for approval:

  • 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.


  • comment {name}
  • for SEO, this has "how to" and "WCAG" in main title and "accessible [topic]" for topic titles {EOWG telecon 26 April}

previous considerations:

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}

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}

Open Issues - Topic Specific


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


Planned Topics

  • Images
  • Forms
  • Data tables
  • ...

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

(deleted this timestamp check)