W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2016

RE: Framework Draft Skeleton - ‘WCAG as JSON’ - Data and File Requirements (and Test Procedure) that must meet WCAG 2

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Mon, 24 Oct 2016 06:44:50 -0400
To: "'Wilco Fiers'" <wilco.fiers@deque.com>, "'Manu Sporny'" <msporny@digitalbazaar.com>, "'David Ezell'" <David_E3@VERIFONE.com>, "'Janina Sajka'" <janina@rednote.net>
Cc: <public-apa@w3.org>, "'Web Payments IG'" <public-webpayments-ig@w3.org>, <public-wcag-act@w3.org>, <w3c-wai-gl@w3.org>
Message-ID: <0ea501d22de3$a66c57b0$f3450710$@gmail.com>
All,

 

(OK thanks, Wilco.)

 

I am wondering how the different W3C APIs that use JSON, such as some of the Web Payments work could utilize this WCAG/JSON for supporting the resultant UIs and data of APIs that are relevant to Accessibility.

 

One example of where there are data file WCAG2 legal requirements is in the ACA regulations in the US Federal government for Electronic Health Records (as part of the Affordable Health Care Act ACA) where there are certification and test requirements identified.

 

In plain English, the regulation/rule requires that when patients need to access/use their EHR via viewing, downloading or transmitting that the resulting files MUST be WCAG 2 Level A (or AA) conforming.

 

I provide this in my trainings for US Section 508 Coordinators and their staff:  

 

HHS Office of the National Coordinator for Health Information Technology

•       Rule adopts standards, implementation specs, and certification criteria for Electronic Health Record (EHR) technology.  ‘ <http://www.healthit.gov/providers-professionals/ehr-incentives-certification> Meaningful Use’ rules/regulations for secure exchange of information between providers and patients to support better care across the nation.  (HIPPA/HITECH and ACA)

•       WCAG 2.0 Level A for HER  (and now AA possibly posits Bruce Bailey of the Access Board)

•       Meaningful Use 42 CFR (§ 170.204(a)
 <http://www.healthit.gov/sites/default/files/2014editionehrcertificationcriteria_mustage2.pdf> http:// <http://www.healthit.gov/sites/default/files/2014editionehrcertificationcriteria_mustage2.pdf> www.healthit.gov/sites/default/files/2014editionehrcertificationcriteria_mustage2.pdf ) for certification criteria

•       Test Requirements:  <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> § <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> 170.314 <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> ( <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> e <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> )( <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> 1 <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> )  <http://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf> View, download and transmit EHR data

 

 

Specifically the Certification Test Procedure says:

 

The test procedure will evaluate the capability of the EHR technology to permit patients and their authorized representative(s) to view the provider’s name and office contact information and Common MU Data Set using ambulatory EHR technology; and the admission and discharge dates and locations, discharge instructions, and reason(s) for hospitalization, and the Common MU Data Set using inpatient EHR technology, in conformance with the Web Content Accessibility Guidelines (WCAG) 2.0, Level A Conformance standard ( <http://www.w3.org/TR/2008/REC-WCAG20-20081211/#conformance-reqs> http://www.w3.org/TR/2008/REC-WCAG20-20081211/#conformance-reqs ). Any capabilities of the EHR technology that permit patients and their authorized representatives to download and transmit health information must also be in conformance with WCAG 2.0 Level A.

​​​​​

 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

 

From: Wilco Fiers [mailto:wilco.fiers@deque.com] 
Sent: Monday, October 24, 2016 6:05 AM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Subject: Re: Framework Draft Skeleton - ‘WCAG as JSON’

 

Hi Katie,

No I hadn't, although I've actually done a similar project a while back with based on work from Michael Cooper. I't used in the WCAG-EM Report Tool.

https://github.com/WilcoFiers/wcag2json

 

Wilco

 

On Mon, Oct 24, 2016 at 12:01 PM, Katie Haritos-Shea GMAIL <ryladog@gmail.com <mailto:ryladog@gmail.com> > wrote:

Wilco,

 

Have you seen this ‘WCAG as JSON’ work from Karl Groves:  <https://github.com/karlgroves/wcag-as-json> https://github.com/karlgroves/wcag-as-json?

 

 

​​​​​

 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 <tel:703-371-5545>  |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 <tel:703-371-5545>  |  <https://twitter.com/Ryladog> @ryladog

 

From: Wilco Fiers [mailto:wilco.fiers@deque.com <mailto:wilco.fiers@deque.com> ] 
Sent: Friday, October 21, 2016 12:24 PM
To: public-wcag-act@w3.org <mailto:public-wcag-act@w3.org> 
Subject: Framework Draft Skeleton

 

Hi team,

 

I'm afraid I haven't been able to complete the draft skeleton just yet. I'll get the skeleton document to you before the next meeting but it might not be in time for you to do a full review on it.

 

-- 

Wilco Fiers - Senior Accessibility Engineer








 

-- 

Wilco Fiers - Senior Accessibility Engineer





image001.gif
(image/gif attachment: image001.gif)

Received on Monday, 24 October 2016 10:45:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:06 UTC