1. Kansas Partnership for Accessible Technology April 14, 2015 Meeting

2. KANSAS STATE CAPITOL KIOSKS Matt Veatch Assistant Division Director / State Archivist, State Historical Society

3. STATUS UPDATES AND ANNOUNCEMENTS

4. Deque University  Web accessibility training from Deque  Online and Instructor-led classes  Curriculum packages and boot camps  https://dequeuniversity.com/ https://dequeuniversity.com/

5. AMP Training  Held another AMP Training session last month  Trained 13 people from 10 organizations  The next session is scheduled for Thursday, June 11  Info and registration at http://oits.ks.gov/kpat/tool/training http://oits.ks.gov/kpat/tool/training

6. AMP Release  AMP has been updated to the Winter 2015 Release since we last met.  Features include:  Editable instance severity  Ability to attach screenshots to reports for individual violation instances  Info on what’s new at http://bit.ly/1HRCbifhttp://bit.ly/1HRCbif  Demo video at https://youtu.be/X0JMPrdhjVUhttps://youtu.be/X0JMPrdhjVU

7. AMP for Mobile  New product from SSB BART Group  Beta release  Tests accessibility of mobile apps and content  Tests native mobile and hybrid apps  Tests the on-device experience  Supports iOS and Android  Seamlessly integrated with AMP

8. AMP for Mobile  Partnership with IBM  Incorporates IBM AbilityLab Mobile Accessibility Checker  Offered as an add-on to the AMP Enterprise License  More information:  Home page: http://info.ssbbartgroup.com/AMPforMobile.html http://info.ssbbartgroup.com/AMPforMobile.html  Blog announcement: http://www.ssbbartgroup.com/blog/amp-for-mobile-is-here/ http://www.ssbbartgroup.com/blog/amp-for-mobile-is-here/  Press release: http://prn.to/1IKGoEzhttp://prn.to/1IKGoEz  IBM AbilityLab Mobile Accessibility Checker: http://ibm.co/1Fipboh http://ibm.co/1Fipboh  Interest?

9. Mobile Accessibility  On February 26 the W3C Mobile Accessibility Task Force published a First Public Working Draft entitled Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile.  Describes how WCAG applies to mobile, provide guidance on mobile accessibility issues, and links to WCAG Techniques that apply to mobile. Also highlights the relevance of UAAG and ATAG to mobile.  Document: http://bit.ly/1AOSDxnhttp://bit.ly/1AOSDxn  Blog announcement: http://www.w3.org/blog/news/archives/4447 http://www.w3.org/blog/news/archives/4447

10. DOJ ANPRM Accessibility of Web Information and Services of State and Local Governments  Listing in the Fall 2014 Reginfo.gov agenda changed the date for NPRM from unspecified August to unspecified December.  http://go.usa.gov/3D9SF http://go.usa.gov/3D9SF

11. DOJ ANPRM & NASCIO  However, NASCIO issued an inquiry April 2 about the proposed rule, introducing it and seeking feedback on burden, economic impact, costs of assessment and remediation, and compliance data.  It also stated: “The proposed rule is currently at the Office of Information and Regulatory Affairs (OIRA), located within the White House Office of Management and Budget. OIRA is conducting its own review of the rule and must sign off before DOJ can issue the proposed rule for public comment.”

12. Other NASCIO Activity  Earlier, in January, NASCIO announced a list of four federal advocacy priorities for 2015, the second of which is to modernize outdated federal regulations impacting state IT.  I responded by suggesting that the Section 508 / ICT Refresh be included in that, to which representatives from Massachusetts, Minnesota, Texas, Oregon, and Utah expressed agreement, and which the NASCIO Director of Government Affairs and Executive Director acknowledged.  (This was before the announcement of the NPRM.)

13. PDAA  Upon seeing my message, a few of the other state representatives reached out to me to include me in a network of state accessibility officers/directors that they are trying to build.  In particular, they shared with me a project they’ve been working on that is designed to help vendors improve the accessibility of their products over time, called Policy Driven Adoption for Accessibility (PDAA).  Overview presentation at http://go.usa.gov/3DXNm http://go.usa.gov/3DXNm

14. STATE ADA COORDINATOR REPORT Anthony Fadale State ADA Coordinator

15. ICT STANDARDS AND GUIDELINES

16. ICT Standards and Guidelines  Proposed Information and Communication Technology (ICT) Standards and Guidelines  Notice of Proposed Rulemaking (NPRM) published in February  Latest stage in the rulemaking process for the update, or “refresh”, of the federal Section 508 standards and Section 255 guidelines  Updates accessibility requirements for ICT in the federal sector covered by Section 508 and, jointly, telecommunications equipment subject to Section 255

