Accessibility scores

Tingtun Checker

To minimize the risk of any usability barriers on our website, we ran our website's pages through the automated Tingtun Checker. This checker is designed to automatically detect barriers in HTML-files, and to conform the files to the WCAG2.1 standard.

All pages checked in the test, no "Fail"s or "Verify"s detected.

Accessed: 01. December 2020
Link: http://checkers.eiii.eu/

CSS validator

To make sure that the CSS-file was up to date with current standards, and to make sure there were no problems with the accessibility caused by poor CSS, we ran the CSS-file through the W3C CSS validator.

All documents checked. No errors found.

Accessed: 01. December 2020
Link: https://jigsaw.w3.org/css-validator/

HTML validator

Just like the CSS validation test, we also wanted to make sure that all the HTML-files were up to date with current standards, and that potential bad code would make our website less accessible to any users. The HTML validator was a way of double checking the accessibility of our code when the website was finished.

All documents checked. No errors found.

Accessed: 01. December 2020
Link: https://validator.w3.org

Internationalization Checker

We used the Internationalization Checker to ensure our website's level of internationalization-friendliness and to check our character encodings.

All our pages were checked in the test, and the result for all pages was: "No issues to report".

Accessed: 01. December 2020
Link: https://validator.w3.org/i18n-checker/

CSS LINT

We used the CSS LINT tool to test our stylesheets efficiency and to make sure there are not any problematic patterns that can cause troubles for the user experience in our CSS-file.

After running our stylesheet through the checker the result was zero errors. All warnings that were presented, which potentially could lead to accessibility troubles for various browsers, were replaced. And the other warnings were checked manually to make sure they did not present any problems development wise.

Accessed: 01. December 2020
Link: http://csslint.net/

Link Checker

The Link Checker is used to check that no anchor tag is defined twice and that all links are dereferenceable. It also checks any HTTP redirects and how our links works recursively.

After running the test on our website all links were validated automatically by the checker, aside from 4 links:

(1) The link to this link checker, and

(2) the link to the QR-code generator had to be checked manually due to denied robot access.

(3) The link to the Pixabay image of the scrapyard gave an initial error. We therefore checked this link manually and verified that this link-address was how Pixabay wanted their images to be credited and linked to.

(4) The link to the email in the footer is a mailto-anchor-link which is designed to open the users standard email service provider, with the søpl email already filled in. The linkchecker has disabled the check of this type of link.


Accessed: 01. December 2020
Link: https://validator.w3.org/checklink

A11Y Color Contrast Checker

Weak color contrast ratios can lead to websites being less accessible for users with vision impairements and for those that are colorblind. We therefore used the A11Y Color Contrast Checker to make sure that all use of colors on our website had a contrast ratio exceeding 4.5 - which is the reccomended standard in the WCAG 2.1 guidelines

The checker found no contrast issues on our page, and the lowest contrast ratio was 5.21:1

Accessed: 01. December 2020
Link: https://color.a11y.com/Contrast/

Color Oracle Test

We conducted a manual test with the use of the Color Oracle tool to check all pictures that are not scanned by an automatic tester.

We scanned all pages with the different color blindness types to see if any of these would result in a lack of information and usability when browsing our pages. As far as we could tell, none of our content is neither difficult to use nor lead to lower user satisfaction for someone with color blindness of any type.

Checked: 01. December 2020
Link: http://colororacle.org/

Firefox Accessibility Checker

We used the built in accessibility checker in Firefox to make sure we had no accessibility barriers that our other tests had not found.

After scanning all our pages with the automatic site checker, there were no issues showing.

Accessed: 01. December 2020

Axe Accessibility Checker

We wanted to do as many high quality tests as we could in order to have the highest possible chance to uncover faults in our website. Therefore, we conducted this final automatic accessibility checker that checks a multitude of accessability related tests. As stated by their own description: "It only tests for accessibility issues that can be accurately detected via automation, and it only tests for components that actually exist on the page or application you’re testing."

We tested all individual pages and for every page we recieved a warning, "Impact: serious", to ensure sufficient color contrast. All counts were manually tested and, as previously stated with the A11Y Color Contrast Checker, surpassed WCAG 2.1 AAA required contrast ratio.

Furthermore, some pages gave low foreground/background contrast errors and listed the accused color values. However, by manually checking, the stated foreground/background color combinations never appears on any of our pages.

Accessed: 01. December 2020
Link: https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd