Hi,

I have been a tester for a small project that required accessibility. In terms
of development, I believe that there is some adition in terms of testing time
but I would suspect that this is simply a part of regular testing. Also, this
was a unique situation where my employer had been asked to develop a virtual
laboratory. In this case, some amount of additional research was required to
make it accessible. Having said all of the above, roughly speaking, the time
added to make a project accessible would not be more than two or 3%. The two or
3% figure comes in because of the time taken to test and research unique
accessibility requirements. If the requirements are standard, then I doubt that
any additional time would be involved since all one really has to do to
incorporate accessibility is to use standard interfaces.

Pranav 

-----Original Message-----
From: Equal Access to Software & Information [mailto:[log in to unmask]] On
Behalf Of Jennison Asuncion
Sent: Thursday, March 01, 2007 5:48 PM
To: [log in to unmask]
Subject: development time and accessibility

(*Apologies for the cross-posting.)

Hello,

I am interested to here 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. I was recently
quoted a statistic thatstated that this activity added  8 to 10% on a project's
development time.

Does this statistic hold true?

Thanks,
Jennison