Addition of 2.2

[dmundra]

Initial PR to include 2.2

[dmundra]

@maryjom and @mgifford I updated WCAG 2.2 VPAT to say 2.5 based on comment from #21 (comment).

[dmundra]

@mgifford check out the commit ba2af5f to see the small adjustments I made.

[maryjom]

@mgifford @dmundra How did you intend to cover the change in WCAG 2.2 that makes 4.1.1 Parsing obsolete and deleted? This is something the VPAT committee has not yet determined how to handle, as 508 and current EN 301 549 both include it. WCAG 2.0 and 2.1 will have an errata (published soon) that this SC is always met.

[dmundra]

@mgifford @dmundra How did you intend to cover the change in WCAG 2.2 that makes 4.1.1 Parsing obsolete and deleted? This is something the VPAT committee has not yet determined how to handle, as 508 and current EN 301 549 both include it. WCAG 2.0 and 2.1 will have an errata (published soon) that this SC is always met.

@maryjom that is a good question. Right now (just tested it) if we remove 4.1.1 from a catalog then trying to validate an openacr report will throw an error. I think the catalog schema will need to support like a deprecated flag or something similar that the validator then can use to ignore that criteria and the HTML generator would ignore that output. Quick ideas though, that might not be what is needed here.

[maggiewachs]

@dmundra @mgifford any thoughts on when this may be merged? I'm updating the CMS VPAT reports and would like to use latest (v2.5 including WCAG 2.2). Merci beaucoup!

[dmundra]

I am going to close this in favor of getting GSA#353 merged to support WCAG 2.2 and VPAT 2.5 version.