Accessibility

This accessibility statement applies to app.smartify.org

This website is run by Smartify. We want as many people as possible to be able to use this website. For example, that means you should be able to:

change colours, contrast levels and fonts
zoom in up to 300% without the text spilling off the screen
navigate most of the website using just a keyboard
navigate most of the website using speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver

We've also made the website text as simple as possible to understand.

HOW ACCESSIBLE IS OUR WEBSITE?

We know some parts of this website are not fully accessible, for example:

some video and audio elements may lack a transcript or audio description
some text lacks sufficient contrast against the background
Word and PDF documents may not be accessible to screen reader users
some decorative images may not have an appropriate alternative value
social share buttons do not have an accessible name

REPORTING ACCESSIBILITY PROBLEMS WITH THIS WEBSITE

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us via email at [email protected] and our product team will deal with your report.

COMPLIANCE STATUS

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

NON-ACCESSIBLE CONTENT

The content listed below is non-accessible for the following reasons.

NON-COMPLIANCE WITH THE ACCESSIBILITY REGULATIONS

Several user interface components cannot be interacted with when navigating the web application using a keyboard. These include: in-app notifications, radio buttons within the menu on the media-player, filter on the Search page, etc. This fails WCAG 2.2 success criterion 2.1.1 Keyboard. We plan to resolve this by July 2026.
When viewing the alternative text for images, decorative imagery might contain alternative text. This fails WCAG 2.2 success criterion 1.1.1 Non-Text Content. We plan to resolve this by July 2026.
When navigating the pages with iOS VoiceOver and Android TalkBack, markup might not always have been used to aid accessibility, especially on the Timeline pages and in the menu of the media-player. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value. We plan to resolve this by July 2026.
When navigating the web application using a keyboard, and closing a pop-ups, the focus might reset to the top of the page. This fails WCAG 2.2 success criterion 2.4.3 Focus Order. We plan to resolve this by July 2026.
Some PDF documents may not be tagged resulting in the PDF being inaccessible to screen readers. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships. We plan to resolve this by: December 2026.
The play button found on videos may not meet contrast depending on what frame of the video is playing. This means some users may find it difficult to view and recognise user interface components easily. This fails WCAG 2.2 success criterion 1.4.11 - Non-Text Contrast. We plan to resolve this by: December 2026.
When navigating the site using Android Talkback (screen reader software) users can tap behind the active menu overlay. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value. We plan to resolve this by: December 2026.
The newsletter signup form field does not indicate to the user the required format. This fails WCAG 2.2 success criterion 3.3.2 - Labels or Instructions. We plan to resolve this by: December 2026.
Some Google map iframes lack an appropriate title. Frames must be appropriately titled to support screen reader users. This fails WCAG 2.2 success criterion 2.4.1 - Bypass Blocks. We plan to resolve this by: March 2027.
Error messages do not provide suggestions as to how to correct the error. This fails WCAG 2.2 success criterion 3.3.3 - Error Suggestion. We plan to resolve this by: April 2027.
Some images lack an alternative text that is read aloud by screen readers. This results in either nothing or the image file name being read aloud for users of screen readers. This fails WCAG 2.2 success criterion 1.1.1 Non-Text Content. We plan to resolve this by: June 2027.
Some pre-recorded video-only or audio-only content lacks a text alternative. This fails WCAG 2.2 success criterion 1.2.1 Pre-Recorded Audio-Only and Video-Only. We plan to resolve this by: June 2027.
Some PDF documents may not contain XMP metadata, which may cause the content of the document to be inaccessible to screen reader users. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value. We plan to resolve this by: June 2027.
When navigating the site using Android Talkback and iOS Voiceover, (screen reader software) when a user navigates to ‘Another date’ when it has been previously activated, it incorrectly announces as ‘double tap to activate,' when already active. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value. We plan to resolve this by: June 2027.

DISPROPORTIONATE BURDEN

Some buttons relating to social media sharing may lack an accessible name, resulting in no content being announced by a screen reader. This fails WCAG 2.2 success criterion 1.1.1 Non-Text Content.

Text contrast within the social pop-up does not meet the minimum contrast ratio of 4.5:1. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum).

We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment in November 2026.

CONTENT THAT IS NOT WITHIN THE SCOPE OF THE ACCESSIBILITY REGULATIONS

PDFS AND OTHER DOCUMENTS

Some of our PDFs are essential to providing our services. For example, we have PDFs with information on how users can access our services. By June 2027, we plan to either fix these or replace them with accessible HTML pages. The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

PRE-RECORDED MEDIA

Some older videos do not have captions or an Audio Described alternative. The Accessibility Regulations do not require us to fix pre-recorded time-based media published before 23 September 2020.

LIVE VIDEO

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

WHAT WE’RE DOING TO IMPROVE ACCESSIBILITY

We plan to continue to improve the accessibility on this website over the next 12 months to ensure that new content and components are built to the highest WCAG standards where possible. We will test our design, products and content for accessibility.