E-mail List Archives
Thread: wording for accessible design in RFP
Number of posts in this thread: 5 (In chronological order)
From: James L Bailey
Date: Mon, Jun 27 2011 10:18AM
Subject: wording for accessible design in RFP
No previous message | Next message →
My school is a blend of in-house web design and using off-campus
contractors. We want to add language to our RFPs that include the
requirement for accessible web design. Does anyone have suggestions?
Thanks in advance.
--
Best regards,
James
--
James Bailey M.S.
Adaptive Tech Coordinator
University of Oregon
From: Keith Parks
Date: Mon, Jun 27 2011 10:39AM
Subject: Re: wording for accessible design in RFP
← Previous message | Next message →
On Jun 27, 2011, at 9:17 AM, James L Bailey wrote:
> My school is a blend of in-house web design and using off-campus
> contractors. We want to add language to our RFPs that include the
> requirement for accessible web design. Does anyone have suggestions?
>
The website for the California State University Chancellor's Office has a page with information related to procurement:
<http://www.calstate.edu/Accessibility/EIT_Procurement>;
Of particular interest might be the second document on the list "Information for Vendors".
******************************
Keith Parks
Graphic Designer/Web Designer
Student Affairs Communications Services
San Diego State University
San Diego, CA 92182-7444
(619) 594-1046
mailto: = EMAIL ADDRESS REMOVED =
http://www.sa.sdsu.edu/communications
http://kparks.deviantart.com/gallery
----------------------------------------------------------
Yes We Can!*
*should not be interpreted to mean that we necessarily will
From: Michael.Moore
Date: Mon, Jun 27 2011 12:33PM
Subject: Re: wording for accessible design in RFP
← Previous message | Next message →
We have a standard contract clause that we use at Texas HHS
http://architecture.hhsc.state.tx.us/myweb/Accessibility/website/word/HHSUniformEIRAccessibilityClause.doc
We take a warrantee approach so that the vendor will be responsible for the cost of any repairs needed to bring a resource into compliance.
Michael Moore
From: Mark Magennis
Date: Tue, Jun 28 2011 3:57AM
Subject: Re: wording for accessible design in RFP
← Previous message | Next message →
James,
The Accessible ICT Procurement Toolkit (www.universaldesign.ie/useandsupply/ict/itprocurementtoolkit) gives suggested text for including in RFPs, which it calls Requests for Tender (RFTs). You'll find it in the 'Writing an RFT' section. It has different texts for different technologies, including websites. It's aimed at the Irish public sector but should be equally relevant to you too. Make sure you cover everything in your RFP, not just the accessibility of the website content. For example, if you're getting a content management system with your website, you'll want to specify that it should produce accessible code and possibly also be accessible to any content managers with disabilities, so you'll be talking abut ATAG compliance as well as WCAG or 508. You might also consider specifying a universal design process for the development, including stages of user input and user testing involving people with disabilities. All this is included in the Procurement Toolkit which cove
rs the whole procurement process, from writing an RFP, through development, implementation and ongoing maintenance. Accessibility is affected by every stage and they can all be addressed in the RFP.
Mark
Dr. Mark Magennis
Director of the Centre for Inclusive Technology (CFIT)
NCBI Working for people with sight loss
Whitworth Road, Dublin 9, Republic of Ireland
Tel: +353 (0)1 882 1956
Skype: markncbi
Web: www.cfit.ie
On Jun 27, 2011, at 9:17 AM, James L Bailey wrote:
> My school is a blend of in-house web design and using off-campus
> contractors. We want to add language to our RFPs that include the
> requirement for accessible web design. Does anyone have suggestions?
>
NCBI: Celebrating 80 Years
********************************************************************
National Council for the Blind of Ireland (NCBI) is a company
limited by guarantee (registered in Ireland No. 26293) .
Our registered office is at Whitworth Road, Drumcondra, Dublin 9.
NCBI is also a registered Charity (chy4626).
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
From: Mark Magennis
Date: Tue, Jun 28 2011 7:09AM
Subject: Re: wording for accessible design in RFP
← Previous message | No next message
Sorry, that link was wrong.It should have been http://www.universaldesign.ie/useandapply/ict/itprocurementtoolkit.
Mark
On 28 Jun 2011, at 09:01, Mark Magennis wrote:
> James,
>
> The Accessible ICT Procurement Toolkit (www.universaldesign.ie/useandsupply/ict/itprocurementtoolkit) gives suggested text for including in RFPs, which it calls Requests for Tender (RFTs). You'll find it in the 'Writing an RFT' section. It has different texts for different technologies, including websites. It's aimed at the Irish public sector but should be equally relevant to you too. Make sure you cover everything in your RFP, not just the accessibility of the website content. For example, if you're getting a content management system with your website, you'll want to specify that it should produce accessible code and possibly also be accessible to any content managers with disabilities, so you'll be talking abut ATAG compliance as well as WCAG or 508. You might also consider specifying a universal design process for the development, including stages of user input and user testing involving people with disabilities. All this is included in the Procurement Toolkit which co
ve
> rs the whole procurement process, from writing an RFP, through development, implementation and ongoing maintenance. Accessibility is affected by every stage and they can all be addressed in the RFP.
>
> Mark
>
> Dr. Mark Magennis
> Director of the Centre for Inclusive Technology (CFIT)
> NCBI Working for people with sight loss
> Whitworth Road, Dublin 9, Republic of Ireland
>
> Tel: +353 (0)1 882 1956
> Skype: markncbi
> Web: www.cfit.ie
>
>
>
> On Jun 27, 2011, at 9:17 AM, James L Bailey wrote:
>
>> My school is a blend of in-house web design and using off-campus
>> contractors. We want to add language to our RFPs that include the
>> requirement for accessible web design. Does anyone have suggestions?
>>
>
>
> NCBI: Celebrating 80 Years
>
> ********************************************************************
> National Council for the Blind of Ireland (NCBI) is a company
> limited by guarantee (registered in Ireland No. 26293) .
> Our registered office is at Whitworth Road, Drumcondra, Dublin 9.
> NCBI is also a registered Charity (chy4626).
>
> NOTICE: The information contained in this email and any attachments
> is confidential and may be privileged. If you are not the intended
> recipient you should not use, disclose, distribute or copy any of
> the content of it or of any attachment; you are requested to notify
> the sender immediately of your receipt of the email and then to
> delete it and any attachments from your system.
>
> NCBI endeavours to ensure that emails and any attachments generated
> by its staff are free from viruses or other contaminants. However,
> it cannot accept any responsibility for any such which are
> transmitted. We therefore recommend you scan all attachments.
>
> Please note that the statements and views expressed in this email
> and any attachments are those of the author and do not necessarily
> represent the views of NCBI
>
>
> ********************************************************************
>
>
>
>