E-mail List Archives
Re: RFP Boilerplate for Accessibility
From: Ryan E. Benson
Date: Jan 29, 2019 6:36AM
- Next message: Barry Hill: "Native or web?"
- Previous message: Ryan E. Benson: "Re: RFP Boilerplate for Accessibility"
- Next message in Thread: Jiatyan Chen: "Re: RFP Boilerplate for Accessibility"
- Previous message in Thread: Ryan E. Benson: "Re: RFP Boilerplate for Accessibility"
- View all messages in this Thread
>How would that work? I thought the language in the RFP was to decide who
to award the contract to. Once the contract is awarded, then the
application is built, then it's tested. How could you audit something that
hasn't been written yet?
Not sure what approach they were taking, though if they mean before award,
make respondents speak about their accessibility knowledge or demonstrate
it as part of their submission package. If they meant before award, as in
before getting paid, have somebody check the deliverable for accessibility.
HHS' language closes with
(d) Respondents to this solicitation must identify any exception to Section
508 requirements. If a offeror claims its supplies or services meet
applicable Section 508 accessibility standards, and it is later determined
by the Government, i.e., after award of a contract or order, that supplies
or services delivered do not conform to the described accessibility
standards, remediation of the supplies or services to the level of
conformance specified in the contract will be the responsibility of the
Contractor at its expense.
--
Ryan E. Benson
On Mon, Jan 28, 2019 at 12:41 PM glen walker < <EMAIL REMOVED> > wrote:
> >
> > Remove 2y experience requirement for the auditor.
> >
>
> I'm curious why you would want to remove that requirement? Does that mean
> you'd be comfortable with an auditor that's only worked in the area for a
> few months?
>
> Or should the "requirement" be changed to a "recommendation"? So maybe
> changing "auditors with at least 2 years experience" to "prefer auditors
> with at least 2 years experience".
>
> Limit the scope to the applicable functions of the app (rather than the
> > entire app).
> >
>
> Not sure I follow that. The entire app needs to be accessible.
>
> The audit has to be done BEFORE the contract award.
> >
>
> How would that work? I thought the language in the RFP was to decide who
> to award the contract to. Once the contract is awarded, then the
> application is built, then it's tested. How could you audit something that
> hasn't been written yet?
>
> I like the language that the auditor can be involved in the whole
> development process, especially the design end before any code is written,
> but those skills might be beyond some auditor's skillsets. That is, some
> auditors might be proficient in finding problems in existing apps but might
> not be experienced in helping with design.
>
> Glen
> > > > >
- Next message: Barry Hill: "Native or web?"
- Previous message: Ryan E. Benson: "Re: RFP Boilerplate for Accessibility"
- Next message in Thread: Jiatyan Chen: "Re: RFP Boilerplate for Accessibility"
- Previous message in Thread: Ryan E. Benson: "Re: RFP Boilerplate for Accessibility"
- View all messages in this Thread