IT Policy Forum

August 5, 2015

Copyright © 2015 Board of Regents of the University of Wisconsin System

1

Bob TurnerChief Information Security Officer

2

1. Welcome

Bruce MaasUW-Madison CIO, and

Vice Provost for Information Technology

3

2. Introduction

Web Accessibility is Important

• It says something about who we are

4

Get it right – from the beginning

• Wise use of resources• Requirements gathering• Design for accessibility• Make a habit of efficient and effective

practices

5

A Team Effort

• Everyone who publishes content on the web needs to do their part

6

3. Web Accessibility Testing Tools

a. Overview of tools and plans

Todd SchwankeMcBurney Disability Resource Center

7

IT Accessibility Coordination

• Web and Mobile Accessibility/Usability Coordinating Group (a.k.a. Accessibility Coordinating Group)

• Since 2012• Ongoing group• Representatives from a variety of units• Open membership• Meets every two weeks

8

Mission

• Coordinate selection & deployment of web and mobile accessibility tools

• Coordinate overall efforts to improve web and mobile accessibility at UW-Madison

• Raise awareness• Current emphasis is on public-facing web

pages

9

Web Accessibility TestingTools Service

• DoIT service• Released July 1st, 2015• Culmination of three years of:

– Requirement s gathering– Research– Configuration– Testing

10

Featured Enterprise Tool

• Accessibility Management Platforms (AMP)• From SSB Bart Group• Software as a Service• Site license for all faculty/staff and students• NetID login enabled• KB Documentation• Help Desk Support

11

Supplementary Tools

• Web-based evaluation tools (free)+ Functional Accessibility Evaluator (FAE 2.0)+ Web Accessibility Evaluation Tool (WAVE)

• Mix of Firefox, Chrome and IE tools (free)

12

Why AMP?

• Supports a distributed organizational model• Thorough UI documentation• Excellent documentation on how to repair

problems (best feature)• Support from the vendor• Training materials available

13

Next steps

• UW-Madison has deployed a major evaluation tool, but we need to use it wisely

• Work on integrating accessibility into the web development and publishing process– Fixing it after the fact is the least effective and

efficient way. We can’t afford that model.– “Get it right – from the beginning” is much more

efficient and effective.

14

b. Demonstration of AMP

Al NemecCALS

15

c. IT Accessibility Priorities

Gary De CluteOffice of the CIO

16

Policy

• Web Accessibility Policy + Web pages must meet “Section 508” standard+ Websites must have an accessibility contact+ Units must respond to requests from people with

disabilities who need assistance in accessing material

17

Prioritizing Pages

• Policy implementation sets priorities for which pages to work on first:+ Top 20% of pages used+ Core institutional information and functions+ Pages needed by people with disabilities in order

to participate

18

Change is Coming

• “Section 508” will change in the next two to three years

• Will adopt WCAG 2.0– Better for people with disabilities– More complex to understand and implement

• Start working toward WCAG 2.0

19

Prioritizing within WCAG 2.0

• Not all guidelines are equally important• Some things are not adjustable by CMS users• Newly published UW-Madison guidelines

help with prioritizing• Perfect is the enemy of good enough• 80/20 rule – stop when you get to

diminishing returns

20

Starting Points

• For anyone who is publishing on the web• Nine key guidelines, divided into three

sections:+ Organization – when designing a page or site+ Text and Images – when entering content+ Audiovisual – when using audio and video

• Goes a long way toward making pages accessible – but not a “stopping point”

21

For CMS users

• Two additional documents for CMS users+ Web Accessibility for Users of Content

Management Systems+ Forms and Frames Supplement

• Organized the same as the “starting points”

22

Designed for CMS users

• Only includes features CMS users can typically adjust

• Avoids references to HTML whenever possible

• Features are listed in priority order (roughly)• In some cases the user is referred to the

webmaster

23

For Web Developers

• Two additional documents for web application and website developers– Web Accessibility for Web Developers– Forms, Frames and Advanced Topics

• Organized the same as the “starting points”

24

Designed for Web Developers

• Lists all accessibility guidelines in WCAG 2.0• References extensive technical resources at

W3C• Guidelines are listed in priority order

(differs somewhat from the CMS users)• Also states what the CMS users were told

25

Summary

• Policy prioritizes within websites:+ Top 20%+ Core institutional information+ Enable people with disabilities to participate

• Guidelines prioritize within WCAG 2.0+ Start with the “Starting Points”+ The rest is in priority order+ Stop when you get to diminishing returns

26

• Break up into two or three small groupsOne group for “Web Accessibility PolicyOne or two groups for “Integrating Web

Accessibility…”• Appoint a note taker• Report back some top items at the end• Please give the full notes to Gary

27

4. Discussion Groups

5. Report Back from Discussion Groups

Please report the top items you discussed

28

6. Invitation to Participate Further

• Try out the Accessibility Management Platform (AMP) and other tools. Let us know what you think.

• Send feedback about the policy, guidelines and procedures. Please send feedback to accessibility@cio.wisc.edu.

• Help campus with "getting it right, from the beginning". Participate in the Accessible Development and Publishing Phase I Project.

29

Invitation Continued

• Help guide UW-Madison's IT accessiblity program. Join the Web and Mobile Accessibility/Usability Coordinating Group.

• Share your experience. Join various interest lists on which accessibilty is discussed.

• Raise the issue of accessibility in other interest lists or organizations you are a member of.

30

5. ClosingPlease fill out the evaluation

Policy Planning TeamCo-chairs: Jennifer Bonifas (SMPH)

Bruno Browning (L&S)Gary De Clute (CIO Office)Peg Eusch (Records Mgt)Laura Grady (Communications)

, Jason Erdmann (Education)

Phil Hull (EM)Noel Kim (Engineering)Lee Konrad (Libraries)David Parter (Computer Science)

31

• General contactpolicy@cio.wisc.edu

• Gary De Clutegary.declute@wisc.edu

http://www.cio.wisc.edu/policies/https://wiki.doit.wisc.edu/confluence/display/POLICY/

IT accessibility contact: accessibility@cio.wisc.edu

Thanks!

Future Forums:• Nov 2015• Feb 2016• Apr 2016

32