Please report any problems to the Shared Tools Team at    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • ITAccessCG Meeting 2015-10-22
Skip to end of metadata
Go to start of metadata

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

Oct 22, 2015, 11:00-12:00, McBurney Center, Graaskamp Rm

  1. Agenda Review

  2. Notes from the  previous meeting. Please send comments or changes to Gary.

  3. Discussion of AMP capabilities.
    Questions/issues to address, implied by the discussion:
    • For which users on campus is AMP among the right tools for their situation?
    • AMP, like any tool, will have limitations, some of which will take long time to reduce, and some might never be reduced. How do we play to the strengths of AMP, without getting blocked by the weaknesses?
  4. Discussion of accommodation response process.
    Questions/issues to address, implied by the discussion:
    • Discussion highlighteed the need to have a response process. (Not the same as a complaint process, although we need a complaint process too.)
    • When a site or applications is not sufficiently accessible, how do we as an institution respond?
      • Start with the unit that publishes/maintains the web resource.
      • If they can bring it to a reasonably satisfactory conclusion, great!
      • If they can't resolve it. What then?
    • What about communicating our existing informal response process?
      • If the unit can't resolve it, the unit can contact for advice.
      • Still leaves us with the question: if that advice is not sufficient to resolve it, what then?
  5. Discussion of how making things accessible ties into usability.
    Questions/issues to address, implied by the discussion:
    • Not always clear if it is a usability problem or an accessiblity problem.
    • Not always enough information. Not always possible to get enough information.
    • Are we communicating enough about usability and relationship between usability and accessibility?
  6. Discussion about standards-based approach to making things accessible.
    Questions/issues to address, implied by the discussion:
    • Laws prohibit discrimination. That get's interperted into: follow this or that standard.
    • Compliance with standards does not equal compliance with the law – it helps with compliance.
    • Standards-based approach can distract service providers from considering the needs of their entire community of users.
      • Example: a perception that if we can't make a tool accessible we have to stop using it.
      • Not necessarily. Instead, could provide an alternative that is sufficiently functional, timely, etc. so that offering it as an alternative is not discrimination, it's accomodation.
    • Is our campus policy taking the right approach?
  7. Getting it Right, From the Beginning - Documenting processes and best practices during Phase I (all) (55 minutes)
    • Handouts: Web Accessibility Workflow - Drafts, Web Accessibility Workflow - AssumptionsAccessible Development and Publishing Phase I Project.
      Will break into small groups at Oct 22 meeting to discuss selected cases.
    • Objective: Draft some workflows for different types of sites and development processes
    • Background information:
      (From OCT 01)
      • Discussed the list of cases. Are there any missing? Duplicates? Idea is to cover case that occur on campus. Don't have to cover every possible case.
      • Documenting the different cases is what Phase I is about.
      • If the documented process is new or is an improvement to an existing process, it needs to be tested in actual use.
      • Deliverable for Phase I is a group of documented and tested processes intended to help units improve their own process.
    • Discussion: 
    • Action:
      • Keep improving the work flows between meetings. See "handouts" above.

  8. Check in on other open action items: (OCT 22: ALL ARE POSTPONED UNTIL LASTER MEETINGS)

    1. IT Policy Forum on Accessibility 8/5/2015 debrief
      • Objective: Incorporate discussion results into our work
      • Background information:
        • Is related to "Getting it right, from the beginning" agenda item (see above)
        • Is related to "Online course accessibility policies" agenda item (see below)
        • Is related to "Accessibility policy draft & edits" agenda item (see below)
      • Discussion:
      • Next Steps:
    2. Accessibility content & new site (Todd & Phyllis)
      • Objective:
      • Background information:
      • Discussion: Deferred.
      • Next Steps:
    3. Accessibility complaint procedure (Todd & Gary)
      • Objective:
      • Background information:
      • Discussion:
      • Next Steps:
    4. Commitee membership (Todd)
      • Objective: Options for short, middle, and longer-term sustainability of the committee
      • Background information:
      • Discussion:
        • Consider sending a message via MTAG, inviting units to appoint someone to the Coordinating Group.
        • Nature of a volunteer based group
        • Campus need for a sustained and cohesive effort
        • Unknown future of new positions
      • Next steps:
    5. Captioning Contract (Sandi Arendalkowski, Todd Schwanke)

      • Objective:
      • Background information:
      • Discussion:
      • Next Steps:
        • What are next steps?

        • What can the committee contribute?

    6. Online course accessibility policies (Todd)
      • Objective:
      • Background information:
        • Receiving regular questions about what the policy is related to online courses and interpretations of the web policy
        • Dealing more directly with what should be done proactively vs. as an accommodation, and with what is practical or not.
        • August IT Policy discussion notes address this. See policy forum agenda item above.
      • Discussion:
      • Next Steps:
    7. Accessibility policy draft & edits (Todd & Gary)
      • Objective:
      • Background information:
      • Discussion:
      • Next steps: 
    8. Enhanced voiceover PowerPoints (Todd)
      • Objective:
      • Background information:
      • Discussion:
        • What tools are in this space?  - Articulate Storyline, Adobe Captivate, Adobe Presenter, others
        • How can a tool be identified that meets the needs/preferences of designers, instructors, students (including those with disabilities)
        • Determine what can be done to move ahead in this critical area
      • Next Steps: 
    9. Browser support trends, accessibility, and policy context (Todd)
      • Objective:
      • Background information:
      • Discussion: Deferred.
      • Next Steps:
    10. Unizin & Courseload accessibility follow-up

      • Objective:
      • Background Information:
      • Discussion:
      • Next Steps (from Aug 6):
        • Possible sub-committee to assist Bruce in assuring Unizin and related systems are accessibile.
        • Discuss in future.
  9. Upcoming agenda items
    • See "On Deck Items", "Future Agenda Items" below.

Future agenda items:

  • Get more info on new Executive Committee meeting (invite Chris Holsman to a meeting?) (12/4 note: Check with Phyllis on this item.)
  • 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 (suggested at April 17, 2014 meeting)
  • Brainstorm how to build awareness of instructional content accessibility (suggested at May 29 meeting)
  • Brainstorm "Resources to help developers and content providers to incorporate accessibility into their existing processes" (suggested at March 6, 2014 meeting) 

Future dates:

  • National Disability Employment Awareness Month – October, 2015, see   
  • Accessing Higher Ground conference – Nov 2015 (will be the week before Thanksgiving), see:  
  • Report to the sponsors – December 31, 2015. 
  • Community of Educational Technology Support (ComETS) annual meeting – January 2016, see:  
  • Workshop sponsored by the Coordinating Group – Tentatively: March 3, 2016 
  • Report to the sponsors – March 31, 2016. 
  • Showcase –  April 2016
  • Teaching and Learning Symposium – May 2016
  • Report to the sponsors – June 30, 2016.
  • Report to the sponsors – September 30, 2016.

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  





Thank you for registering to attend the webinar. You should receive a confirmation email with login details shortly. If you do not receive a confirmation email, please contact

For more information on AMP for Mobile, please contact

  • No labels