This week we're super excited to unveil a project that's been in the works for a while: the new QA and Accessibility Page Reports. Read on to find out more about that and what's new in Policy.
- Upgraded Page Reports in QA and Accessibility, now with a sleeker interface and more accessible functionality.
- Progress graphs in Policy so you can track the number of policy matches over time.
Improved Page Reports in Quality Assurance and Accessibility
At Siteimprove, it's been one of our high-priority goals to upgrade the Page Reports to make them easier to use, more accessible, and internally consistent. We've made huge progress towards that with the new QA and Accessibility Page Reports (and we'll be doing the same for the SEO and Policy Page Reports soon). In addition to updating the user interface in line with Siteimprove's new look, we've also improved and added new functionalities.
More interconnected functionality
The first thing you'll notice about the new Page Reports is the updated styling. It's more than just a facelift though—we've reorganized and restyled the user interface so it integrates better into your workflow. A few highlights:
- Additional Accessibility filters so you can focus on only those issues/occurrences of an issue which are within your abilities to fix as an editor, webmaster, or developer. Combine this with the existing conformance level and severity filters to prioritize which issues you want to work on.
- More prominently placed buttons so you can easily access your CMS, share the Page Report with others, check out analytics for that page, or go to the Page Inspector.
- Guidance on how to fix Quality Assurance issues, in line with the Accessibility Page Report.
- When viewing a page affected by a particular issue, you have the option of being taken back to the platform to see other pages with that issue, so you can get into the flow of tackling one issue at a time.
HTML code view
Being able to see issues directly in the code has been one of our most-requested features, and it's now available on the QA and Accessibility Page Reports. This means you can now pinpoint exactly where a problem is located in the code, as well as exactly where to implement the fix.
Accessible interface and improved highlighting of occurrences
Good news for users of screen readers—the Accessibility and QA Page Reports are now fully navigable by keyboard. And when highlighting occurrences of an issue on the page or in the code, the focus is moved directly to where it appears on the page so you don't have to hunt for it.
The way occurrences are highlighted has improved as well. Previously, highlighting markup was added directly to the page. The new Page Reports highlight using an overlay instead so it doesn't interfere with the existing HTML.
We've vastly improved the accessibility of the Page Reports, and will continue to improve on them in the future.
Likewise, disabling CSS makes it easier to check that the order of content makes sense for users of assistive technologies.
Static Page Reports for a better user experience
In the old Page Reports, you could actually click into links on the page when viewing it in the Page Report frame. This resulted in a confusing experience because you would be taken to a new page, but the reported issues would still be specific to the page you were previously viewing. The new Page Reports show a static snapshot of the page when it was last crawled, so you can stay focused on the task you were working on.
Progress Graphs in Policy
If you've created or added policies to track compliance with organizational standards, now you can track how effective your policies have been with the new Policy progress graphs.
For each individual policy you have enabled on your site, you can see how the number of matches have fluctuated over time. A downward trend on a policy that looks for missing meta descriptions? Upward trend on a policy that looks for pages with an above-average number of page views? With the new graphs, you can use these concrete stats to report progress on your policy efforts.