Overview
- WCAG evaluation methodology
- Accessibility-support database
- Guidance for tool developers
- Other resources on evaluation
Achieving Conformance
Achieving conformance requires consideration throughout the process:
- Awareness-raising and buy-in
- Tools, processes, and training
- Continual quality-assurance
Maintaining Conformance
Maintaining the achieved level of accessibility conformance requires:
- Awareness-raising and buy-in
- Tools, processes, and training
- Continual quality-assurance
Conformance Evaluation
In some situations post-development evaluation is useful:
- Evaluate website to improve it
- Verify conformance statements
- Regularly monitor the progress
Applicability
Website: A coherent collection of one or more related web pages that together provide common use or functionality.
- Full, self-enclosed set of web pages
- Includes all "complete processes"
- No exclusion of individual web pages
Example Website

5 Steps of WCAG-EM
WCAG-EM is designed around 5 steps of evaluation:
- Define the evaluation scope
- Explore the target website
- Select representative sample
- Audit the selected sample
- Report evaluation findings
Some Highlight
Some of the areas currently under discussion:
- Types of reports
- Sampling approach
- Performance Score
Reporting
WCAG-EM describes these types of reports:
- Basic Report: yes/no type result
- Detailed Report: points examples
- In-Depth Report: analyzes issues
Sampling
WCAG-EM suggests content-oriented rather than volume-oriented sampling:
- Targetted sampling
- Random sampling
- Sample adjustment
Scoring
To score or not to score, that is the question:
- Coarse and potentially misleading
- Misses context and can deter focus
- ...but powerful for communication
Input Wanted!
Your feedback on these and other aspects is needed:
Schedule
Completion of WCAG-EM 1.0 is expected in 2013:
- Current draft: for review
- Summer 2013: final draft
- December 2013: first Note
Interested in participating? Please contact us!
Accessibility Support
Developers need to know how supported Techniques are:
- Web browsers
- Assistive technologies
- Operating systems
...and individual versions of these!
Really?!
How can you collect this sheer amount of information?
Scope: not all information is really equally interesting.
Crowd Sourcing
Attempt to collect partially existing information:
- Current "hero" contributors
- Rising "hero" contributors
- Future research projects
- Browser and AT vendors
- Enterprise repositories
Schedule
Accessibility support database is already under development:
- Q2 2013: first public prototype
- Populate database and refine
- Q2 2014: first public release
Interested in contributing? Please contact us!
Evaluation Tools
Current situation of web accessibility evaluation tools:
- Most claim to support WCAG 2.0
- Most claim to be the best tool
- ...yet there are many variances
Developer Guidance
Current idea is to provide a framework that describes:
- Features that tools could provide
- Overall: crawl, customizable rules, ...
- Specific: ways to support SC 1.1.1, ...
- Profiles of different types of tools
Example Features I
These could be overall features that tools provide:
- Tool can crawl all web pages linked on a website
- Tool provides a way to simulate user form-inputs
- Tool can export results into bug-tracking systems
Example Features II
These could be features for WCAG 2.0 Success Criterion:
- Automatically identify missing text alternatives
- Automatically identify suspicous text alternatives
- Provide way to manually verify text alternatives
Purpose
Contribute to more consistent support for WCAG 2.0:
- Selection of features to guide tool developers
- ...selection of features to inform tool users
- Flexbile framework for different types of tools
Schedule
This work is currently just starting up (good time to get involved!):
- Q3 2013: first Working Draft
- Q1 2014: final Working Draft
- Q3 2014: first public release
Interested in contributing? Please contact us!
Get Involved in WAI
Using WAI resources and contributing to WAI:
- Getting WAI highlights and updates
- WAI-Engage Community Group (CG)
- Contributing comments and feedback
- Participating in WAI Working Groups
- Sponsoring WAI and W3C Membership