You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do not want to reference the fa-solid-900.woff on Content Build and Next Build pages, as the font file is no longer being generated.
Description or Additional Context
Font Awesome was retired, but the reference to the font file was never removed from VA.gov. This is causing metrics problems for some folks.
This was being reported in Siteimprove which is used by VHA and VAMC editors. It's in the <head> of the site so that means it's being found and reported on for every page of each VAMC, which ends up being a lot of errors.
Screenshot of where it is in the code
Screenshot of the Milwaukee VAMC Siteimprove Broken links report
You can see here that Siteimprove is reporting 160 broken links (when in reality it's just 1 link but happens to be on every page)
Because of how Siteimprove is set up, I can't get a report of how many issues total without manually going into each VAMC and then adding up the total reported broken links. But I have gone into a few and reported the total number below so we can review these after the next SI report runs and confirm that these numbers have gone down to 0:
Milwaukee: 160
Eastern Kansas: 49
Alaska: 45
Boston: 139
Steps for Implementation
Remove the reference to the file. There is no active harm in this, as the file itself no longer exists.
Acceptance Criteria
fa-solid-900.woff is removed.
The text was updated successfully, but these errors were encountered:
User Story or Problem Statement
We do not want to reference the fa-solid-900.woff on Content Build and Next Build pages, as the font file is no longer being generated.
Description or Additional Context
Font Awesome was retired, but the reference to the font file was never removed from VA.gov. This is causing metrics problems for some folks.
This was being reported in Siteimprove which is used by VHA and VAMC editors. It's in the
<head>
of the site so that means it's being found and reported on for every page of each VAMC, which ends up being a lot of errors.Screenshot of where it is in the code
Screenshot of the Milwaukee VAMC Siteimprove Broken links report
You can see here that Siteimprove is reporting 160 broken links (when in reality it's just 1 link but happens to be on every page)
Because of how Siteimprove is set up, I can't get a report of how many issues total without manually going into each VAMC and then adding up the total reported broken links. But I have gone into a few and reported the total number below so we can review these after the next SI report runs and confirm that these numbers have gone down to 0:
Steps for Implementation
Remove the reference to the file. There is no active harm in this, as the file itself no longer exists.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: