Table of contents
Before we get started, it is important to note that there is no such thing as "perfect accessibility". In addressing accessibility you should take a holistic approach, with considerations spanning content, design and code.
By the way, if you're interested in learning more about why good accessibility is important, we'd encourage you to read this article on how inclusive design creates better digital experiences for everyone (2-3 minute read).
The score we provided you with above is calculated from the key findings and test results found in this report - in total around 100 different checks. You can use this score to help benchmark your site and measure improvements.
The rest of this report provides a snapshot to help you understand how well your site is currently performing against accessibility standards and where the main issues lie.
At the end of the report we have provided you with a number of next step options to choose from to help you take action on these findings.
We performed manual checks that focus on key things, such as page title, primary navigation, page structure, keyboard navigation, link styles and zooming.
You can use these findings to identify quick wins that will have the highest impact.
Status: PassProvide a unique title for each page or view.
Your titles are very good. Nicely structured by "front-loading" with important information relevant to the current page.
Status: PassIncrease text size to 200%.
Page zooming works great as responsive styles kick in. Text zooming causes a few minor layout glitches, but most content is still readable. Does not seem to allow the default font size to be changed in Chrome though.
Status: PassUse a simple, straightforward, and consistent layout.
Consistent menu system, consistent theme, familiar content layout.
Status: IssuesUse landmark elements to indicate important content regions.
Good use of major landmarks;
footer. Some sections could be better labelled for screen readers, especially in the footer.
Status: IssuesUse heading elements to introduce content.
Headings are generally used well to introduce content, but there are some jumps in heading levels that may be confusing for assistive devices. Also missing an h1 tag on the homepage.
Status: IssuesEnsure that links are recognizable as links.
In general, most of your links are recognisable due to the context they are displayed in. For example, it's styled like a button, or it has a call to action like "Read". You should consider adding additional styling such as bold or underline for inline links, so that they are recognisable by more than just colour.
Status: PassMake sure there is a visible focus style for interactive elements that are navigated to via keyboard input.
It's very hard to track where you are on the site when tabbing through due to the lack of focus styles.
Status: PassProvide a skip link and make sure that it is visible when focused.
No "skip to content" link.
We performed a comprehensive set of tests that cover many of the WCAG 2.1 rules, as well as common accessibility best practices.
Tests are a great baseline check for your site because they are not subjective and will pass or fail. On average they find 57% of WCAG issues.
You can use this summary to understand the impact of the issues, what disabilities will be affected and where to prioritise efforts.
Critical issues result in blocked content for people with disabilities, and will definitely prevent them from accessing fundamental features or content. This type of issue puts your organisation at risk.
Serious issues result in substantial barriers for people with disabilities, and will partially or fully prevent them from accessing fundamental features or content. People relying on assistive technologies will experience significant frustration and may abandon essential workflows.
- 1 color problem
- 1 text alternatives problem
- Low Vision
Moderate issues result in some difficulty for people with disabilities, but will generally not prevent them from accessing fundamental features or content. Users may be frustrated and abandon non-critical workflows.
- 2 semantics problems
- 1 keyboard problem
- Sighted Keyboard Users
Minor issues are considered to be a nuisance or an annoyance.
The accessibility of UK websites is covered by the Equality Act 2010. This protects all individuals from unfair treatment and promotes a fair and more equal society. As a website owner you are required to make 'reasonable adjustments' to make your site accessible to people with disabilities.
Whilst there is currently no legal precedent about what these 'reasonable adjustments' might include, it is broadly accepted that WCAG 2.1 AA is a good standard to aim for - not least because that is the standard adopted by the UK government's own website.
Based on the test results above your website has:
Now that you have an idea about how your site is performing against accessibility standards, we have some suggestions for what you might do next.
Send the technical report to your development team
We are able to provide a developer action report that details the specific issues we have found, why they matter and how they might be fixed.
Bring us on board to help solve the issues
We're happy to work with your in-house team as consultants, or you can fully outsource the task to us.
Get a fully comprehensive report
This report covers accessibility basics but does not get into specific content issues. We are able to offer more detailed reports that will look at the content within specific journeys or features of your site.