Compliance
92/100
Advisor

August 2026
73
Your Funka Score is 73 out of 100. Maturity is your lowest-scoring area, so focus on improving it first.
No accessibility statement was detected. We've prepared a draft for you to complete and publish.

Neutral
0–69
Below 70

Bronze
70–79
Score 73

Silver
80–89
7 points away

Gold
90–100
17 points away
The Funka Score is a comprehensive measure of digital inclusion that goes beyond accessibility compliance to evaluate how accessible, usable and discoverable a website is, providing one clear score and actionable insights for improvement.
Does your website meet accessibility standards and legislation?
Checks for accessibility issues, such as missing image descriptions, poor colour contrast and buttons without labels.
Accessible pages help people using screen readers, keyboards and magnifiers access the same information and services as everyone else. Automated checks are a starting point, not a complete assessment.
Anyone using a screen reader hears "link" with no idea where it leads, so they have to follow it to find out.
See details & how to fix: Give links discernible textIf the edge or background of a button is too faint, people with low vision, or anyone using a screen in bright light, can't see that it's clickable or where it begins and ends.
See details & how to fix: Give clickable elements enough contrastThe field is announced with no name, so someone using a screen reader or voice control can't tell what to type into it.
See details & how to fix: Add labels to form fieldsText with too little contrast is hard or impossible to read for people with low vision, for many older people and for anyone looking at a screen in bright light.
See details & how to fix: Improve text contrastScreen-reader users move around a page by jumping between its regions: header, navigation, main content and footer.
See details & how to fix: Wrap content in landmarksScreen-reader users lose the shortcut that takes them past the menu straight to the content.
See details & how to fix: Add a main landmarkThe main heading tells people what the page is about before they read anything else.
See details & how to fix: Add a top-level headingPeople who find it hard to tell colours apart, including many with colour blindness or low vision, see the link as ordinary text and may miss it completely.
See details & how to fix: Don't rely on colour alone to mark linksHeading levels tell screen-reader users how a page is organised.
See details & how to fix: Fix heading orderMany screen-reader users skim a page by jumping from heading to heading.
See details & how to fix: Code visual headings as real headingsHow transparent are you about accessibility?
Reviews your accessibility statement to see how clearly you explain known issues, what you're doing about them and how people can contact you.
A clear statement helps visitors understand what to expect, find support and report barriers. It also makes your commitment and next steps visible.
Visitors who meet a barrier can't find out what on the site isn't accessible, how to get the content another way or where to report the problem.
See details & how to fix: Link to your accessibility statementIs your website easy to read and use?
Looks at how easy your text is to read and whether content moves around unexpectedly while pages load.
Readable text and a stable page make it easier for people to understand information and complete tasks, especially when they have cognitive or visual access needs.
Readability (LIX) on 5 pages. Visual stability (CLS) on 5 pages. Time to stable layout on 5 pages.
No individual error details are available for this area in the current scan.
Can people find your website and its content?
Checks how well your pages are structured so search engines and AI tools can find and understand your content.
Clear headings and page structure help people find relevant information and help search engines and AI tools understand what each page is about.
The fix: Use the same words in the main heading (H1) as in the page title, so visitors who arrive from a search result can see they are on the right page.
The fix: Give every page one main heading (H1) that says what the page is about.
The fix: Point each page's canonical link at the page's own address, unless the page really is a copy of another. A canonical link to another address can keep the page out of search results.
Your badge shows your score with its Bronze tier, and it updates on its own every time a monthly re-scan lands.
Showing it is optional: it's one line of code in your footer, linking to your badge information page.
Evidence
The same scan, two ways of looking at it: by finding, or page by page. Every test runs against the public version of your site, so your own team can reproduce every error.
135
Errors
Elements that failed a test
181
Approved
Elements that passed a test
2
Incomplete
Tests a person needs to finish by hand
8
Inapplicable rules
Rules for features your pages don't use
Each fix belongs to the team that usually makes it. Pick a team to see only their part of the work.
Technical fixes involving code, page structure, labels and keyboard accessibility.
7 of 11 fixes
Design improvements involving colour contrast, visual clarity and interactive elements.
3 of 11 fixes
Content improvements involving headings, links, images and written information.
4 of 11 fixes
Ordered worst-first: by severity, then by how many elements each rule affects.
Showing all 11 fixes.
Who fixes it: Developers and content managers
Anyone using a screen reader hears "link" with no idea where it leads, so they have to follow it to find out.
The fix: Give every link text that says where it leads. For a link that is only an icon or an image, add a name in the code, with aria-label or the image's alt text.
Some links have no text content, leaving screen-reader users without context.
Found on 5 of the scanned pages, in 50 elements in total.
Rule
link-name
50 elements
First failing element
a.card-linkRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: UX designers and developers
If the edge or background of a button is too faint, people with low vision, or anyone using a screen in bright light, can't see that it's clickable or where it begins and ends.
The fix: Give the border or background of every button and other control a contrast ratio of at least 3:1 against the colour next to it. Check the colours in your design system with a contrast checker, so new components get it right from the start.
Buttons and other controls don't stand out enough from their background. Interactive elements need a 3:1 contrast ratio (WCAG 1.4.11).
Found on 5 of the scanned pages, in 33 elements in total.
Rule
funka-clickable-contrast
33 elements
First failing element
/html[1]/body[1]/main[1]/form[1]/button[1]Read the standard: WCAG 1.4.11 Non-text Contrast (opens in a new tab)
Who fixes it: Developers
The field is announced with no name, so someone using a screen reader or voice control can't tell what to type into it.
The fix: Connect a visible <label> to every field with for and id, or put the field inside its label. If the design has no room for a visible label, give the field an aria-label.
Form inputs are missing <label> or aria-label, so the fields are unannounced.
Found on 1 of the scanned pages, in 5 elements in total.
Rule
label
5 elements
First failing element
input#qRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: UX designers
Text with too little contrast is hard or impossible to read for people with low vision, for many older people and for anyone looking at a screen in bright light.
The fix: Darken the text or lighten the background until normal text reaches at least 4.5:1 and large text at least 3:1. Change the colour where it is defined, in your stylesheet or design system, so every place that uses it is fixed at once.
Text doesn't meet the 4.5:1 contrast ratio required by WCAG 2.2 AA.
Found on 1 of the scanned pages, in 1 element in total.
Rule
color-contrast
1 element
First failing element
span.meta-dateRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: Developers
Screen-reader users move around a page by jumping between its regions: header, navigation, main content and footer. Anything outside those regions is easy to miss.
The fix: Place all visible content inside the page's regions: <header>, <nav>, <main>, <aside> or <footer>. Check things added outside the template too, such as cookie notices and chat windows.
Some content sits outside any landmark, making it harder to navigate by region.
Found on 5 of the scanned pages, in 25 elements in total.
Rule
region
25 elements
First failing element
div.page-introRead how to fix this rule (Deque University) (opens in a new tab)
Visitors who meet a barrier can't find out what on the site isn't accessible, how to get the content another way or where to report the problem.
The fix: Put a link to your accessibility statement in the footer or the main navigation, so it's on every page. Use a link text that says where it leads, such as "Accessibility statement".
No link to an accessibility statement was found in the header or footer, so visitors can't see how accessible the site is or how to report a problem.
Found on 5 of the scanned pages, in 5 elements in total.
Rule
funka-wad10-link
5 elements
First failing element
/html[1]/body[1]/footer[1]Who fixes it: Developers
Screen-reader users lose the shortcut that takes them past the menu straight to the content.
The fix: Wrap each page's main content in one <main> element in the page template. Keep the header, menu and footer outside it.
Each page should contain exactly one <main> landmark for screen-reader users.
Found on 4 of the scanned pages, in 4 elements in total.
Rule
landmark-one-main
4 elements
First failing element
htmlRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: Developers and content managers
The main heading tells people what the page is about before they read anything else. Screen-reader users often jump straight to it.
The fix: Give every page one clear main heading at the top of its content, coded as <h1>.
Pages are missing an <h1>, the anchor of the document outline.
Found on 1 of the scanned pages, in 1 element in total.
Rule
page-has-heading-one
1 element
First failing element
htmlRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: UX designers
People who find it hard to tell colours apart, including many with colour blindness or low vision, see the link as ordinary text and may miss it completely.
The fix: Underline links in body text, or give them another visual cue besides colour, such as an icon, a background or a border. An underline is the cue most people recognise straight away.
Links are distinguished from surrounding text only by colour. Add an underline or another visual cue so everyone can spot them (WCAG 1.4.1).
Found on 1 of the scanned pages, in 1 element in total.
Rule
funka-link-color-independence
1 element
First failing element
/html[1]/body[1]/main[1]/div[1]/p[3]/a[1]Read the standard: WCAG 1.4.1 Use of Color (opens in a new tab)
Who fixes it: Content managers and developers
Heading levels tell screen-reader users how a page is organised. A jump from level 2 to level 4 suggests that content is missing.
The fix: Step heading levels down one at a time: an h2 is followed by an h3, not an h4. Choose a heading's level by its place in the structure, and change how it looks with CSS rather than with another level.
Headings skip levels (e.g. h2 followed by h4), which breaks the document outline.
Found on 1 of the scanned pages, in 1 element in total.
Rule
heading-order
1 element
First failing element
h4.section-titleRead how to fix this rule (Deque University) (opens in a new tab)
Who fixes it: Content managers
Many screen-reader users skim a page by jumping from heading to heading. Text that only looks like a heading is skipped, so they miss how the page is organised.
The fix: Use the heading formats in your publishing tool (Heading 2, Heading 3 and so on) instead of making text bold or larger. In the code they become real heading elements, <h2> to <h6>, chosen by level rather than by size.
Text that's only styled to look like a heading never shows up in a screen reader's list of headings, so the page loses its outline.
Found on 3 of the scanned pages, in 9 elements in total.
Rule
funka-non-semantic-heading
9 elements
First failing element
/html[1]/body[1]/main[1]/div[2]/p[1]/strong[1]Read the standard: WCAG 1.3.1 Info and Relationships (opens in a new tab)
181 elements passed their tests, across 39 rules. Worth knowing, because it tells you where not to spend time.
Automated tests can't judge everything. 2 rules came back inconclusive on your pages, so a person needs to finish them by hand.
These rules look for features your pages don't currently use. Nothing to do, but if you add those features later, they'll start being tested.
The 5 pages this scan covered, worst first. Errors here almost always exist on similar pages that weren't scanned.
https://www.yourcompany.com/sok
https://www.yourcompany.com/vara-varderingar
https://www.yourcompany.com/om-oss
https://www.yourcompany.com/strategi
The 5 pages this scan covered, worst first. Errors here almost always exist on similar pages that weren't scanned.
| Page | Failed rules | Errors |
|---|---|---|
Startsida - Your Company | 6 | 38 |
Sök - Your Company | 7 | 27 |
Våra värderingar - Your Company | 6 | 25 |
Om oss - Your Company | 7 | 24 |
Strategi - Your Company | 6 | 21 |
The same words are used throughout this report. Here is what each one means.
| Test | A single automated check run against your pages, for example “images must have alternative text”. |
|---|---|
| Rule | The standard a test measures against. Each rule can produce many errors. |
| Element | One individual thing on a page: a link, a button, a heading, an input field. |
| Error | One element that failed one rule. 135 errors across 11 failed rules means the same 11 problems repeat in 135 places. |
| Failed test | A rule your pages did not meet. These are the fixes listed under “What we found”. |
| Approved test | A rule your pages met. Nothing to do. |
| Incomplete test | A test the engine could not decide automatically, usually because of a gradient, image or overlay behind the element. A person has to finish it by hand. |
| Inapplicable rule | A rule that does not apply because your pages don’t use the feature it tests. It starts being tested if you add that feature. |
| Severity | How much a finding hurts a user. Serious can stop someone completing a task, Moderate makes the site harder to use, Minor is annoying but rarely blocking. |
| Tier | The badge level your total score earns. With Funka Advisor: Bronze 70–79, Silver 80–89, Gold 90–100; below 70 the badge is Neutral. With Funka Assistant it is always Neutral. |
The Funka Score is indicative. It is produced by Funka's automated scanning engine against WCAG 2.2 AA, combined with a maturity assessment of published accessibility documentation, and weighted using a model built on Funka's 26 years of accessibility expertise.
Automated testing can only detect a portion of all accessibility and usability barriers. Judgement-based criteria, such as meaningful alt text, logical reading order, clear language, focus order and the usability of complex components, cannot be reliably measured by software. A high score does not guarantee compliance, and a low score does not mean a site is unusable.
For an accurate measure on accessibility and compliance, an automated scan should be complemented by a manual expert audit, assistive technology testing (screen readers, keyboard-only, magnification, voice control) and testing with users with disabilities. Funka can carry out these audits and issue a formal compliance assessment.
This report is not legal advice and is not a certificate of compliance with the European Accessibility Act, the Web Accessibility Directive, EN 301 549, the ADA or any other legislation or standard. Funka accepts no liability for any fines, penalties, claims, complaints, legal proceedings, losses or damages arising from reliance on this report or on the score, badge or tier shown in it. Responsibility for the accessibility of the website remains with the customer.
You have the full report
Every failed rule on this scan is listed above, your badge carries its metal tier, and a monthly re-scan keeps both current.
The Funka Score is indicative. For a fully accurate picture, explore our expert services and tools.
Get the badge code. Displaying the badge is optional. If you choose to, it's one line in your footer, it always shows your latest score and links to your badge information page. Read the badge guide.
Get the badge code