Events Archive
U Webmasters Bi-Monthly Forums
Topic: Accessibility and Community Priorities
Presenters: Barb Iannucci (Director, Digital Strategy & CRM), UTS
Date: September 17, 2026
This session focused on accessibility compliance progress, community survey feedback, font licensing awareness, and future Community of Practice priorities. Participants discussed accessibility support needs, common vendor accessibility issues, AI-generated content and code, chatbot initiatives, and emerging challenges facing campus web professionals.
Files:
AI Meeting Notes
Generated by AI. Be sure to check for accuracy.
Meeting notes:
- Accessibility Compliance And Support: Barb reviewed the extended ADA Title II timeline, noted that accessibility progress
in Axe Monitor has plateaued, and gathered feedback from Henry, Kim, Miranda, and
others on targeted training, remediation, testing, and support for remaining complex
cases.
- Compliance Timeline: Barb explained that the ADA Title II compliance deadline was extended to next April and is now approximately halfway through the extension period. Although substantial progress occurred before the original deadline, Axe Monitor scores have remained steady in recent months; Barb asked teams to continue remediation rather than defer work until next spring.
- Software Review Priorities: Barb described the university’s third-party accessibility review process. They review software purchased through the software-purchasing process when it meets applicable thresholds or is intended for multiple departments, but cannot assess every VPAT. Review prioritization considers factors such as user volume and whether faculty, staff, or students are the primary users, with student-facing applications receiving particular priority.
- Accessibility Training Needs: Henry requested workshops or training on document remediation and explained that the law school has addressed most straightforward web and document issues but needs help with unusual cases, such as complicated tables in published law-review articles. Henry recommended workshops or office hours where teams can discuss ambiguous examples with an expert; Barb agreed that support should focus on the remaining complex or idiosyncratic cases.
- Future Support Model: Survey feedback identified accessibility resources and training as the community’s most valued offering, while accessibility compliance, content governance, AI, outdated content, and limited staffing were major challenges. Barb proposed separating in-depth accessibility training from regular forums through office hours, workshops, tooling guidance, prioritization support, case studies, and success stories; Kim supported separate trainings, and Miranda suggested identifying remaining gaps as teams polish and future-proof their sites.
- Digital Content Requirements: Barb answered Michelle’s questions that accessibility requirements apply to digital materials distributed by email and social media, including one-off PDFs and private contracts, not only public websites. Public and broad-audience content should be prioritized first because it carries greater exposure, but teams should inventory all digital materials, document prioritization, and maintain a plan for remediation.
- Inaccessible PDF Alternatives: Barb advised that the preferred approach is to publish only an accessible PDF. If an inaccessible version must remain available, the organization should provide an accessible alternative or an easy way for someone to request assistance, such as a replacement format or guided support; an inaccessible document without an accommodation mechanism does not meet the minimum practical standard discussed.
- Web And Vendor Accessibility Issues: Barb, Emily, and Matt discussed accessibility issues involving Trumba, Tableau embeds,
and Kaltura/MediaSpace videos, with the web team offering to investigate reported
problems and share implementation guidance when relevant fixes are available.
- Trumba Feeds: Matt asked whether accessibility issues in Trumba feeds had been investigated. Emily said the team had not encountered recent issues and that Shelly had been working to make the feeds fail gracefully; some fixes depend on Trumba itself. Barb asked participants to report specific problems so the team can relay them to Trumba support, particularly for Trumba’s JavaScript-based widgets or “spuds.”
- Kaltura Remediation: The team reported ongoing work with Digital Learning Technologies on accessibility issues in Kaltura, also referred to as MediaSpace, streaming-video embeds. Emily said Adam Stewart may need to add code on the provider side before the university can implement the solution. Barb said they would post details after Roger returns and clarify whether sites in the central environment will be updated by the central team or require local action.
- Vendor Questionnaire: Michelle requested a copy of the third-party vendor accessibility questionnaire. Barb committed to posting it in the Teams channel, after MaRc explained that posting to the team channel rather than the meeting chat may avoid permission problems.
- Font Licensing And Spam Prevention: Barb raised the university’s move away from Monotype fonts and advised teams to verify
font licensing, while Peter asked about potential reCAPTCHA usage charges and Emily
described an alternative spam-prevention tool being tested with FormAssembly.
- Monotype Licensing: Barb explained that Monotype has contacted organizations about commercial-font licensing and that centrally managed university themes have moved away from Monotype fonts. Teams outside centrally managed Modern Campus, UMC WordPress, or similar environments should review their fonts, consult brand.utah.edu for approved university fonts, and verify licensing restrictions related to usage or traffic volume. Issues already raised by UMC should continue to be handled with UMC.
- Healthcare Drupal Fonts: In response to Sophie’s question about Drupal fonts, Barb said that Acquia-hosted healthcare websites are expected to have strong branding and licensing controls, but they did not confirm the specific font inventory and recommended treating the environment as likely managed while verifying details if needed.
- reCAPTCHA Usage: Peter asked whether Google’s move toward cloud-based reCAPTCHA could create charges if a bot exceeds the included usage allowance. Barb and Emily had not encountered such licensing issues; Emily said FormAssembly was testing an alternative called Altra, partly because reCAPTCHA had still allowed significant spam. Barb committed to checking with engineering and following up with Peter about usage limits and licensing.
- AI In Web Content And Chatbots: Barb used the survey discussion to explore AI use cases, chatbots, and AI-generated
code, while Daniel, Leah, Emily, Mark, and others described campus chatbot efforts
and risks from inserting unreviewed generated code into managed web systems.
- AI Learning Priorities: Barb asked whether the community’s interest in AI centered on practical use cases, content creation, accessibility applications, chatbots, or content-agent integration. The discussion identified a need for more information about enterprise chatbot options and campus AI initiatives, with Caprice’s rescheduled AI update expected to provide a broader UTS perspective.
- Campus Chatbots: Barb identified Swoop on the Undergraduate Studies website as a chatbot powered by Mainstay and suggested that Caprice could clarify whether an enterprise chatbot solution is available or planned. Daniel said a separate Ubot effort was intended to guide users toward graduate and undergraduate studies and help them explore majors, but they could not confirm whether it replaced the existing Mainstay chatbot. Lisa mentioned possible Delphi work with departments, and Barb offered to investigate those efforts.
- AI-Generated Code Risks: Leah explained that content editors have used AI-generated code to create visual tables outside the CMS design system and have also embedded scripts for automation, raising security concerns. Emily confirmed that the web team has seen people immediately add AI-generated code to sites, causing accessibility issues. Barb instructed content editors to avoid adding custom code to template-driven CMSs unless it is reviewed, because it can conflict with template code and introduce accessibility or other technical problems.
- Chatbot Development: Mark reported that their department director is developing a work-in-progress chatbot at code.hci.utah.edu. The tool is behind a login and undergoing security testing, and its intended function is advanced search across the Huntsman Cancer Institute website and help systems. Barb asked Mark to provide future updates.
- Developer Tools Question: Peter asked whether users could use a browser Developer Tools console to submit AI-generated content back to a CMS database. Barb said their understanding was that Developer Tools changes are local to the browser and asked whether anyone knew of a mechanism that would post those changes to the server; no confirmed method was provided during the meeting.
- Community Engagement And Communication: Barb welcomed newer members, reviewed the community’s purpose and survey feedback,
and explored better ways to distribute Teams updates and resources without causing
notification fatigue.
- Community Orientation: Barb welcomed Sophie as a newer participant and explained that the community shares best practices, web-landscape updates, accessibility guidance, training, and support. They noted that the group includes both long-standing and newer members and should account for differing levels of familiarity.
- Survey Findings: Barb reported 11 survey responses and said the community most valued accessibility resources and training, Webmaster Forum presentations, community announcements, and recorded sessions. Future topic preferences centered on AI, content strategy, UX, and usability, followed by accessibility, governance, and project showcases; major reported challenges included accessibility compliance, AI and web content, keeping content current, limited staffing, and content governance.
- Teams Notifications: Barb said the Enterprise Web Advisory Council had reported that some staff do not receive or notice Teams channel updates. They acknowledged the tradeoff between visibility and notification fatigue and asked participants to suggest alternatives, including other ways to communicate important resources and announcements.
- Resource Distribution: Barb encountered permission problems when sharing survey and accessibility documents through Teams. They successfully reposted the survey through the Teams channel and meeting chat, confirmed that Abbey could access it, and planned to use the same channel-based approach for the third-party accessibility questionnaire.
- Rescheduled AI Campus Update: Barb postponed Caprice Post’s planned AI update because of a scheduling conflict
and intends to reschedule it for a future forum, likely the next session.
- Rescheduling Plan: Caprice Post was unable to attend because of a scheduling conflict, so the planned campus AI update did not occur. Barb said the session would be rescheduled, probably for the next forum, and closed by reiterating that Caprice is expected to address campus AI activity, UTS initiatives, and upcoming enterprise developments.
Follow-up tasks:
- reCAPTCHA Licensing: Investigate whether the university’s engineering teams or FormAssembly have encountered usage limits, licensing requirements, or potential charges for reCAPTCHA, and report the findings to Peter. (Barb)
- Accessibility Questionnaire: Post the third-party vendor accessibility questionnaire in the Teams channel so community members can access it. (Barb)
- Kaltura Accessibility Updates: Share details in the Teams chat about the Kaltura/MediaSpace accessibility fix, including whether website owners need to add code on their side. (Barb)
- AI Chatbot Landscape: Ask Caprice and relevant campus teams about enterprise chatbot solutions, including the status of Swoop, Ubot, Delphi initiatives, and other chatbot efforts, for discussion at the rescheduled AI update. (Barb)
- Accessibility Support: Develop separate accessibility training or office-hour resources focused on advanced remediation cases, testing tools, prioritization, and remaining compliance gaps. (Barb)
- AI Content Governance: Define a future forum topic addressing AI-generated code added to CMS design systems, including its accessibility and security risks. (Barb)
- Chatbot Project Updates: Provide future updates to the community on the progress and security testing of the HCI chatbot project. (Mark)
Topic: Certificate Changes and Keeping Your Sites Secure
Presenters: Dave Packham (Director of Identity & Access Management) and Dustin Udy (Associate Director of Security Assurance), UTS
Date: July 16, 2026
This session covered the university's transition to CertiNext, including certificate migration, domain validation, automation, and shorter certificate lifecycles. Attendees also learned about web security and vulnerability management tools available to help identify and reduce security risks.
Files:
AI Meeting Notes
Generated by AI. Be sure to check for accuracy.
Meeting notes:
- Transition from Sectigo to CertiNext for SSL Certificates: Dave Packham explained the university's transition from Sectigo to CertiNext for SSL
certificate management, detailing the timeline, automation requirements, and changes
to certificate lifetimes, with support from the IAM team including Tina and Ryan.
- Transition Timeline and Key Dates: Dave outlined that the transition from Sectigo to CertiNext was announced on April 7, 2026, with access to the Sectigo portal ending on July 17, 2026. Existing certificates remain valid until expiration, but after December 31, 2026, all new certificates will have a maximum validity of 90 days, requiring more frequent renewals.
- Automation and ACME Protocol: Dave emphasized the need for automation in certificate renewal due to the shortened certificate lifetimes, recommending the use of ACME protocol clients for automated certificate issuance and renewal. The IAM team is providing API keys and tokens for CertiNext, and a ServiceNow document with guidance and ACME client options was shared.
- Changes to Certificate Management Process: With the move to CertiNext, the web UI for certificate management will be disabled, and all certificate requests must be processed through CertiNext using automation or a ServiceNow form for one-off certificates. Manual processes previously available through Sectigo are no longer supported.
- Wildcard and Subject Alternate Name (SAN) Certificates: Dave clarified that wildcard certificates for the entire utah.edu domain are not allowed due to security risks, though third-level wildcards are still permitted. He also noted a current CertiNext limitation of 100 SANs per certificate, which is being addressed for teams with larger needs.
- Support and Next Steps for Departments: The IAM team, including Tina and Ryan, is reaching out to departments with existing Sectigo logins to assist with the transition, collect managed domain lists, and provide necessary credentials for CertiNext. Departments are encouraged to renew certificates before December 31, 2026, for a longer validity period and to prepare for automation.
- Impact on Technical Teams and Centralized Services: Barb and Dave discussed how centralized teams such as UTS, Modern Campus, UMC, and
the NOC are handling certificate automation for their managed environments, reducing
the burden on individual webmasters and content editors.
- Centralized Certificate Management: Barb assured that teams working with UTS in Modern Campus or UMC in WordPress will have certificate management handled for them, so content editors and webmasters in these environments do not need to take action regarding the CertiNext transition.
- Automation for Load Balancers: Dave mentioned that teams like the NOC and Kim's web team are working on automating certificate renewals for F5 load balancers, and suggested that moving standalone servers behind load balancers could further streamline the process.
- Best Practices for Certificate and Key Management: Dave provided guidance on public key infrastructure best practices, including the
protection of ACME credentials and SSL/TLS private keys, and cautioned against the
broad use of wildcard certificates.
- ACME Credential Security: Dave advised IT admins to treat ACME HMAC EAB credentials as sensitive secrets, recommending the use of secure vaults like BeyondTrust Secret Safe and limiting access to only necessary personnel.
- Private Key Protection: He stressed that SSL/TLS private keys must never be shared and should be generated and stored securely on the systems where they are used, with unique passwords and secure storage.
- Risks of Wildcard Certificates: Dave explained that wildcard certificates increase risk exposure due to their broader coverage and higher-value private keys, and recommended using host-specific certificates with automation instead.
- Web Security and Vulnerability Management Tools: Dustin Udy presented on web security and vulnerability management, highlighting available
tools such as Qualys, CIS Security, and OWASP, and discussed the importance of regular
scanning and following best practices.
- Security Assurance and Vulnerability Management: Dustin described his team's role in managing security assurance, vulnerability management, and attack surface management, and emphasized the need for departments to protect their web content and infrastructure.
- Best Practices and Resources: He recommended resources such as CIS Security benchmarks, OWASP Top 10, and Wordfence for WordPress plugin vulnerabilities, all available to university members for improving web security.
- Risks of Non-University Managed Hosting: Dustin warned about the risks of hosting websites outside university-managed infrastructure, including lack of security controls, shared risk profiles, and limited ability for the ISO to assist in case of compromise.
- Qualys Web Application Scanning: He introduced Qualys as the university's primary vulnerability management tool, available for web application and OS scanning, and explained how to request access via ServiceNow.
- Vulnerability Management Policy and Registration: Dustin reminded participants of the requirement to scan or be scanned under the university's vulnerability management policy, and encouraged teams to ensure their servers are registered in the network assignments database for effective incident response.
- Security Implications of AI and Rapid Vulnerability Discovery: Barb and Dustin discussed the impact of AI on the security landscape, with Dustin
noting the acceleration of zero-day vulnerability exploitation and the increasing
speed of vendor patch releases.
- AI-Driven Security Challenges: Dustin explained that AI is making it more difficult to defend against threats, as zero-day vulnerabilities are now exploited within hours of discovery, and vendors are releasing patches at an unprecedented rate.
- Importance of Defensive Layers: He recommended using load balancers and, ideally, web application firewalls (WAFs) to provide additional layers of defense, though noted that a WAF is not currently available at the university.
- Vendor Patch Management: Dustin highlighted the increased frequency of security patches from major vendors like Microsoft, Adobe, Apple, and Oracle, and stressed the need for teams to stay current with updates.
- Peer Sharing of Security Tools and Practices: Jared shared that their team uses Burp Enterprise for security scanning, and Dustin
discussed its features and cost, encouraging open discussion of tools and practices
among participants.
- Alternative Security Tools: Jared mentioned the use of Burp Enterprise for web security scanning, and Dustin acknowledged its capabilities and cost, noting that it has been considered for centrally hosted environments.
Follow-up tasks:
- SSL Certificate Transition Preparation: Submit requests and lists of domains managed for SSL certificates to the IEM team to be set up in the new CertiNext environment and receive API key and token for automation. (All departments managing SSL certificates)
- Network Assignments Registry Update: Review and update the network assignments page to ensure IP addresses of servers are correctly registered for security contact purposes. (All website/server owners)
- Vulnerability Scanning Access: Request access to the Qualys platform via the ServiceNow catalog item to enable vulnerability scanning of web applications and operating systems. (Interested web application owners)
- Web Registry Utilization: Register websites in the web registry to ensure the security team is aware of all active sites for monitoring and vulnerability management. (All website owners)
Topic: From Panic to Plan - Making the Most of the ADA Title II Extension
Presenter: Barb Iannucci, Director of Digital Experience & CRM, University Technology Services
Date: May 21, 2026
The ADA Title II deadline has been extended to April 26, 2027, giving teams much-needed breathing room. In this session we talked about how to use it wisely with a phased, practical Accessibility Roadmap. Participants walked away with a clearer plan, smarter priorities, and (hopefully) less stress heading into 2027.
Files:
AI Meeting Notes
- Accessibility Compliance Roadmap and Deadline Extension: Barb led the meeting to clarify the implications of the accessibility compliance deadline
extension to April 2027, emphasizing that expectations and risks remain unchanged,
and outlined a phased, sustainable roadmap for university-wide progress involving
webmasters.
- Deadline Extension Clarification: Barb explained that while the accessibility compliance deadline has been extended to April 26, 2027, the requirements for accessibility remain in effect, and the risk of complaints or lawsuits persists; the extension allows for a more strategic approach rather than last-minute fixes.
- Phased Roadmap Overview: Barb presented a four-phase plan: Phase 0 (ownership determination), Phase 1 (triage and easy wins), Phase 2 (process improvement and prevention), Phase 3 (strategic cleanup focusing on high-impact pages), and Phase 4 (validation and ongoing maintenance), aiming for sustainable progress rather than perfection.
- Shared Responsibility Across Teams: Barb highlighted that accessibility is a shared responsibility across UTS, UMC, webmasters, and editors, with support teams handling templates and global components, while content managers control much of the accessibility through their daily work.
- Success Criteria and Ongoing Maintenance: Barb defined success as having accessible core content, fewer PDFs, and effective processes, stressing the importance of ongoing validation, manual testing, and maintenance to prevent regression and avoid future panic.
- Axe Monitor Usage and Accessibility Data: Barb provided an update on Axe Monitor's deployment, noting nearly 1,000 sites configured,
an average automated accessibility score of 74%, and active engagement from 257 users,
while emphasizing the limitations of automated testing and the need for manual checks.
- Automated Testing Progress: Barb reported that Axe Monitor has nearly 1,000 sites configured, with an average automated accessibility score of 74%, representing significant progress but not full compliance.
- Limitations of Automated Testing: Barb clarified that automated testing covers only about 50% of accessibility issues, and reaching 100% in automated scores does not guarantee full accessibility, underscoring the need for manual testing.
- User Engagement Metrics: Barb shared that out of 377 users, 257 have actively logged in, checked their scores, performed remediation, and rescanned their sites, indicating widespread participation.
- Distributed Responsibility and Site Coverage: Barb described the distribution of accessibility work across UTS, UMC, enterprise apps, health websites, and miscellaneous scans, facilitated by naming conventions in Axe Monitor for site identification.
- PDF Accessibility Challenges and Solutions: Jason, Roger, Barb, and others discussed the difficulties of managing PDF accessibility
errors, filtering them in Axe Monitor, alternative tools like Form Assembly for accessible
forms, and ongoing evaluation of PDF remediation tools.
- Filtering PDF Errors in Axe Monitor: Roger demonstrated how to filter PDF-related errors in Axe Monitor, showing users how to view, sort, and identify issues specific to PDFs, including page counts and URLs.
- Alternative Tools for Accessible Forms: Barb recommended Form Assembly as an accessible online forms tool, offering integration with Google Cloud and email, and noted its strong accessibility compliance as a reason for selection.
- PDF Remediation Tool Evaluation: Barb and Roger discussed ongoing evaluation of automated PDF remediation tools beyond Adobe Acrobat, expressing hope for campus-wide adoption to improve PDF accessibility.
- Strategies for Managing Large PDFs: Peter shared a solution using a custom crawler to index all PDF files and create an accessibility page listing them with disclaimers and contact information, suggesting dedicated accessibility pages as an expedient approach.
- Manual Accessibility Testing and Advanced Compliance: Kevin raised questions about manual testing and advanced accessibility requirements
for web applications, with Barb confirming the need for documentation and planning,
and noting limited campus resources for manual testing, but offering to follow up
for support.
- Advanced Accessibility Challenges: Kevin described the complexity of achieving compliance with WCAG criteria such as reflow, keyboard interaction, and dynamic content, which often require architectural changes rather than simple styling fixes.
- University Approach to Major Remediation: Barb advised documenting known issues and creating reasonable remediation plans based on team constraints, noting that the deadline extension was granted due to the scale and resource limitations faced by universities.
- Lack of Centralized Manual Testing Resources: Barb acknowledged the absence of a dedicated campus resource for manual accessibility testing, though the Office for Disability and Access has assisted with global components, and promised to follow up with Kevin and others needing support.
- Peer Collaboration and Tool Sharing: Peter offered to share a custom crawler tool that aids in manual review and triage, highlighting its visual and HTML mapping features for error identification and remediation, and invited others to contact them for access.
- Axe Monitor Access and Content Management System Features: Barb explained the process for granting Axe Monitor access to webmasters, described
CMS features like Dependency Manager in Modern Campus for tracking PDF links, and
noted similar functionalities may exist in other systems like WordPress.
- Axe Monitor Access Setup: Barb stated that webmasters assigned to sites in the website registry are automatically granted Axe Monitor access, and additional access can be requested from UTS or UMC teams.
- CMS Tools for PDF Link Tracking: Barb described the Dependency Manager feature in Modern Campus for identifying which pages link to PDFs, and suggested that similar features are likely available in other content management systems.
- Tools for Pre-Upload PDF Accessibility Testing: Cam, Barb, Roger, and Abbey discussed the limitations of Axe DevTools and Wave for
pre-upload PDF accessibility testing, recommending PAC as a free tool for PCs and
noting ongoing search for better solutions.
- DevTools and Wave Limitations: Abbey clarified that Axe DevTools and Wave browser extensions cannot scan PDFs before upload, as they only work with HTML pages.
- PAC Tool Recommendation: Roger recommended PAC, a free PC-based tool for scanning PDFs, as an alternative to Adobe Acrobat for pre-upload accessibility checks.
- SharePoint Document Access Issues: Michelle raised concerns about SharePoint permissions, with Barb committing to resolve
access issues and distribute the necessary document to the group.
- SharePoint Permissions Resolution: Barb acknowledged frustration with SharePoint permissions and promised to reattempt posting the document, ensuring correct access settings for distribution.
- Campus Map Accessibility Inquiry: Miranda asked about accessible solutions for classroom maps, with Barb indicating
that campus map enhancements are on the roadmap and promising to follow up with relevant
information.
- Classroom Map Accessibility Plans: Barb noted that the campus map development team may be working on mapping specific classrooms and will investigate further to provide Miranda with a suitable solution.
- PDF Error Filtering Support: Work with Jason to provide guidance or a list on filtering PDF-related errors in Axe Monitor and share relevant screenshots in the Teams channel for broader reference. (Roger)
- Campus Map Accessibility Inquiry: Investigate whether the campus map development team has a solution for accessible building and classroom maps and follow up with Miranda regarding alternatives to image-based PDFs. (Barb)
- SharePoint Document Access: Re-attempt posting the referenced document in SharePoint with correct permissions and ensure distribution to all relevant participants. (Barb)
- PDF Pre-Upload Accessibility Tools: Research and recommend tools or workarounds for checking PDF accessibility before upload, and follow up with Jason and the group with findings. (Barb)
- Manual Accessibility Testing Resources: Follow up with Kevin to explore resources or support for manual accessibility testing, especially for issues not covered by automated tools, and share findings with the group. (Barb)
Topic: ADA Title II Deadline - The Final Stretch
Facilitator: Barb Iannucci, Director of Digital Experience & CRM, University Technology Services
Date: March 19, 2026
Building on our previous Accessibility Support Session, this conversation continued to focus on the real-world challenges webmasters are navigating as the April 2026 ADA Title II deadline approaches. Participants brought forward new questions, edge cases, and ongoing concerns, while working through prioritization, vendor-related issues, and common accessibility findings.
Files:
AI Meeting Notes
Generated by AI. Be sure to check for accuracy.
- Third-Party Vendor Accessibility Due Diligence: Barb led a detailed discussion on the university's responsibility for ensuring third-party
vendor tools and applications are accessible, outlining a due diligence process and
sharing a comprehensive checklist with participants including Michelle, Mark, Angie,
and others.
- University Responsibility for Vendor Accessibility: Barb explained that the university is responsible for the accessibility of all third-party vendor tools and applications used by students, staff, or the community, emphasizing the need to prioritize remediation efforts based on the impact of the tool on participation in university programs.
- Vendor Accessibility Checklist Overview: Barb introduced and reviewed a vendor accessibility checklist document, which includes an email template for contacting vendors, a list of required documentation (such as VPATs and accessibility roadmaps), and guidance on documenting product details and usage.
- Evaluating and Documenting Accessibility: The checklist instructs users to request a VPAT or conformance report, review known issues and workarounds, and document the accessibility lead's contact information; it also recommends performing a quick internal accessibility check using keyboard navigation, screen readers, and color contrast assessments.
- Risk Assessment and Final Recommendations: Barb described a stoplight model for rating accessibility risk (green, yellow, red) based on the severity of barriers and vendor responsiveness, and advised that major barriers or high-risk tools should be escalated to department heads for decision-making, with all findings and recommendations documented.
- Coordination for Campus-Wide Vendor Tools: In response to Angie's question, Barb clarified that her team manages due diligence for widely used campus tools (e.g., Nelnet, FormAssembly, Atlassian), and committed to creating a shared spreadsheet to track which vendors have been reviewed, coordinating with Aimee Elliott and encouraging departments to check before duplicating outreach.
- Accessibility Office Hours and Support Resources: Barb announced recurring virtual accessibility office hours, coordinated by UTS and
UMC, to provide support and answer questions for webmasters and staff preparing for
the Title 2 deadline, with Emily and others assisting in sharing booking links and
resource information.
- Office Hours Schedule and Booking: Barb shared that virtual accessibility office hours will be held every Friday from 11:00 AM to 1:00 PM until the Title 2 deadline, with a booking link posted in the University Webmasters Community of Practice Teams channel for participants to sign up and submit questions in advance.
- Session Structure and Expectations: Barb clarified that the office hours are intended for answering questions and helping participants overcome roadblocks in their accessibility remediation work, but are not designed for staff to remediate content on behalf of attendees.
- Additional Faculty Support: Barb directed participants to the Center for Teaching Excellence, which offers resources and Thursday office hours specifically for faculty needing help with accessible course materials and PDFs.
- PDF and Flipbook Accessibility Guidance: Barb addressed questions from Mark, Michelle, and others regarding the accessibility
requirements for PDFs, scanned documents, and flipbooks, providing guidance on remediation
priorities, exceptions, and best practices for creating accessible content.
- Flipbook Accessibility Challenges: Barb explained that PDF flipbooks, such as those created with ISSUU, often disrupt semantic structure and are generally not accessible, recommending that content be provided in accessible HTML or tagged PDF formats, and that a more accessible alternative be made available if flipbooks are used.
- Remediation of Scanned PDF Consents: In response to Mark's question, Barb advised focusing on making future patient consent forms accessible by moving to online forms, while gradually remediating older scanned image PDFs by tagging them for accessibility, starting with the most recent and frequently used documents.
- Exceptions for Pre-Existing Documents: Barb clarified that under ADA Title 2, pre-existing conventional electronic documents (such as PDFs, Word, and Excel files) uploaded before the compliance deadline are generally exempt from remediation unless they are required for participation, but this exception does not apply to videos or HTML content.
- Faculty and Staff Process Improvement: Kim raised concerns about managing large volumes of PDFs from faculty, and Barb recommended leveraging the Center for Teaching Excellence for faculty training and resources, emphasizing the importance of setting accessibility tags in source documents before PDF creation.
- Video Captioning and Audio Description Requirements: Barb clarified for participants that all videos, whether public-facing or internal,
must have captions according to WCAG 2.1 AA guidelines, and explained when audio descriptions
are required, addressing a recurring question from the group.
- Captioning Requirements for Videos: Barb stated that captions are required for all prerecorded videos with audio, regardless of whether they are public or internal, and referenced WCAG 2.1 AA guideline 1.2.2 as the standard.
- Audio Description Guidelines: Barb explained that audio descriptions are only required if visual information in the video is necessary to understand the content, such as when a presenter does not verbalize slide content that is essential for comprehension.
- Remediation Prioritization: Barb recommended prioritizing captioning for the most recent and critical videos, especially those required for participation, and working through large video collections in a triaged manner.
- Site-Wide Accessibility Banners and User Accommodation: Kim and others inquired about placing site-wide banners to communicate ongoing accessibility
improvements, and Barb relayed guidance from OGC, recommending banners focus on providing
contact information for accommodation requests rather than admitting non-compliance.
- Banner Messaging Recommendations: Barb advised that banners should not state the site is non-compliant, but instead offer a clear avenue for users to request alternative accommodations if they encounter barriers, and committed to drafting approved wording for the community.
- Color Contrast and Template Updates: Larissa and Roger discussed issues identified by axe monitor regarding color contrast
in web templates, with Barb confirming that the team will review and address these
concerns as needed.
- Template Color Contrast Issues: Barb and Roger agreed to investigate and update web templates to resolve color contrast issues reported by axe monitor, and requested specific examples from Larissa to facilitate the process.
- Vendor Cooperation and Documentation of Accessibility Barriers: Mark raised concerns about uncooperative vendors like Atlassian regarding accessibility
documentation, and Barb advised documenting all issues and refusals, applying pressure
where possible, and noted ongoing efforts to obtain VPATs for such tools.
- Handling Uncooperative Vendors: Barb recommended that departments document accessibility issues and vendor refusals to remediate, communicate the legal obligations to vendors, and escalate persistent problems, while noting that her team is actively working on obtaining VPATs for widely used tools like Atlassian.
Follow-up tasks:
- Vendor Accessibility Checklist Sharing: Resolve the permissions issue preventing some participants from accessing the vendor accessibility checklist document in the meeting chat. (Barb)
- Flipbook Accessibility Guidance: Add the official stance on flipbooks and their accessibility limitations to the digital resources websites for reference by webmasters. (Emily, Digital Experience Team)
- PDF Accessibility Resource Links: Notify Sravi and UMC that the links for the resources site dedicated to document accessibility are not working and coordinate to have them fixed. (Barb)
- Banner Wording for Accessibility Compliance: Draft a site-wide accessibility banner message, run it by OGC for approval, and post the approved wording to the community for use by webmasters. (Barb)
- Third-Party Vendor Due Diligence Coordination: Create and share a spreadsheet in the Teams channel listing campus-wide third-party vendor tools and the status of accessibility due diligence, coordinating with Amy Elliott and relevant departments. (Barb)
Topic: Accessibility Support & Therapy Session
Facilitator: Barb Iannucci, Director of Digital Experience & CRM, University Technology Services
Date: January 15, 2026
For this Accessibility Support Session, we focused on the real questions webmasters are navigating as we prepare for the ADA Title II accessibility deadline. The conversation created space to share challenges, ask questions, and talk through where additional guidance or support would be most helpful in the months ahead. The session emphasized open discussion and practical insights to help teams feel more prepared as accessibility expectations continue to evolve.
Files:
Topic: Accessibility, AI, and What Today’s Trends Mean for Campus Websites
Presenter: Barb Iannucci, Director of Digital Experience & CRM, University Technology Services
Date: November 20, 2025
For this webmasters forum, Barb discussed how accessibility, AI, and emerging web trends are reshaping the way we maintain campus websites. We looked at why accurate, accessible content is more important than ever, how AI-driven search changes what users see, and what these shifts mean as we prepare for the 2026 Title II deadline. The session connected high-level trends with practical next steps for keeping your site healthy and up to date.
Files:
Topic: Understanding the U's Brand Updates
Presenter: Scott Troxel, Director of Digital Strategy, University Marketing & Communications
Date: September 18, 2025
For this webmasters forum, Scott walked us through the University of Utah’s recent brand updates, including the new interlocking U logo, expanded color palette, and updated typeface. He covered when to use the interlocking U versus the Block U, what changes apply to college and department logos, and how these updates align with Strategy 2030.
Files:
Topic: Your Accessibility Ally - Getting to know Axe Monitor
Presenter: Abbey Allen, Web Developer and Content Support Specialist, Web Support & Usability, USS/UTS
Date: July 17, 2025
For this webmasters forum, Abbey introduced Axe Monitor, the University of Utah’s new accessibility auditing tool. This platform helps website owners identify, track, and resolve accessibility issues—supporting both usability and our campus-wide compliance efforts. Whether you’re just getting started with accessibility or looking for a more efficient way to manage it, this session will give you the tools and guidance to move forward confidently.
Files:
Topic: Web Accessibility in Action - Basic Principles, Strategies, and Fixes
Presenter: Leah Donaldson, User Experience & Web Developer and Garrett Ward, User Experience Assistant, J. Willard Marriott Library
Date: May 15, 2025
In this forum, Leah Donaldson and Garrett Ward explored key principles of web accessibility—screen reader options and use, keyboard navigation, proper use of headers, writing good alt text, and color contrast tools. They also walked through real-life examples of troubleshooting and resolving problems on their own library websites, highlighting practical strategies and tools to apply in your own work.
Files:
Topic: Creating Accessible PDFs - Best Practices for Word Docs and PowerPoint
Presenter: Sravi Garikipati, Associate Director of Digital Research & Operations, University Marketing & Communications
Date: March 20, 2025
In this forum, Sravi Garikipati provided practical strategies and actionable techniques for creating accessible documents in Microsoft Word and PowerPoint, with a focus on converting them into compliant PDFs for web distribution.
Files:
Topic: Accessible PDFs - Best Practices for Compliance and Usability
Presenter: Amanda Babcock, Associate Director, Center for Disability and Access
Date: January 16, 2025
In this forum, Amanda Babcock, Associate Director for the Center for Disability and Access, shared her expertise on accessibility standards, creating accessible PDFs, and understanding when they are the right choice for your content. We also learned when to avoid using PDFs and how to ensure they meet accessibility requirements when they are necessary.
Files:
Topic: ADA Title II Updates and Campus Plan - Q&A and Discussion
Presenter: Barb Iannucci, Director of Web Support & Usability, USS / UTS
Date: November 21, 2024
In this forum, Barb Iannucci, Director of Web Support & Usability in USS/UTS, provided a brief recap of recent updates to Title II of the Americans with Disabilities Act (ADA). She also presented an initial draft of a campus plan and facilitated a Q&A session.
Files:
Topic: ADA Title II Updates and Practical Accessibility Testing
Presenter: Barb Iannucci, Director of Web Support & Usability, USS / UTS
Date: September 19, 2024
In this forum, Barb Iannucci, Director of Web Support & Usability in USS/UTS, gave an overview of recent updates to Title II of the Americans with Disabilities Act (ADA). These updates mandate that universities ensure their web content and mobile apps meet WCAG 2.1 AA standards by April 24, 2026. Practical techniques for accessibility testing were also demonstrated.
Files:
Topic: Information Security Policy Updates
Presenter: Trevor Long, Director of Governance, Risk and Compliance (GRC), Information Security
Office (ISO) / UTS
Date: July 18, 2024
In this forum, guest presenter Trevor Long, Director of Governance Risk and Compliance (GRC) in UTS' Information Security Office (ISO) provided an overview and conducted a Q&A session on recent updates to the University of Utah Information Security Policy (4-004),
Files:
Topic: WebAIM Accessibility Training
Presenter: Jonathan Whiting, Director of Training, WebAIM
Date: May 16, 2024
In this forum, guest trainer Jonathan Whiting from WebAIM spent an afternoon covering basic web accessibility principles and what you need to know to ensure that your web site meets legal guidelines and international standards.
Files:
Topic: Writing for the Web
Presenter: Amanda Crittenden, Assistant Head for User Experience and Web Development, J. Willard
Marriott Library.
Date: March 21, 2024
In this forum, guest presenter Amanda Crittenden of User Experience and Web Development at the Marriott Library explores techniques for crafting and sustaining user-centric web content.
Files:
Topic: Online Forms - Data Privacy and HIPAA
Presenter: Chris Keller, Information Privacy Manager, Compliance Services
Date: January 18, 2024
In this forum, guest presenter Chris Keller of Compliance Services discusses data privacy and HIPAA. Afterward there was a great discussion about how the protection of data applies to online web forms for campus.
Files:
Topic: Branding
Presenter: Scott Troxel and Dave Titensor, University Marketing and Communications Digital Team
Date: November 17, 2023
In this forum, guest presenters Dave Titensor and Scott Troxel of University Marketing and Communications (UMC) discuss the recently updated University Brand website brand.utah.edu.
Files:
Topic: UWebmaster 101 and New Registry Portal
Presenter: Barb Iannucci, Director of Content Management & Usability, UTS
Date: September 21, 2023
In this forum, we get back to the basics and revisit the fundamentals of what you need to know as a University webmaster. We also introduce the newly revamped website registration verification process. This session aims to empower webmasters with essential knowledge and resources while also fostering a sense of community and collaboration.
Files:
Topic: Search Engine Optimization (SEO) Tips and Training
Presenter: Jen Jenkins, Associate Director of Digital Experience, U of U Health
Date: July 20, 2023
SEO—everyone has heard of the term, but do you understand the true implications of search engine optimization? Come find out and contribute your knowledge to our webmaster group. This presentation will include an exploration of the latest updates to the Google algorithm and, it almost goes without saying, a presentation/discussion of what the new generative AI models mean for SEO.
Files:
Supporting Resources:
U of U Health Digital Experience Team's Training Resources (in Pulse)
Topic: Web Accessibility Compliance and Tips For Getting Started
Presenter: Barb Iannucci, Director of Content Management & Usability, UTS
Date: May 18, 2023
In celebration of Global Accessibility Awareness Day (GAAD), this forum focused on web accessibility compliance and included valuable tips for getting you started.
Files: