Web Accessibility Preliminary Evaluation

Nav: EOWG wiki main page > Evaluation Pages

Easy Checks - new clean comment page!

Notes


Important Note: For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way — for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.

Easy Checks - A First Look at Web Accessibility

title ideas

Contents

[Thanks to #Contributors!]

Introduction

Introduction in WAI draft page

Status:

  • Complete, ready for detailed review.
  • no major edits since February

Comments:

  • comment {name, date}

Page title

Page title in WAI draft page

Status:

  • Complete, ready for detailed review.
  • no edits since February

Comments:

  • [open] Suggest the alt-text on screen grabs include the browser name and version {Andrew}
    reply: I think it would add unnecessary clutter - lots of text and do people who cannot see the image care so much which browser & version? what do others think? {shawn}
  • [open] We should include FF web developer toolbar example too - 'Information' then 'View Page Information' opens a new window with the page title at the top {Andrew}
    reply: why? the page title is shown in the window title bar so why would you need to use the develop toolbar to get it? {shawn}
  • comment {name}

Images for Page Title

  • To check page title - with IE WAT:
    <...image link here...>

Image text alternatives ("alt text")

alt text in WAI draft page

Status:

  • Complete, ready for detailed review.
  • no edits since February

Comments:

  • [open EOWG] Finally, I'm mulling over the term "inappropriate alt text". Would that be the correct term? {Vicki}
    reply: other ideas?
  • comment {name}

Headings

Headings in WAI draft page

Status:

  • Complete, ready for detailed review.
  • no edits since February

Comments:

  • comment {name}

Color contrast

Color contrast in WAI draft page

Status:

  • EOWG: Needs someone to fill in some details on using the tools.
  • EOWG: Needs some images.
  • Overall flow, instructions, text is complete.
  • 7 March edit: moved the 3 options with pros & cons from under "To check contrast with IE WAT" up a level to apply to all.

Comments:

  • [open EOWG] mention/discuss color blindness? {Andrew}
    reply: is that too much complication for an easy check? If you think not, please draft wording :) {Shawn}
  • comment {name}

Zoom

Zoom in WAI draft page

Status:

  • Complete, ready for detailed review.
  • 7 March edits were mostly minor. Note new second sentence in first paragraph: "Some need to change other aspects of text display: font, space between lines, and more." This is important so that readers don't think simple zoom covers all user needs (like in the color section we mention the need for low luminosity).

Comments:

  • comment {name}

Keyboard access, content order, visual focus

Keyboard, etc. in WAI draft page

Status:

  • Draft in progress

Comments:

  • comment {name}

Forms, form labels, and error messages

Forms in WAI draft page

Status:

  • Draft in progress

Comments:

  • comment {name}

Multimedia (video, audio) alternatives

Multimedia in WAI draft page

Status:

  • Draft in progress

Comments:

  • comment {name}

Next Steps

[Status: Draft in progress - feel free to edit the text or add comments below.]

So, you've spent a little time getting a sense of the accessibility issues that need to be addressed, but what do you do next? How can you flag what you've discovered, while being sure that the information reaches those who can make the changes happen?

If you're a site visitor who doesn't work for the organization but wants to report accessibility-related concerns, you will likely want to reach out by using the site's contact form or by sending email to a "Webmaster" address. Of course, if you have a specific point of contact in the organization, starting with that person can be beneificial.

On the other hand, if you work for the organization that operates the site you've looked at, you might use a bug-tracking/helpdesk system to report your findings. Or you might decide it would be more effective to write a report in which you group problems and possible solutions in a way that makes sense within the company's structure.

Whether or not you work for the company that runs the site you've checked, you'll want to describe the issues clearly, including identifying the browser and any other tools you used. Providing as much detail as you can will help others replicate the issue and identify approaches to resolve it. For examples of recommendations we have developed to guide site visitors who experience difficulty accessing a web site, see a section of [ http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] called "Describe the Problem." These Sources for More Information will help your colleagues familiarize themselves with additional references for more details about problems and solutions.   When it's time to conduct a more thorough evaluation,either internally or by hiring a qualified contractor, the [WCAG-EM Evaluation Methodology Overview] (coming soon) and accompanying documents will help you or others develop plans as we all work together to provide a more accessible web for all.



EOWG Notes on Next Steps

  • comment {name}



Contributors

Thanks to:

  • Those who edited in December and January: Suzette (forms, @@), Sharron (Intro, @@), Shawn (Intro, page titles, headings, alt text), Ian (zoom n text resize).
  • Those who commented in December and January: Sylvie, Wayne, Anna Belle, ...
  • Those who drafted checks 16-28 November:
    • Sharron for drafting {list sections!}
    • Suzette for drafting : Check usable with page zoomed and text enlarged, Check color contrast, Check color coding and shape coding, {?other sections}
    • Wayne for drafting {list sections!}
  • Andrew & Shawn for editing the keyboard access & visual focus section in early Nov.
  • Ian, Suzette, Vicki, Sylvie, Helle, Shawn for working on an early draft at the f2f in Nov.
  • Sharron for help making all the early drafts and versions less confusing.
  • Wayne and Ian for sharing colleagues' related work.
  • Denis for edits to the old page content.

testing image: search-icon.png

Consider for Later

  • The text says: "The first thing screen readers say when the user goes to a different web page is the page title. Page titles are important for orientation — to help users know where they are and move between open pages."
    Would it be useful to have a sound clip of the screen reader going through page titles? Low priority, but maybe neat for people who don't know screen readers? {Shawn}
Last modified on 7 March 2013, at 19:27