17. Timeline  §255 guidelines effective (1998)  §508 standards effective (2001)  Refresh process starts (2006–2008): TEITAC  TEITAC report: April 2008  Advance notice and first draft text released: March 2010  Advance notice and second draft text released: December 2011  Proposed rule submitted to OMB: February 2014  Proposed rule released for public comment: February 2015

18. Next Steps  Public comment period  42 questions  Ends May 28, 2015  Analyze comments  Develop final rule  Develop regulatory assessment  Submit to OMB for review  Publish final rule in the Federal Register  FAR Council incorporates new Section 508 rule into Federal Acquisition Regulations

19. Documents Released  Proposed Rule  http://go.usa.gov/3Wcd5 http://go.usa.gov/3Wcd5  Overview of the Rule  http://go.usa.gov/3Wcvk http://go.usa.gov/3Wcvk  Regulatory Assessment  http://go.usa.gov/3WcvG http://go.usa.gov/3WcvG  News Release  http://go.usa.gov/3WcfT http://go.usa.gov/3WcfT  Public Comments Docket  http://go.usa.gov/3Wcf9 http://go.usa.gov/3Wcf9 All of these are available on the main ICT Refresh page at http://go.usa.gov/3WcfA.http://go.usa.gov/3WcfA

20. Structure and Organization  Similar format to ADA and ABA Accessibility Guidelines  Advisories and links to technical assistance provided  Adopts functionality-based approach vs. product categories

21. Structure and Organization  Single document for both 508 standards and 255 guidelines  Two Application and Administration chapters  One for each rule  508 = E, 255 = C  Two Scoping chapters  One for each rule  Common chapters:  Chapter 3: Functional Performance Criteria  Chapter 4: Hardware  Chapter 5: Software  Chapter 6: Support Documentation and Services

22. Highlighted Issues  Broad application of WCAG 2.0  Incorporated by reference  Delineation of covered electronic content  Public and non-public facing  Expanded interoperability requirements  Software compatibility with AT  Requirements for RTT functionality  Real-Time Text

23. Broad Application of WCAG 2.0  Incorporation of WCAG 2.0 Success Criteria by reference  Propose to also apply WCAG Success Criteria to software and some offline electronic documents  E205 Content  E205.4 Accessibility Standards  Content must conform to Level A and Level AA Success Criteria and Conformance Requirements specified for Web pages in WCAG 2.0 (incorporated by reference in Chapter 1) or, where applicable, ISO 14289-1 (PDF/UA-1) (incorporated by reference in Chapter 1).  E207 Software  E207.2 WCAG Conformance  User interface components, as well as the content of platforms and applications, must conform to Level A and Level AA Success Criteria and Conformance Requirements specified for Web pages in WCAG 2.0 (incorporated by reference in Chapter 1).

24. Delineation of Covered Electronic Content  Covers “Agency Official Communication” that is:  E205.2 All public facing content: such as websites, posted documents, blog posts, agency social media  E205.3 Eight categories of non-public facing electronic content covered 1.An emergency notification 2.An initial or final decision adjudicating an administrative claim or proceeding 3.An internal or external program or policy announcement 4.A notice of benefits, program eligibility, employment opportunity, or personnel action 5.A formal acknowledgement or receipt 6.A questionnaire or survey 7.A template or form 8.Educational or training materials  Exception: Only for National Archives and Records Administration (NARA)

25. Delineation of Covered Electronic Content  Content “broadly disseminated throughout an agency” was dropped from the 2011 draft.  An exception for draft materials was dropped from the 2011 draft.  The rationale is that public-facing content should be accessible regardless, and non-public facing drafts won’t fall within the eight categories anyway.

26. Expanded Interoperability Requirements  Proposed rule describes required compatibility of covered technologies, including operating systems, software development toolkits, and software applications with assistive technology.  502.2 Documented Accessibility Features  502.2.1 User Control of Accessibility Features  502.2.2 No Disruption of Accessibility Features  502.3 Accessibility Services  502.3.1 Object Information  502.3.2 Row, Column, and Headers  502.3.3 Values  502.3.4 Label Relationships  502.3.5 Hierarchical Relationships  502.3.6 Text  502.3.7 Actions  502.3.8 Focus Cursor  502.3.9 Event Notification  502.4 Platform Accessibility Features

27. Requirement for RTT Functionality  Real-time text functionality (text that is transmitted character by character as it is being typed) for products providing real-time, two-way voice communication  410.6.1 Display of Real-Time Text  410.6.2 Text Generation  410.6.3 Interoperability  410.6.3.1 PSTN  410.6.3.2 VoIP Using SIP  410.6.4 Voice Mail, Auto-Attendant, and IVR Compatibility  410.6.5 HCO and VCO Support

