EASI Archives

Equal Access to Software & Information: (distribution list)

EASI@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0
Sender:
Equal Access to Software & Information <[log in to unmask]>
Subject:
From:
Joe Clark <[log in to unmask]>
Date:
Sun, 18 Mar 2007 15:13:51 -0500
In-Reply-To:
Content-Type:
text/plain; charset="us-ascii" ; format="flowed"
Reply-To:
Equal Access to Software & Information <[log in to unmask]>
Parts/Attachments:
text/plain (17 lines)
>I am interested to [hear] from folks who have actually gone through 
>the exercise of planning for, costing and implementing 
>accessibility-related activities into a web development project as 
>part of their project's life cycle.

Your question is a bit too vague. Do you mean a brand-new project, a 
remediation to bring a tag-soup site (like a bank's, for example) to 
a level of extremely minimal compliance, or a complete 
standards-compliant redesign?


-- 

     Joe Clark | [log in to unmask]
     Accessibility <http://joeclark.org/access/>
     Expect criticism if you top-post

ATOM RSS1 RSS2