Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Site-Specific Issues For Content Managers to Address

Module

Issue Description

Priority Level

How You Can Fix

Accessibility

Heading issues

Status
colourRed
titleHigh

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

Status
colourYellow
titleMedium

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

Status
colourYellow
titleMedium

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

Status
colourGreen
titlelow

Consider the hierarchy that you need for each section. Can the navigation be simplified, combined, etc.?

SEO

Pages with iFrames

Status
colourGreen
titlelow

Consider if the iFrame is necessary. Can you link to the content rather than embed it?

SEO

Pages with low text-to-code ratio

Status
colourGreen
titlelow

On pages where there is very little content, you may be able to combine content.

Info

Guide to Priority Levels

Status
colourRed
titleHigh
Fix these issues first to make the most impact on the accessibility of your site.
Status
colourYellow
titleMedium
These issues can affect usability and content quality.
Status
colourGreen
titlelow
You may not necessarily need to fix these issues, but they are recommended guidelines to keep in mind.

...

Recently Fixed

We fixed missing meta tags, titles, and descriptions. Metadata serves external sites like Facebook or Google and may have a SEO impact on what appears there
Expand
titleMeta issues - missing tags, titles, descriptions [High]
WAI-ARIA labels [Medium]

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
titleMobile Speed [Medium]

We fixed the lower mobile speed of some sites due to logo sizes.

Expand
titleElement IDs are not unique Button missing a text alternative [Low]

We changed the element ID of the submit button on Search so that it is no longer the same element ID as the submit button on WebformsAppropriate text alternatives for caret toggles in the side navigation menu will be added

Expand
titleEmpty heading level [Low]

Empty heading levels will be removed from Location pages

Expand
titleAdjust DOM Order [Low]

Adjustments will be made to the DOM (Document Management Order) so that it is in the correct order for all screen widths

Expand
titleBroken 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
titleLandmark Issues "Skip to Main Content" link is not visible [Medium]

We reviewed the HTML5 or WAI-ARIA landmarks to ensure they’re appropriately applied so that visitors who use screen readers can navigate more easilyfixed 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
titleNo "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.

We fixed an issue that caused some agencies to see a significant decrease in Quality Assurance and DCI scores after a Siteimprove release
Expand
titleBroken links at page level 2, 3, and deeper [High]
No active, hover, or focus link states on breadcrumb menu links

We are added those state indicators to breadcrumb links.

Work in Progress

...

titleHeading issues [High]

...

Identified on Our Roadmap

Researching whether there is any styling that we can remove from the HTML in the iFrame code
Expand
Expand
titleHTML used to format content [Low]
titleWAI-ARIA labels [Medium]

Need to review the "aria-labelledby" attribute to ensure it accurately describes the element.

Table cell missing context [Low]

Researching the appropriate fix for the bug in the WYSIWYG.

Expand
titleLink without a text alternative [Low]

Researching appropriate text alternatives for links.

Expand
titleVisible label and accessible name do not match [Low]

Reviewing page elements.

Expand
titleRole 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
titleHTML used to format content

We are unable to limit inline styles that are included in embedded items like YouTube videos.

Expand
titleRedirects - 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
titleColor contrast insufficient

This only occurs on some color palettes during the hover/active state of links.

...

Expand
titleInline 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.