Please report any problems to the Shared Tools Team at    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • Coordinating Group Meeting 2017-01-12
Skip to end of metadata
Go to start of metadata

Agenda & Notes - Accessibility/Usability of IT Coordinating Group (Coordinating Group)

Jan 12, 2017, 11:00-12:00, McBurney Center, Graaskamp Rm 

  1. Agenda Review

  2. Notes from previous meeting. Please send comments and corrections to Gary.

  3. Discuss possible meeting with the team Sponsors.
    Handout: Web Accessibility Coordinating Group Timeline and Activities-2017-01-12.docx
    Examples of items for such a meeting:
    • Things we did
    • Things we're hoping to do
    • Questions for the sponsors we need answers to in order to continue
    • The team will continue to meet monthly
    • There may be activity between meetings
    • The group received initial guidance from our sponsors at this meeting, but needs some further guidance on timeframe, priorities, etc. (i.e. strategy, not the details.)
    • Possible roles for the group
      • Assist with policy revision
      • Help with selection of vendors for web accessibility-related activity (requirements? RFP Team?)
      • Assist in development of decision-trees on what needs to be made accessible in what timeframe.
        • (Could generalize this a little to include some other procedures and processes. If so, which ones?)
      • Help executives understand priorities for resource allocation.
    • Regarding web accessibility policy:
      • An upgrade from the current Section 508 standard to the new WCAG 2.0 A and AA standard has already been planned and the guidelines have been published. The corresponding policy revision is awaiting official action by the regulators.
      • A major policy revision may be needed in order to address substantive issues that the current version does not touch upon. New provisions or procedures might include such things as: training, formal liaisons/contacts, authorization to publish, accommodation and complaint procedures, decision trees for prioritizing work, and process improvement for developing and publishing web content. The actual list is TBD.
    • Regarding the "Accessibility Staffing Recommendations for UW-Madison"
      • A typical arrangement at other schools is to have three FTE's: a coordinator (leader), a training person, and a technical support person. These are typically in the IT department, with exceptions.
      • The UW-Madison recommendation was also for three FTE's, distributed somewhat differently. (Training was not identified as a separate position.)
    • Regarding long-term vs. short-term improvements:
      • Short-term, there will need to be significant effort to remediate pages that have already been published.
        • This is an expensive way to make web content accessible. This approeach is difficult to sustain. This is not a good long-term solution.
        • It's important that in the process of remediating current pages, we do not get locked into that approach for the long-term.
      • Long-term, we need to integrate web accessibility into the web development and publishing process. This has also be referred to as "Getting it right, from the beginning."
        • This is a relatively low cost and sustainable way to make content accessible.
        • The Coordinating Group has worked on this approach. There is a lot more to do.
  4. Upcoming agenda items
    • See the Feb 11 meeting notes for a sizable number of items that could be addressed at future meetings. We could select items to carry forward based on the future direction and priorities of the team.
    • See "Future Agenda Items" below.

Future agenda items: (in no particular order)

  • DoIT plans for web accessibility testing and remediation 
  • How to communicate our progress to faculty.
    • One way might be to work through the Equity and Diversity Committees that are advisory to deans and are composed of faculty and staff.

    • Accessibility and diversity are related, followup (suggested at May 1, 2014 meeting). Note: we made brief contact with Hazel Symonette at the T&LS on May 19.

  • Accessibility of email. (Campus Communicators have discussed this, see 10/30 notes.)
  • Go over the implications of the new Wisconsin law on accessibile educational materials in higher education
  • Brainstorm how to build awareness of instructional content accessibility
  • See the Feb 11 meeting notes for more.

Future Dates:

Furture meetings:

  • Coordinating Group Meeting 2017-09-11, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-09-28, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-10-12, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-10-26, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-11-09, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-11-23, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-12-14, 11:00-12:00, McBurney Graaskamp Rm
  • Coordinating Group Meeting 2017-12-28, 11:00-12:00, McBurney Graaskamp Rm (tentative) *
  • Coordinating Group Meetings

* Tentative meeting on Dec 28, between the holidays.

Coordinating Group members:

Sandi ArendalkowskiDoIT MarketingSteven BoldtDCSGary De CluteCIO Office
Brendon DybdahlHousingApril EbacherDoIT ADIRyan EngelLSS
Matt GoinsDoIT PTEAndy GoldsteinDoIT ATLaura GradyDoIT Marketing
Jamie GutkowskiDoIT ADIJohn HareDoIT EIS  
Jini JastiLaw SchoolHaley KerkhoffDCSAl NemecCALS
Jessie NemecLibraries

Casey Schacher

LibrariesTodd Schwanke, (co-chair)McBurney Center
James SkempBusinessGarrett SmithDoIT ATPhyllis TreigeDoIT Marketing
Nick WeaverUniv. MarketingPeter Weil (co-chair)Univ. Marketing  
Also attendingUnitAlso attendingUnitAlso attendingUnit
Phil JochimsenDoIT EISLee KonradLibraries  
vacant, (sponsor)CIO OfficeCathy Trueba, (sponsor)Office of Compliance  




  • No labels