This accessibility statement applies to Hijack instances provided by SMILE.
Hijack is a web application run by SMILE. 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 application text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible Hijack is
We know some parts of this website are not fully accessible:
- the text will not reflow in a single column when you change the size of the browser window
- live video streams, 360 videos and background videos do not have captions
- some of our online forms are difficult to navigate using just a keyboard
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email support@wearesmile.com
Weâll consider your request and get back to you in 5 days.
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: our support team via support@wearesmile.com.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the âaccessibility regulationsâ). If youâre not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
SMILE is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 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
Some videos do not contain the ability to add videos, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add the ability to add captions for all videos by September 2020. When we publish new content weâll make sure our use of images meets accessibility standards.
Disproportionate burden
Interactive tools and transactions
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a âlabelâ tag.
Our forms are built through third-party software.
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 aim to update these forms by September 2020.
Content that’s not within the scope of the accessibility regulations
Content uploaded by our users
SMILE provides the Hijack platform, but our users are free to upload content to their instance. The responsibility for the accessibility of this content is deemed to lie with the user or users organisation.
Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Preparation of this Accessibility Statement
This statement was prepared on 16th April 2020. It was last reviewed on 16th April 2020.
This website was last tested on 16th April 2020. The test was carried out by SMILE.
We used this approach to deciding on a sample of pages to test. We created a demo Hijack and fully loaded it with content. This was used as a test case.