28. Functional Performance Criteria  Functional performance criteria apply when there are gaps in the technical requirements and when evaluating equivalent facilitation.  This is a reversal from the 2011 ANPRM, which proposed to require conformance to the functional performance criteria in all cases, and is consistent with the existing standards.

29. Miscellaneous Notes  “… an updated product accessibility template that includes WCAG 2.0 and the other referenced standards… available through the GSA Section508.gov site…. We expect GSA will update this tool so that it will be available for use by agencies on or before the effective date of revised 508 Standards.”  E202.6.1 proposes to require that agencies document in writing the basis for determining that ICT fully conforming to applicable 508 Standards is not commercially available.

30. KPAT Response  Decide whether we want to submit a comment  Previous first and second draft comments available: 1.http://go.usa.gov/nDLhttp://go.usa.gov/nDL 2.http://go.usa.gov/PIWhttp://go.usa.gov/PIW  Public comment period ends May 28, 2015.  Determine policy revision recommendations for adopting the new rule when it goes into effect  ITEC Policy 1210  Other ICT

31. ACCESSIBILITY STATUS OF STATE OF KANSAS WEBSITES

32. Assessment  Matches last year’s for direct comparison  182 entity home page domains, as represented in the Agencies & Associations Listing page on the Kansas.gov website (with corrections and a few additions)  Spidered each site up to 50,000 pages  Automated testing

33. Pages  886,877 pages scanned  385,989 last year

34. Numbers of Violations 20132014 Δ Total Violations3,205,7628,897,447 Average Violations Per Page8.3010.03 ↑ 1.73

35. Violation Severity 20132014Δ High Severity Violations1,768,937(55%)3,849,439(43%)↓ 12% Medium Severity Violations212,193(7%)3,667,034(41%)↑ 34% Low Severity Violations1,224,632(38%)1,380,974(16%)↓ 22%

36. Most Frequent Violations (by Pages Affected) Best PracticeViolations Percentage of Pages with ViolationSeverityNoticeabilityTractability 1. Ensure link text is meaningful within context (–) 2,881,976 54% (0%) 662 2. Ensure the language of a document is set (1) 407,859 46% (46%) 162 3. Provide alternative text for images (2) 2,170,588 30% (32%) 10 2 4. Ensure text can be resized (12) 87,080 24% (5%) 358 5. Provide valid, concise, and meaningful alternative text for image buttons (5) 301,10119% (10%) 682 Last year’s info in parentheses

37. Most Frequent Violations (by Violation Count) Best PracticeViolations Percentage of Pages with ViolationSeverityNoticeabilityTractability 1. Ensure link text is meaningful within context (–) 2,881,976 54% (0%) 662 2. Provide alternative text for images (3) 2,170,588 30% (32%) 10 2 3. Avoid unnecessary use of heading elements (2) 814,490 8% (10%) 332 4. Provide valid labels for form fields (5) 671,125 19% (20%) 1062 5. Avoid the sole use of device dependent event handlers (4) 625,29510% (5%) 872 Last year’s info in parentheses

38. Most Severe Violations Best PracticeViolations Percentage of Pages with ViolationSeverityNoticeabilityTractability 1 (T). Provide alternative text for images (1(T)) 2,170,588 30% (32%) 10 2 1 (T). Provide valid labels for form fields (1(T)) 671,125 19% (20%) 1062 1 (T). Ensure headers and cells are properly associated (1(T)) 1,170 0% (0%) 1074 4 (T). Provide alternatives for server- side image maps (4(T)) 1,359 1% (0%) 988 4 (T). Avoid utilizing sub-tables in header elements (4(T)) 1,034 0% (1%) 935 Last year’s info in parentheses

39. Most Tractable Violations Best PracticeViolations Percentage of Pages with ViolationSeverityNoticeabilityTractability 1 (T). Provide alternative text for images (1(T)) 2,170,588 30% (32%) 10 2 1 (T). Provide valid labels for form fields (1(T)) 671,125 19% (20%) 1062 1 (T). Avoid the sole use of device dependent event handlers (1(T)) 625,295 10% (5%) 872 1 (T). Provide valid, concise, and meaningful alternative text for image buttons (1(T)) 301,101 19% (10%) 682 1 (T). Ensure frame titles are meaningful (1(T)) 118,147 9% (8%) 762 1 (T). Ensure link text is meaningful within context (–) 2,881,976 54% (0%) 662 1 (T). Ensure hr elements utilize relative sizing (1(T)) 2,042 0% (0%) 422 1 (T). Avoid unnecessary use of heading elements (1(T)) 814,4908% (10%) 332

40. OPEN DISCUSSION

41. Next Meeting Tuesday, July 14, 2015 Time: 2:30–4:30 PM Location: Landon State Office Building Room 509 900 SW Jackson Street