Add Accessibility Statement page to the UGRC website

[chriswnek]

To show transparency in the efforts being put forth by UGRC to meeting accessibility requirement, we will add a page to the UGRC website that includes an Accessibility Statement, along with a link to our Accessibility Action Plan document. Where necessary, we can link to this page from other websites or web apps that UGRC manages.

Tasks

• Draft Accessibility Statement for website
• Draft Accessibility Action Plan (In progress)
• Create new page on website
• Add link to page in the footer of gis.utah.gov

Content for Website

Accessibility page text

UGRC is committed to ensuring digital accessibility for all users, including those interacting with our geospatial information systems. We believe that location-based data should be inclusive. We strive to provide an equitable experience that aligns with WCAG 2.1 Level AA standards for all websites and apps that we maintain. If a UGRC website or app does not meet your accessibility needs, please contact us at ugrc@utah.gov.

We created the Accessibility Action Plan to serve as our formal roadmap for identifying and remediating digital barriers across our websites and GIS applications. We maintain this as a living document to outline our testing procedures and remediation workflows, ensuring a consistently inclusive experience for you.

[chriswnek]

I've worked on modifying our AAP Google Doc to address accessibility issues that it was having when published to the web. Fixes included removing the tabbed sections and instead making it one long document, adding padding around links, and fixing table headers.

WAVE can't seem to handle analyzing the published Google Doc, but Lighthouse does work. Only two issues remain:

• element does not have a [lang] attribute: the html of a published Google Doc cannot be modified, so there is not workaround for this issue
• Document does not have a main landmark: similar to the above language error, where the issue is with Google's html template. A recommended workaround was to add a Table of Contents to the top of the document to help a screen reader with navigation, so that's been implemented. Another "band-aid" we can do is to add a role and aria-label to the iframe code. Below is an example of what that would look like:

<iframe 
src="https://docs.google.com/document/d/e/2PACX-1vS-Y54mTB9D7H1rVk4xmZa-8TrCitVwrE0HihpTdlQ_y6k7na45mixr9CQhMrf7R4ZxvIWQ2fLeUUWI/pub?embedded=true"
role="main"
title="Main Document Content"
aria-label="Main Document Content">
</iframe>

[chriswnek]

Modified the draft accessibility text so it better followed our UGRC style guide.