WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: VPAT version for AODA

for

From: Philip Kiff
Date: Mar 25, 2020 1:10PM

I'm curious about this as well. In fact, I didn't even realize that
there was a VPAT that might theoretically be used to make a claim about
compliance with the AODA or WCAG. I had always thought of the VPAT as
something related to requirements of the US government and Section 508.

Here in Ontario in Canada where the AODA applies, I can't say that I've
EVER seen anyone make reference to a VPAT other than in the context of
compliance with U.S. regulations. But maybe I've just been out of  the
loop on these things?

Lastly, Mitchell, I noticed a couple problems and limitations with the
sample VPAT documents currently available from the ITI site here:
https://www.itic.org/policy/accessibility/vpat

First, these are not formatted using the current MS Word docx file
format? I would recommend updating all files to using current docx
format. A user of such a form can't even run the rudimentary, but still
useful, built-in MS Word accessibility checker without upgrading the
file format to docx.

Second, they contain font sizes that I consider too small to be
considered accessible in a default context (11 point Calibri). I would
recommend reformatting the documents to use a minimum 12-point font
size. Possibly use Legal-size paper (landscape orientation) instead of
Letter-size paper if you want to preserve more space for user input?

Lastly, I'm not sure that Microsoft Word is even the best format for
this kind of file. Is this what everyone in the US is filling in when
they talk about VPATs? It seems to me that this is actually a fillable
form, and as such, especially given the number of tables and use of
subheadings within individual tables, I wonder if these VPAT files might
not be better formatted as accessible PDF forms? Or maybe that is what
you intend consumers of these files to do with them? Regardless, on
first impression, I have to say that they don't immediately  inspire me
to start jumping in to use them for AODA compliance.

I would welcome any corrections or clarifications on all this, however,
as I really don't know hardly anything about VPATs, and that's why I'm
wondering.

With sincere curiosity,

Philip Kiff
D4K Communications

On 2020-03-25 01:33, Mitchell Evan wrote:
> Hi Logan,
>
>> I'd like to chime in and state that if this is related to AODA, the City
> of Ottawa will not accept a VPAT as it still isn't relevant to us. We have
> vendors submit assessments utilizing the WCAG-EM Tool.
>
> I agree the WCAG-EM Report Tool
> <https://www.w3.org/WAI/eval/report-tool/#!/ > can produce excellent WCAG
> reports, but I'm curious — what aspects of VPAT 2.x
> <https://www.itic.org/policy/accessibility/vpat> have been problematic? If
> the WCAG section in VPAT hasn't worked well for Ottawa's needs, then I'd
> like to understand what's lacking and see if we can get it fixed, either in
> the VPAT template itself or in its instructions for vendors.
>
> The WCAG edition of VPAT and the International edition of VPAT might be new
> to some folks here. They are meant to help buyers and regulators compare
> accessibility reports from different vendors easily, while vendors
> shouldn't have to rewrite the same accessibility findings in multiple
> report formats.
>
> (Multiple languages, that's another matter.)
>
> Cheers,
> Mitchell
>
> Mitchell Evan
> +1 (510) 375-6104
> <EMAIL REMOVED>
> Twitter @mitchellrevan
> https://www.linkedin.com/in/mitchellrevan/
>
>