WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: VPATs for Word, PPT, Excel, etc.

for

From: Emily Ogle
Date: Jun 2, 2018 5:46PM

Well, it would seem it is entirely plausible an agency would insist on a VPAT for each deliverable, eg, Word, PPT, etc, because that's happened.

This is unexpected so I'm looking to find out what they're really expecting since we'd have to rethink our strategy by quite a bit. When I asked the DHS what the typical expectation was, I was given a link to the trusted tester page, in which there was, among several files, an 84-page document on how to test Word files for accessibility!

We're providing training on how to make PPTs etc accessible, but a VPAT for each seems like overkill.

> On Jun 2, 2018, at 11:02 AM, Duff Johnson < <EMAIL REMOVED> > wrote:
>
> So, looking for clarity here…
>
> a) Is it reasonable or plausible that an agency might demand a VPAT for each deliverable?
>
> b) Is it reasonable to expect that "deliverable" can be construed to include documents?
>
> c) That while the form of the VPAT must be explicable, the actual nature of the VPAT itself, on a per-document basis, is up to the agency (vendor, whatever), providing the document under terms that include a VPAT….yes? Seems obvious, but always best to ask.
>
> If all of these are true I have a follow-up question.
>
> Thanks.
>
> Duff.
>
>>> On Jun 1, 2018, at 22:49, Ryan E. Benson < <EMAIL REMOVED> > wrote:
>>>
>>> VPAT has the word "Voluntary" in it, which to me means "whatever you
>> want."
>>
>> This is incorrect. Yes the V is for voluntary, meaning "here's the
>> documentation without asking for it." If the government asks, you either
>> provide the PAT or risk losing the contract. The company is still able to
>> deny the request, but it's not in your best interest. In terms of Emily's
>> question, contract language [often] says provide a VPAT for all
>> deliverables. The checklists I mentioned are an alternative to a VPAT for
>> docs. These are often written in non-legalese to make things easier.
>>
>>> The government would be better served if they required certification of
>> documents files for Sec. 508 compliant (WCAG 2.0, PDF/UA-1).
>>
>> A VPAT is literally just that. It is a document that says "We, [company],
>> certify our deliverable meets these standards." As an example, HHS' has
>>
>> 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.
>>
>> Source:
>> https://www.hhs.gov/grants/contracts/contract-policies-regulations/hhsar/part-352-solicitation-provisions-contract-clauses/index.html#352.239-73
>>
>> In English, vendors must document their deliverables meet HHS' standards,
>> the government reserves the right to double check, and if the government
>> finds issues prior to acceptance, the vendor must fix it. GSA has some
>> high-level guidance to develop language like I quoted above at:
>> https://section508.gov/buy/define-accessibility-criteria.
>>
>> --
>> Ryan E. Benson
>>
>>> On Fri, Jun 1, 2018 at 4:47 PM, < <EMAIL REMOVED> > wrote:
>>>
>>> No.
>>> VPAT has the word "Voluntary" in it, which to me means "whatever you want."
>>>
>>> The government would be better served if they required certification of
>>> documents files for Sec. 508 compliant (WCAG 2.0, PDF/UA-1). Use any of our
>>> free or not-so-free tools such as:
>>>
>>> Acrobat Pro DC:2018
>>> Word and PowerPoint built-in checker
>>> Axes 4
>>> PAC-3
>>> NetCentric's Validator
>>>
>>> Generally, we find that if the file passes any combo of two of these, then
>>> it's usually ok, but of course, the best testing is done my knowledgeable
>>> humans!
>>>
>>> --Bevi Chagnon
>>>
>>> — — —
>>> Bevi Chagnon, founder/CEO | <EMAIL REMOVED>
>>> — — —
>>> PubCom: Technologists for Accessible Design + Publishing
>>> consulting ' training ' development ' design ' sec. 508 services
>>> Upcoming classes at www.PubCom.com/classes
>>> — — —
>>>
>>>
>>>