University Councils and Committees
Page tree

Accessibility ICT Policy Council 
Tuesday, August 10, 2021
3:00 - 4:00 PM
Zoom (Please see Outlook Invite for Details)

Members Present: Lisa Andreotta, Donna Carelli, Melanie Domanico, Angela King Taylor, Vince Patriarco, Brian Tibbens, and Scott Warren

Co-chairs: Jenny Gluck and William Myhill


Minutes: Christian Jones


  1. Welcome/Announcements (Jenny, William)
    1. Membership
      • Angela has accepted a position at University of Missouri as the associate dean of students. A new Council member to join on Angela’s behalf is being determined. 
      • We are still looking for a faculty member to join the Council. 
      • Scott will be traveling for business during the next 2 meetings.
    2. Update from 8/6 Discussion with Purchasing
      • 2021.07.20 AICTPC-Purchasing Subcommittee Minutes
      • Vince met with Jean Gallipeau today to discuss the changes to the Policy, which she agrees with. Vince will work with Jenny and William on the wording for these changes. 
      • We have a plan on how to approach the 2 processes. They’ll try to put those together and bring ideas around workflow back to the group for input. 
      • Purchasing is continuing to develop the procedures manual, in which we can specify what needs to happen when campus community members buy software.
      • They also spoke about possible changes in PeopleSoft, itself, which would change workflow. We will look closer at that to assess if it will help the campus 
      • William added that there are multiple entry points for procurement, instead of a centralized purchasing model. It would be helpful to identify all of the entry points so we can understand where we could be missing things/where the gaps might be, and decide on how to address them. 
      • We have plans to follow up early in the semester and continue the dialogue.
  2. Review Table of Recommendations (Group)
    1. AICTPC Table of Recommendations 
      1. Any questions?
  3. Recommendations 
    1. Recommendation 7a: The University intends to use ATAG (Authoring Tool Accessibility Guidelines) 2.0 to ensure that authoring tools are capable of producing accessible content. (Jenny, William)
      1. Review Authoring Tool Coverage Table (Recommendation 7a)
      2. Solicit other authoring tools to include
      3. Defining “authoring tool” and “web content” within the context of the Syracuse University community
        • In the last meeting (7/27 Meeting), we were wrestling with what we meant by “authoring tool,” as well as by “web content” which ties into the definition of authoring tool. We’ve mapped out some examples in the table linked in hopes that we can work through some of these and try to come up with guidance for the Policy. 
        • The definition listed below this table for authoring tool references the W3C language. Is this as narrow as the focus is for this standard? If so, what do we do about non-HTML stuff? 
        • It would seem that content that exists on the web should be considered “web content,” but it seems that there are exceptions. 
        • Scott noted that not everything on the web is created on the web - it’s not on the web until it’s on the servers connected to the web. We can create documents using a variety of tools and the content may/may not end up being web-based. If that content is loaded onto a platform that has a web presence or put on a server, then we’re talking about web-based content. 
        • How you engage with content (browser-based or a predefined application) matters. If you are engaging with the content through a web client, it should be considered a web app. If you require a stand-alone application or app environment to use it, that puts it into the application realm. 
        • So we agree that if you can view and engage with content within a browser, it can be considered web content. If you have to open another tool view/engage with content, it is no longer web content. 
        • A browser is something that reads HTML. Flipgrid is not a browser as you have to be inside Flipgrid to look at a Flipgrid file. 
          • It may render content in a browser, but that doesn’t mean it’s HTML.
          • If I use a browser and I’m looking at an HTML file and an image within, I’m seeing that image because the HTML is sharing to that browser. An image still needs to be evaluated. 
        • Brian noted that there is a distinction between web content and web API’s (application environments). We can build Flipgrid content, which works in a browser, but it’s an application environment. PeopleSoft is also an application environment. We’re going to run into bottlenecks with this. 
        • An application environment is essentially a website within the web. For example, you’re using Firefox/Safari/etc. to access MySlice/PeopleSoft, etc. but in reality, it’s encapsulated in its own box and doesn’t have to follow the rules of HTML because it’s using Javascript; it’s using other applications to manage that environment and make it work. 
        • There are also self-contained authoring tools that work with mathematical/scientific equations. 
        • You can use some authoring tools to create queries. You’re not going to create content separate from the system, you’ll create content in order to run queries against an information corpus. The authoring tool is embedded inside the database that frames that corpus of information. 
          • It’s not the same as what we’ve talked about with authoring tools where you’re authoring something independent of an underlying set of information. 
          • Example: Reaxys - a web-based database of chemical information, allows you to draw chemical structures. 
        • Perhaps we should add a column to indicate whether or not a tool is an authoring tool. 
        • The group used the remainder of the meeting time to go through the draft table examples.
  4. Next/Future Meeting
    1. Wrap up defining an authoring tool and continue with the table.
    2. Next Recommendations
    3. Language

Supplemental Materials:

Accessibility ICT Policy 

Accessibility ICT Policy - Working Document

 Standards Table for AICTPC (Draft)

Draft Legacy Software Reference Guide

Ongoing Issues to Address

  1. Glossary of Terms
  2. End of Exception Cycle
    1. The exception is only good for the term of the version. How long is the life of the exception? What triggers a review of the product?
  3. Auto-renewals
  4. Vendor-deliverables 
  5. Review of DERC Phase 2 Recommendations Communications with Council (available in the Restricted Resource Library to AICTPC members)

  6. Review Purchasing procedures manual and the Purchasing website
  7. Recruiting graduate student and associate dean-level membership
  8. WCAG Review - 1 vs 3 years

Next Meeting: Tuesday, August 17th,  2021  

  • No labels