February 21, 2023 through March 10, 2023 – Data Inconsistencies
There was a bug discovered that inexplicably assigned the wrong results to some page scans. Over this period of time, only 0.07% of all pages that were scanned during this period were affected. Once this was discovered, we promptly removed the results from the affected pages and triggered recalculations for the appropriate pages, websites, etc. As such you may see a small deviation from your websites typical statistics in this date range.
February 1, 2023 – Axe-Core Update
We’ve updated from minor version 4.5.x to 4.6.x. You may see a small change in violations reported. You can find more information about the changes in this axe-core update on their releases page. https://github.com/dequelabs/axe-core/releases
January 23, 2023 – Axe-Core Update
We’ve updated from minor version 4.4.x to 4.5.x. You may see a small change in violations reported. You can find more information about the changes in this axe-core update on their releases page. https://github.com/dequelabs/axe-core/releases
January 9, 2023 – Axe-Core Update
We’ve updated from minor version 4.3.x to 4.4.x. You may see a small change in violations reported, particulary those about aria roles or color contrast issues. You can find more information about the changes in this axe-core update on their releases page. https://github.com/dequelabs/axe-core/releases
November 21, 2022 – Accessibility Score Update
We have updated our accessibility score algorithm. You will likely see some mostly minor changes to your scores upon pages next scans. Score changes are only moving forward, we have not gone back and rescored old scans. This new algorithm takes into account the number of elements on the page that have accessibility issues. So, if you have MANY affected elements on a page you can expect your score to drop slightly, whereas if you only have a few affected elements you may see a bump in score.
October 26, 2022 – Redirection Behavior (reverted)
After observing the impact of our changes in redirection behavior over the previous day, we’ve decided to revert this behavior as it was previously. RAMP will follow 3xx redirects and scan the destination page, so long as its on the same website. This matches the behavior prior to the October 24th change. You may see small fluctuations in your accessibility trends occurring on or around the 25th of October.
October 24, 2022 – Redirection Behavior
Pages that 302 or 301 redirect will not longer be scanned in the future. These pages are now considered “invalid” and only direct destination page paths will be scanned. This is to prevent possible duplicate scans of both old and new page urls that result in the same destination page.
August 2, 2021 – Axe-Core Update
Axe-core has been updated from minor version 4.1 to 4.3. This comes with some new rules and bugfixes, which may have a small change on violations found on your website. For a full list of changes, please refer to the release notes of axe-core.
April 1, 2021 – Axe-Core Update & Best Practices
Axe-core has been updated from minor version 4.0 to 4.1. This comes with some new rules and bugfixes, which may have a small change on violations found on your website. For a full list of changes, please refer to the release notes of axe-core 4.1.
RAMP also now allows users to scan their websites for “best practice” violations. This is an opt-in feature, so unless you decide to do this, no changes will take place. If you do choose to scan for “best practice” violations, expect a large increase in violations found.
February 18, 2021 – Accessibility Violations
Websites will begin to collect a list of all unique, active violations found on pages. Data collection began at 10 AM, so violations found on pages before this time on this day will not show in the violations list until the pages have been rescanned.
January 14, 2021 – Begin Collecting Website & Page Accessibility Score
Pages will begin to collect a new “Accessibility Score” when they are scanned by the page monitoring system. Pages that have not been scanned after this date will not show an accessibility score until they have been rescanned.