Accessibility Statement


Compliance Status

We firmly believe that the internet should be available and accessible to anyone and are committed to providing a website that is accessible to the broadest possible audience, regardless of ability.

To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level.

This website utilizes various technologies that are meant to make it as accessible as possible at all times.

Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level. This application remediates the website's HTML, adapts its functionality and behavior for screen-readers used by blind users, and for keyboard functions used by individuals with motor impairments.

If you wish to contact the website's owner, please use the website's form.


Screen-reader and keyboard navigation

Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various behavioral changes, to ensure blind users visiting with screen-readers can read, comprehend, and enjoy the website's functions.


We have audited and worked on these issues:


1. accesskeys

- Ensures every accesskey attribute value is unique.

2. area-alt

- Ensures <area> elements of image maps have alternate text.

3. aria-allowed-attr

- Ensures an element's role supports its ARIA attributes.

4. aria-allowed-role

- Ensures role attribute has an appropriate value for the element.

5. aria-braille-equivalent

- Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent.

6. aria-command-name

- Ensures every ARIA button, link, and menuitem has an accessible name.

7. aria-conditional-attr

- Ensures ARIA attributes are used as described in the specification of the element's role.

8. aria-deprecated-role

- Ensures elements do not use deprecated roles.

9. aria-dialog-name

- Ensures every ARIA dialog and alertdialog node has an accessible name.

10. aria-hidden-body

- Ensures aria-hidden="true" is not present on the document body.

11. aria-hidden-focus

- Ensures aria-hidden elements are not focusable nor contain focusable elements.

12. aria-input-field-name

- Ensures every ARIA input field has an accessible name.

13. aria-meter-name

- Ensures every ARIA meter node has an accessible name.

14. aria-progressbar-name

- Ensures every ARIA progressbar node has an accessible name.

15. aria-prohibited-attr

- Ensures ARIA attributes are not prohibited for an element's role.

16. aria-required-attr

- Ensures elements with ARIA roles have all required ARIA attributes.

17. aria-required-children

- Ensures elements with an ARIA role that require child roles contain them.

18. aria-required-parent

- Ensures elements with an ARIA role that require parent roles are contained by them.

19. aria-roledescription

- Ensure aria-roledescription is only used on elements with an implicit or explicit role.

20. aria-roles

- Ensures all elements with a role attribute use a valid value.

21. aria-text

- Ensures role="text" is used on elements with no focusable descendants.

22. aria-toggle-field-name

- Ensures every ARIA toggle field has an accessible name.

23. aria-tooltip-name

- Ensures every ARIA tooltip node has an accessible name.

24. aria-treeitem-name

- Ensures every ARIA treeitem node has an accessible name.

25. aria-valid-attr

- Ensures attributes that begin with aria- are valid ARIA attributes.

26. aria-valid-attr-value

- Ensures all ARIA attributes have valid values.

27. audio-caption

- Ensures <audio> elements have captions.

28. autocomplete-valid

- Ensure the autocomplete attribute is correct and suitable for the form field.

29. avoid-inline-spacing

- Ensure that text spacing set through style attributes can be adjusted with custom stylesheets.

30. blink

- Ensures <blink> elements are not used.

31. bypass

- Ensures each page has at least one mechanism for a user to bypass navigation and jump straight to the content.

32. color-contrast-enhanced

- Ensures the contrast between foreground and background colors meets WCAG 2 AAA enhanced contrast ratio thresholds.

33. css-orientation-lock

- Ensures content is not locked to any specific display orientation and the content is operable in all display orientations.

34. definition-list

- Ensures <dl> elements are structured correctly.

35. dlitem

- Ensures <dt> and <dd> elements are contained by a <dl>.

36. document-title

- Ensures each HTML document contains a non-empty <title> element.

37. duplicate-id

- Ensures every id attribute value is unique.

38. duplicate-id-active

- Ensures every id attribute value of active elements is unique.

39. duplicate-id-aria

- Ensures every id attribute value used in ARIA and in labels is unique.

40. empty-heading

- Ensures headings have discernible text.

41. empty-table-header

- Ensures table headers have discernible text.

42. focus-order-semantics

- Ensures elements in the focus order have a role appropriate for interactive content.

43. frame-tested

- Ensures <iframe> and <frame> elements contain the axe-core script.

44. frame-title

- Ensures <iframe> and <frame> elements have an accessible name.

45. frame-title-unique

- Ensures <iframe> and <frame> elements contain a unique title attribute.

46. hidden-content

- Informs users about hidden content.

47. html-has-lang

- Ensures every HTML document has a lang attribute.

48. html-lang-valid

