> EOWG Home Page > Before and After Demonstration
This is an outdated draft. The latest version is available at http://www.w3.org/WAI/demos/bad/.
This page records change requests and changes made to the draft resource Before and After Demonstration. Please send additions or corrections to wai-eo-editors@w3.org.
Last updated on $Date: 2012/02/20 21:03:28 $ by $Author: shadi $
on this page: About the Project | WAI-AGE Update | Evaluation Report | Open Review Notes | Previous Changes
The "Before and After Demonstration" resource suite consists of the following parts:
- sample before site that demonstrates some common accessibility issues;
- sample after site that demonstrates a repaired version of the before site;
- an example of an evaluation report that highlights the demonstrated issues;
- accompanying documents such as overview page, site index, and others to facilitate using the resource suite.
Find the requirements for the Before/After Site (not completely up-to-date).
The "Before and After Demonstration" is currently being updated to better reflect the finds of the WAI-AGE Project and to meet WCAG 2.0. Please find a list of changes that will be be made to the Demo:
- Implement a selection of requirements for older users
- Update the Demo to better meet WCAG 2.0 Level AA
- Other changes that need to be made to the Demo
- Improve the Demo Survey Form page (visual design and implementation)
- Clean-up and test the CSS throughly (the CSS of the Demo needs to serve as a best practice)
- Implement minor changes and open change-log items (see Open Reivew Notes section further below)
- Provide an "in-between" page with icons to highlight the barriers (see Graphic/Icon-Based Reporting Formats article from WebAIM)
- Consider improvements to the Evaluation Report or implementing Wish-List items if they fit well with the work outlined above (see notes on each of these items below)
Currenlty the Demo evaluation report is designed around WCAG 1.0 and needs to be updated. Please find below previous notes about the report design:
Purpose of the evaluation report
- Provide detail on the barriers and repairs demonstrated on the before/after site
- Serve as a model of one type of evaluation report for others to learn from
Audience of the evaluation report
The evaluation report targets developers, evaluators, advocates, and decision makers (such as managers) who want to:
- learn more about accessibility barriers studying real examples
- learn how to write evaluation reports by studying an example
- compare their evaluation reports to other types of reports
- better understand what to expect from evaluation reports
Approach of the evaluation report
- Include an introduction, executive summary, scope, and references sections
- Provide an overview of the conformance to the individual WCAG checkpoints
- Link from the conformance overview to more information about the barriers
- Sort the detailed findings by barriers and barrier groups to clarify the context
- Include screen shots to identify the barriers, and describe recommended actions
Possible future expansion of the evaluation report
- Provide detailed descriptions of the barriers and explain some background
- Implement a sortable list for the overview of the evaluation results
- Include detailed descriptions of barriers that are not demonstrated on the site
The following is a list of open review notes taken from the individual changelog records noted further below in the document.
- [open] consider using a different style for the "barriers page"
- [open] consider a mechanism to get back from the eval report to the "barriers page"
- [open] "after" site will still be repaired only to WCAG 1.0, level AA (priority 2 checkpoints)
- [open] continue expanding full-blown report to support educational purposes
- [open] consider adding a brief in-between meta page on reporting
- [open] improve executive summary on the eval report to be more stand alone
- [open] implement pages to start with level 1 headings, revise headings
- [open] implement a dummy page that confirms successful form submission
Notes on ideas for future updates:
- resizeable text within a fixed size text area (such as
DIV
), when the text is resized it disappears around the box
- javascript pop-window of help page
- in-page navigation using javascript menus
- moving content that can not be turned off (e.g. advertisements)
- multimedia content (audio or video) to display captioning etc.
- background music that can not be turned off by users
- inconsistent navigation (maybe in connection with pop-up help page)
- frames example (maybe pop-up help page could use frame sets)
- large file (eg PDF) for download without prior warning
- provide source code and examples of the demo for download
- consider references to automated tools for eval report
- provide a template version of the eval report for download
- consider a sortable version of the eval report
Notes as of 28 July 2006
From the EOWG Teleconference on 28 July 2006
- [done] rework the warning banner to make clearer, keep it as a sentence
- [done] right-align the warning banner text (as opposed to centering)
- [done] "list of barriers" link from the warning banner should jump to top of document
- [done] make the colors of the warning banners less aggressive
- [done] rephrase last sentence of the introduction of the "barriers page"
- [open] consider using a different style for the "barriers page"
- [done] consider using the logo-icon to do something (go to the site index?)
- [done] add a small blurb on templates in the introduction of the "barriers page"
- [done] remove all "note:" references to the template and rework that section
- [done] implement rewording suggestions recorded in the minutes
- [open] consider a mechanism to get back from the eval report to the barriers page
Notes as of 21 April 2006
From the EOWG Teleconference on 21 April 2006
- [done] consider adding a sortable version of the eval report in the wish-list
- [done] add some explanation of section 4 and 5 of the eval report in the introduction section
- [done] clarify that the eval report checklist summary is based on WCAG 1.0 (and link to it)
- [done] add level 3 in the table of contents of the eval report
Notes as of 7 April 2006
From the EOWG Teleconference on 7 April 2006
- [done] evaluation report should cover all WCAG 1.0 checkpoints, reporting only those relavant to the demo
- [open] "after" site will still be repaired only to WCAG 1.0, level AA (priority 2 checkpoints)
- [done] consider providing a downloadable template version of the eval report (wish-list?)
- [done] revise potentially offensive wording or phrases that are tough to translate/understand
Notes as of 17 March 2006
From the EOWG Teleconference on 17 March 2006
- [open] continue expanding full-blown report to support educational purposes
- [open] consider adding a brief in-between meta page on reporting
- [done] add reference to automated tools on wish-list
- [done] clarify that this is an example eval report, there are many other types
Notes as of 10 March 2006
From the EOWG Teleconference on 10 March 2006
- [done] note the level of conformity in the eval report early, preferably in the introduction.
- [done] consider organizing the eval report acording to checkpoints rather than to specific pages
- [done] consider that there are different types of eval reports, not only this one
Notes as of 2 March 2006
From the EOWG Teleconference on 2 March 2006
- [open] improve executive summary on the eval report to be more stand alone
- [done] eval report findings should illustrate the problem and solution, with representative samples, rather than trying to be exhaustive/complete
Notes as of 24 February 2006
From the EOWG Teleconference on 24 February 2006
- [done] add "source code tutorials" to changelog wishlist
- [done] consider cookbook aproach for Using the Demo
- [done] consider adding some meta-information about the eval report
- [done] revise usage of DL elements on the overview page
Notes as of 14 February 2006
From the BAD TF Teleconference on 14 February 2006
- [done] improve use of images on home page to better clarify accessibility issues
- [done] improve color contrast for links on all pages
- [done] move PDF file for download to wish-list for future updates
- [done] explicitly associated label for the quick menu
- [open] implement pages to start with level 1 headings, revise headings
- [done] implement screen-reader directions
- [done] implement skip-links for screen-readers
Notes as of 27 January 2006
From the EOWG Teleconference on 27 January 2006
- [done] add small screen-shot images on overview page to assist navigation
- [done] improve common look and feel (branding) across the demo to assist orientation
- [done] expand evaluation report categorization into a full-blown report
Notes as of 20 January 2006
From the EOWG Teleconference on 20 January 2006
- [open] implement a dummy page that confirms successful form submission
- [done] shorten brief descriptions of barriers from the warning banner
- [done] move copyright information to a second banner at the bottom of the pages
- [done] improve cross-demo navigation through the top banner
- [done] implement real horizontal rule after top banner (and before footer)
- [done] consider using the "features list" as the gateway across the demo modules
Notes as of 17 January 2006
From the BAD TF Teleconference on 17 January 2006
- [done] implement headings on form page as images
- [done] change expanding font on article page to slight change of color
- [done] check and improve editorial content on all pages
- [done] continue refinement of visual design
- [done] implement brief descriptions of barriers into the warning banner
Notes as of 13 January 2006
From the EOWG Teleconference on 13 January 2006
- [done] improve cross-demo navigation to facilitate overview
- [done] consider adding brief description of barrier highlights for each page
- [done] ensure unambigious continuity of submission on the forms page
Notes as of 6 December 2005
From the BAD TF Teleconference on 6 December 2005
- [done] continue cross-checking and improving implementation of "after" pages
Notes as of 18 November 2005
From the EOWG Teleconference on 18 November 2005
- [done] improve color and font implementation of the warning banner
- [done] minor improvements to visual design and layout
- [done] keep cross-demo navigation in the top banner only
- [done] remove any "real" content from the demo pages
Notes as of 15 November 2005
From the BAD TF Teleconference on 15 November 2005
- [done] consider putting the right navigation bar on the article page
- [done] continue improving and refining forms and article pages
- [done] consider adding links to external pages outside the project
- [done] finalize template for "after" pages and start implementation
Notes as of 4 November 2005
From the EOWG Teleconference on 4 November 2005
- [done] implement a clear warning that is well visible to all users
- [done] consider using a different, more formal style for the warning
Notes as of 11 October 2005
From the BAD TF Teleconference on 11 October 2005
- [done] work with designer on improving visual design
- [done] adapt data tables to the new visual design
- [done] refine and improve the forms page
Notes as of 31 August 2005
From the BAD TF Teleconference on 31 August 2005
- [done] drop usage of frames for now and add to wish-list for later versions
- [done] add javscriot drop-down menu to menu page
- [done] add examples of keyboard compatibility barriers on menu page
- [done] add examples of fixed fonts on article page
- [done] add examples of deprecated elements on article page
- [done] add examples of resizable font within fixed sized border on article page
- [done] add inconsistent navigation to wish-list for future updates
- [done] move pop-window (of a help pahe) to wish-list for future updates
- [done] move form from article page to forms page
- [done] remove nested tables from article page and use nested DIV elements
Notes as of 26 August 2005
From the EOWG Teleconference on 26 August 2005
- [done] for task force discretion: consider droping visual layout breaking outside IE, or moving this feature to a different page
- [done] for task force discretion: consider adding keyboard accessibility (tabbing order) or putting on wish-list
- [done] for task force discretion: consider dropping frames or have a version without frames
- [done] for task force discretion: consider deprecated HTML elements, resizing fonts within non-resizing boxes, fixed fonts, and javascript drop-down menu
- [done] for task force discretion: consider method of navigating throughout the resource suite
- [done] for task force discretion: consider clarifying that these pages are demonstration (eg through a warning)
Notes as of 24 August 2005
From the BAD TF Teleconference on 24 August 2005
- [done] move color coding to forms page
- [done] drop-down list box to header page
- [done] misused blockquote for news article
- [done] open new windows without warning on home page
- [done] pop-window of help page on wish-list
- [done] images within links with innapropriate alt text on news article
- [done] simple data tables on news article
- [done] what's on tonight box from home page to news article
- [done] news article graphs and illustrations in floating divs that don't appear in the same context as visually
- [done] text images with widely used fonts for the menu (mouse-out, mouse-over, you-are-here)
- [done] for wish-list: in-page navigation (images from designer)
- [done] for wish-list: something moving (advertisements)
Notes as of 11 August 2005
From the BAD TF Teleconference on 11 August 2005
- [done] ensure that visual layout breaks in Opera
- [done] create a collection of accessibility barrieres to be demonstrated
Other meetings of interest
All relevant discussion and minutes are publicly available through the mailing list archives of EOWG and the mailing list archives of BAD TF. Additionally, the following are some minutes of discussion during the start-up phase of the project:
Copyright © 2006 W3C (MIT, ERCIM, Keio ), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.