EWe We understand that your scores in the Siteimprove tool are sometimes affected by issues that are out of your control. These are often code-related at the platform level and deal with accessibility or SEO. To keep you informed of what we’re addressing, please see the list below. It will be updated as we work on the issues.
...
Site-Specific Issues For Content Managers to Address
Module | Issue Description | Priority Level | How You Can Fix |
---|
Accessibility | Heading issues | | Be sure to use heading tags (H1, H2, H3, etc.) in hierarchal order and nest them where appropriate. Visitors who use assistive technology lose relative importance of content when heading tags are not in order. |
SEO | Mobile Speed | | Speed can be affected by the size of images. Make sure images are .jpg format and optimized in size for web. Large images and .png format will slow the speed. |
SEO | Desktop Speed | | Speed can be affected by the size of images. Make sure images are .jpg format and optimized in size for web. Large images and .png format will slow the speed. |
SEO | Navigation depth beyond 5 levels | | Consider the hierarchy that you need for each section. Can the navigation be simplified, combined, etc.? |
SEO | Pages with iFrames | | Consider if the iFrame is necessary. Can you link to the content rather than embed it? |
SEO | Pages with low text-to-code ratio | | On pages where there is very little content, you may be able to combine content. |
Info |
---|
Guide to Priority Levels Fix these issues first to make the most impact on the accessibility of your site. These issues can affect usability and content quality. You may not necessarily need to fix these issues, but they are recommended guidelines to keep in mind. |
...
Recently Fixed
Expand |
---|
title | Events showing as broken links |
---|
|
We fixed an issue that caused the "Add to Calendar" button on Events to be broken. |
...
|
We added WAI-ARIA labels to Calls to Action, Promos, and Icon Lists so that crawlers are able to identify links with the default text "Learn more". |
Expand |
---|
title | Element IDs are not unique [Low] |
---|
| The element ID for the submit button on Search and Webforms is the same. We are working to change the element ID of the Search button |
We fixed the lower mobile speed of some sites due to logo sizes. |
Expand |
---|
title | Meta issues - missing tags, titles, descriptions [High] |
---|
|
Metadata serves external sites like Facebook or Google and may have a SEO impact on what appears there. |
...
Button missing a text alternative [Low] |
|
Appropriate text alternatives for caret toggles in the side navigation menu will be added |
Expand |
---|
title | Empty heading level [Low] |
---|
|
Empty heading levels will be removed from Location pages |
Expand |
---|
title | WAI-ARIA labels [Medium] |
---|
| Need to review the "aria-labelledby" attribute to ensure it accurately describes the element |
Adjustments will be made to the DOM (Document Management Order) so that it is in the correct order for all screen widths |
Expand |
---|
title | Broken links related to x.com |
---|
|
The URL x.com (formerly twitter) on any social media references in contacts and the footer was incorrectly registering as a broken link in SiteImprove QA reports. This has been resolved at the Site Improve level. |
Expand |
---|
title | Landmark Issues "Skip to Main Content" link is not visible [Medium] |
---|
|
Need to review the HTML5 or WAI-ARIA landmarks to ensure they’re appropriately applied so that visitors who use screen readers can navigate more easilyWe fixed the issue where using the tab key to navigate the page, the “skip to main content” link at the top of each page gets focus, but was not visible on the screen. |
Expand |
---|
title | No "Current Page" indicator on pagers for Screen Readers |
---|
|
Previously, the pager did not indicate the “current page” in a way that screen readers can identify. This is resolved. |
Expand |
---|
Expand |
---|
title | HTML used to format content [Low] |
---|
|
Researching whether there is any styling that we can remove from the HTML in the iFrame codetitle | Heading issues [High] |
---|
|
Researching appropriate heading levels for embedded content. |
No active, hover, or focus link states on breadcrumb menu links |
|
We are added those state indicators to breadcrumb links. |
Work in Progress
Identified on Our Roadmap
Expand |
---|
title | Table cell missing context [Low] |
---|
|
Researching the appropriate fix for the bug in the WYSIWYG. |
Expand |
---|
title | Link without a text alternative [Low] |
---|
|
Researching appropriate text alternatives for links. |
Expand |
---|
title | Visible label and accessible name do not match [Low] |
---|
|
Reviewing page elements. |
Expand |
---|
title | Role not inside required context (on HDI pages w/ Steps as jump links) [Low] |
---|
|
We are discussing the proper fix for this with the development team. |
We Can’t Fix
Expand |
---|
title | HTML used to format content |
---|
|
We are unable to limit inline styles that are included in embedded items like YouTube videos. |
Expand |
---|
title | Redirects - 301, 3xx, chains |
---|
|
SI flags the node path (ID of the content) that's used in the LinkIt (autocomplete URL) field. This is how GovHub works: The node path redirects to the friendly alias path. |
Expand |
---|
title | Color contrast insufficient |
---|
|
This only occurs on some color palettes during the hover/active state of links. |
...
Expand |
---|
title | Inline frame without a text alternative |
---|
|
This occurs with third party embeds (like YouTube videos or Incognito forms). The title attribute is supplied from the host site, but is not being recognized when SI crawls the website. Please note: We cannot control any additional markup to add a text alternative text outside of the title with third party embeds. |