Submit an Accessibility Issue

As a Single Point of Contact (SPOC), you may see some issues in the Accessibility, Quality Assurance, or DCI reports in Siteimprove that may be confusing or appear like issues you cannot address on your own. While Tyler Technologies continuously improve the template and its features to address issues, you may find a new issue, or fringe case, that has not been identified or addressed yet.site

Submit the issue

To submit an accessibility issue, please have your agency's Single Point of Contact (SPOC) submit a ticket to the E-Government Service Desk at https://servicedesk.oregon.gov.

Be sure to include:

• URL of the page where the issue occurs
• Description of the issue and how it is affecting your website
• Link to the report in Siteimprove that identifies the issue

Once the ticket has been submitted, reviewed, and analyzed, it will be added to this article with reference to the support ticket number, and the support ticket will be closed.

Some tickets may be equivalent to a prior request made by another SPOC. In this case, the ticket number will be added to the equivalent issue.

If an issue is deemed fixable in the template, it is added to the template's roadmap as a part of a future scheduled release version. Due to the nature of development, some fixes will move amongst release versions.

Issue Request Log

The following SharePoint Starter Template issues have been identified but not completed:

Feature Request	Ticket: Date Requested	Development Sprint	Note	Estimated Release Date
Calendar Web Part Text is clipped when resizing. Button size issue	10/29/2025	Sprint 170	Development Starts: 04/07/2026	05/05/2026
Data Cell Missing Context data table expand button column needs context	11/18/2025	Sprint 170	Assigned, Development in Progress
HECC Navigation Icon color contrast issue Color contrast does not meet minimum requirement	10/29/2025	Sprint 171	Assigned, In QA Testing
HECC image-slider accessibility issues Role not inside the required context Role with implied hidden content has keyboard focus Container element is empty Hidden element has focusable content	10/29/2025	Sprint 171	Assigned, In QA Testing
HECC Flip Card accessibility issues Scrollable element is not keyboard accessible	10/29/2025	Sprint 171	Assigned, In QA Testing
Google Maps Layer Pins Don't Meet Color Contrast The pins for the second layer do not meet contrast minimums. Ensure all layer pin colors comply.	03/09/2026	Backlog
Skip to content jumps to left navigation	03/12/2026	Sprint 170	Fixed, Waiting on Deployment	6/9/2026
Shift Tabbing in top navigation can break dropdowns	03/13/2026	Backlog
Eis-announcements component has implied focus	04/08/2026	Backlog
Icon +Story Card Rotator Keyboard accessibility Issue	Manual Testing	Backlog
Google Maps Accessibility Issues	Manual Testing	Backlog
ODOT Project Pages iframe missing text alternative	05/29/2026	Backlog
Form Builder generating empty h2 when no title is present	5/29/2026	Backlog
Data Tables need to require a caption   WCAG2.1 requires data tables have a caption element.	08/06/2025	Backlog
ODHS Meganav Focus Issue	06/01/2025	Backlog

Completed Issues

When an issue has been completed, it will be logged on our completed accessibility issues page

 

How to inquire about a submitted issue

If you have questions about a requested issue, please contact the E-Government Service Desk at https://servicedesk.oregon.gov. Be sure to reference the original ticket number(s).