-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support procurement officer evaluations in the comparison tool #177
Comments
This is an important consideration because (mostly) it should be left to the government procuring official to determine that an exception is applicable. Of course, the vendor might know the regs better than the fed. Having the ACR mention, for example, that the product would always be
If any of these sort of protocols are robust enough to be public facing, that would be great.
Just to be clear, on this thread, your A/B/C/D are factors which can be graded (maybe even pass/fail). (That is, the list is not reflective of a letter grade assigned.) |
Thanks for this feedback @bruce-usab I do think that the UI could include something to remind the procurement officers about the exception is soley at the disgression of the government and not a choice for the vendor. Do you know where that decision would be recorded? Would that be part of the DHS's DART program? I don't know that the VPAT evaluations are robust enough. That said, I don't see why if government departments are using them already that the grading criteria aren't public. People need to know how they are going to be evaluated for a transparent procurement process. Even if it is as simple as, saying that ACRs will be evaluated and marked to see that a preference is given to: If vendors knew that this mattered and might make the difference in winning/losing a bid they might pay more attention. |
There is some interesting guidance from AccessibilityOZ on evaluating VPAT that might have some relevant ideas https://www.accessibilityoz.com/2019/09/how-to-read-a-vpat/ |
The exceptions are pretty clearly laid out in the Section508.gov's Determine ICT Exceptions page.
It would be useful to include a link to this, if vendors are claiming that the product/service is an exception. It would also be useful to highlight that an ACR can only be done on an existing product/service. The point of an ACR is to influence procurement decisions. Contracting could ask for a conformance report at the end of the contract (and probably should) but that should be distinct from a OPAT and should be focused on the accessibility needs of the client as expressed in the contract.
Some departments also have a grading system that is implemented informally to evaluate the quality of a VPAT. The criteria is contract-specific, but generally its:
A: VPAT 2.0 or higher
B: for the most recent version/release
C: filled out to instructions associated with the VPAT or RFP
D: provides sufficient detail in the notes and comments
Some of this could be highlighted in the comparison tool.
The text was updated successfully, but these errors were encountered: