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.


Difference between revisions of "Start with Accessibility"

From Education & Outreach
Jump to: navigation, search
m (Start with Accessibility: How to Integrate It into Web Projects)
Line 5: Line 5:
 
=Start with Accessibility: How to Integrate It into Web Projects=
 
=Start with Accessibility: How to Integrate It into Web Projects=
  
''... here Vicki - a page for a clean copy :-)''
 
  
''for at the end of each main section:''  
+
==Introduction==
 +
 
 +
Consider accessibility early and throughout the design and development process for seamless and elegant integration into web projects.
 +
 
 +
Incorporating accessibility from the start of a project increases the positive impact of designing for a broad constituency while decreasing development costs associated with accessibility when it is addressed much later.  Avoid situations in which accessibility is considered only at the end of the development process.  This often results in awkward, "tacked on" accessibility features that are much less effective for people with disabilities and less beneficial overall.  In addition, this approach - i.e. to address accessibility later and at the end of a project - can result in additional costs.
 +
 
 +
When accessibility is considered for the first time in a project, some additional steps to ensure accessibility are required, but most of the planning, design, checking and implementation will fit easily into the processes already in place. For example, instead of evaluating accessibility separately, integrate accessibility checks iteratively within the current testing and quality assurance (QA) processes. That's just one example of how integrating accessibility applies through a project.  Best practices in web design indicate that it is important to follow a systematic design process and that accessibility issues are addressed at each stage.
 +
 
 +
This resource addresses how and where accessibility fits through the lifecycle of a web project.
  
 
===<span style="color:#808080;">EOWG notes on @@section</span>===
 
===<span style="color:#808080;">EOWG notes on @@section</span>===

Revision as of 15:36, 11 February 2013

Nav: EOWG wiki main page

Previous versions and notes: Eval in process

Start with Accessibility: How to Integrate It into Web Projects

Introduction

Consider accessibility early and throughout the design and development process for seamless and elegant integration into web projects.

Incorporating accessibility from the start of a project increases the positive impact of designing for a broad constituency while decreasing development costs associated with accessibility when it is addressed much later. Avoid situations in which accessibility is considered only at the end of the development process. This often results in awkward, "tacked on" accessibility features that are much less effective for people with disabilities and less beneficial overall. In addition, this approach - i.e. to address accessibility later and at the end of a project - can result in additional costs.

When accessibility is considered for the first time in a project, some additional steps to ensure accessibility are required, but most of the planning, design, checking and implementation will fit easily into the processes already in place. For example, instead of evaluating accessibility separately, integrate accessibility checks iteratively within the current testing and quality assurance (QA) processes. That's just one example of how integrating accessibility applies through a project. Best practices in web design indicate that it is important to follow a systematic design process and that accessibility issues are addressed at each stage.

This resource addresses how and where accessibility fits through the lifecycle of a web project.

EOWG notes on @@section

  • @@comment {name}

back to contents