LibGuides Accessibility/Style Guide Task Force (2021-2022)

LibGuide Accessibility/Style Guide Task Force (2021-2022): The overall purpose of the LibGuide Accessibility & Style Guide Task Force is to support evidence-based changes to LibGuides for improved accessibility and usability as part of the larger web ecosystem of the Libraries, for foundation building for ongoing optimization and maintainability.  

Because this work is never ending, this group is highly focused to ensure rapid delivery without being overwhelmed. The Task Force is charged for 6 months. The work by this group will inform next steps. 

The Task Force will have 3-5 members, with at least two representatives from the Web Team and at least one representative from the Accessibility Committee. The time commitment for months 1-3 is expected to be under 2 hours per month. The time commitment for months 4-6 is expected to be under 4 hours per month. 

Members: 

  1. Web Team + Accessibility Committee: Matthew Daley 
  2. Accessibility Advisory Committee: Danielle Johnson 
  3. Accessibility Advisory Committee: Sakuna Saengow (Chair)
  4. Web Team: Gus Clifton 
  5. Web Team: Will Chaney 

Todd Digby, Chair of Library Technology Services and Laurie Taylor, Senior Director for Library Technology & Digital Strategies, liaise with this group on an ongoing basis to support its work and ensure best outcomes for all stakeholders.  As the leaders, they review each recommendation for improvement and validation. Then, Todd/Laurie will present each recommendation to Joint Chairs, again for improvement and validation, and implementation as applicable. 

Dates and Expectations for Deliverables 

Month 1: Jan. 2022 

Establishing group norms for communication 

Recommendation on font size and colors for contrast1, including whether these should be applied to all existing guides: 

Write 1 page recommendation and send forward. 

Month 2: Feb. 2022 

Determine recommended review cycle – should guides be unpublished if no updates for 12, 18, 24 months, or another cycle moving forward.  

Write 1 page recommendation and send forward. 

Month 3: Mar. 2022 

Determine simple (labor should be under 4 hours per guide) recommended steps that all guide authors should do as part of an annual guide review. This is not meant to be a perfect set; it is meant to be a starting point. Time to complete this by the team should be under 2 hours. 

Steps could be to ensure: 

  • Guide is assigned a “subject” 
  • Account profile is updated with contact information and a photo/avatar 
  • Profile box is added to the guide home page 
  • Guide has been viewed on multiple devices to check responsiveness 
  • All pages have friendly URLs 
  • All links work 
  • Steps could also include from this rubric2 and/or from HSCL inclusivity work. 

Write 1 page recommendation and send forward. 

Month 4: Apr. 2022

Determine basic best practices for LibGuides at UF, and produce initial draft of a best practices guide, which can be modeled on existing examples: https://guides.library.unt.edu/best-practices  

Select a best first training resource for a foundational training on accessibility for LibGuides, to help others in understanding basics of accessibility/usability and for meeting the steps for the annual review. 

Time to complete both of these by the team should be under 4 hours. 

Month 5-6: May-June 2022

Plan for next phase work: 

  • Review existing resources (e.g., rubric for accessibility and HSCL inclusivity review elements) to see if the group can develop a next-step recommendation, that builds on the foundational recommendations 
  • Discuss creating an Accessible, well-designed template: is this recommended to be done? If so, what are the time and team resources needed to do this? 
  • Review Web Style Guide, to see what work/information is applicable from that, for the Web Ecosystem overall 
  • Can we look at reused objects, to be able to bulk fix? 

Deliver a final report (no more than 2 pages) that reviews these questions, and provides a plan for next phase work. 

Time to complete both of these by the team should be under 4 hours (this is first-phase work, not to be perfect).