- Ensures the lang attribute of the <html> element has a valid value.

49. html-xml-lang-mismatch

- Ensure that HTML elements with both valid lang and xml:lang attributes agree on the base language of the page.

50. identical-links-same-purpose

- Ensure that links with the same accessible name serve a similar purpose.

51. image-redundant-alt

- Ensure image alternative is not repeated as text.

52. input-button-name

- Ensures input buttons have discernible text.

53. input-image-alt

- Ensures <input type="image"> elements have alternate text.

54. label

- Ensures every form element has a label.

55. label-content-name-mismatch

- Ensures that elements labelled through their content must have their visible text as part of their accessible name.

56. label-title-only

- Ensures that every form element has a visible label and is not solely labeled using hidden labels or the title or aria-describedby attributes.

57. landmark-banner-is-top-level

- Ensures the banner landmark is at top level.

58. landmark-complementary-is-top-level

- Ensures the complementary landmark or aside is at top level.

59. landmark-contentinfo-is-top-level

- Ensures the contentinfo landmark is at top level.

60. landmark-main-is-top-level

- Ensures the main landmark is at top level.

61. landmark-no-duplicate-banner

- Ensures the document has at most one banner landmark.

62. landmark-no-duplicate-contentinfo

- Ensures the document has at most one contentinfo landmark.

63. landmark-no-duplicate-main

- Ensures the document has at most one main landmark.

64. layout-table

- Ensures that layout tables do not use table elements.

65. link-in-text-block

- Ensure links are distinguished from surrounding text in a way that does not rely on color.

66. list

- Ensures that lists are structured correctly.

67. listitem

- Ensures <li> elements are used semantically.

68. marquee

- Ensures <marquee> elements are not used.

69. meta-refresh

- Ensures <meta http-equiv="refresh"> is not used for delayed refresh.

70. meta-refresh-no-exceptions

- Ensures <meta http-equiv="refresh"> is not used for delayed refresh.

71. meta-viewport-large

- Ensures <meta name="viewport"> can scale a significant amount.

72. object-alt

- Ensures <object> elements have alternate text.

73. p-as-heading

- Ensure bold italic text and font-size is not used to style <p> elements as a heading.

74. presentation-role-conflict

- Elements marked as presentational should not have global ARIA or tabindex to ensure all screen readers ignore them.

75. role-presentation

- Ensures elements with a role of presentation have a valid value.

76. scope-attr-valid

- Ensures the scope attribute is used correctly on tables.

77. select-name

- Ensures select element has an accessible name.

78. server-side-image-map

- Ensures that server-side image maps are not used.

79. skip-link

- Ensure all skip links have a focusable target.

80. tabindex

- Ensures tabindex attribute values are not greater than 0.

81. table-duplicate-name

- Ensure the <caption> element does not contain the same text as the summary attribute.

82. table-fake-caption

- Ensure that tables with a caption use the <caption> element.

83. target-size

- Ensure touch targets have sufficient size and space.

84. td-has-header

- Ensure that each cell in a table that uses the headers attribute refers only to other cells in that table.

85. th-has-data-cells

- Ensure that <th> elements and elements with role=columnheader/rowheader have data cells they describe.

86. valid-lang

- Ensures lang attributes have valid values.

87. video-caption

- Ensures <video> elements have captions.

88. nested-interactive

- Ensures interactive controls are not nested.

89. scrollable-region-focusable

- Ensure elements that have scrollable content are accessible by keyboard

90. svg-img-alt

- Ensures <svg> elements with an img, graphics-document or graphics-symbol role have an accessible text alternative


We are actively working to fix these issues:


1. meta-viewport

- Ensures <meta name="viewport"> does not disable text scaling and zooming.

2. landmark-unique

- Landmarks should have a unique role or role/label/title (i.e. accessible name) combination.

3. region

- Ensures all page content is contained by landmarks.

4. color-contrast

- Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds.

5. image-alt

- Ensures <img> elements have alternate text or a role of none or presentation.

6. page-has-heading-one

- Ensure that the page, or at least one of its frames contains a level-one heading.

7. landmark-one-main

- Ensures the document has a main landmark.

8. heading-order

- Ensures the order of headings is semantically correct.

9. button-name

- Ensures buttons have discernible text.

10. link-name

- Ensures links have discernible text.


Assistive technology and browser compatibility


We aim to support as many browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share, including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS, and NVDA (screen readers), both for Windows and MAC users.


We endeavor to fix all accessibility issues by February 2025 and are currently working with Patrol AI to set up accessibility best practices and implement new fixes to existing accessibility violations, including those listed above.