Swiis International Limited (consisting of Swiis (UK) Limited, Swiis Foster Care Limited, and Swiis Foster Care Scotland Limited) (hereafter referred to as “We”) recognise and value the diversity of all stakeholders.
This accessibility statement and inclusion policy applies to the systems and software we use to deliver interactive websites and online learning to staff, foster carers, children and young people, temporary workers and the public who are interested in the services offered by Swiis.
Swiis websites and software are designed to be used by people with a diverse range of hearing, movement, sight, and cognitive ability.
Swiis responsibilities:
- To develop websites and use external online providers that aims to be compliant with Web Content Accessibility Guidelines (“WCAG”) 2.1, so that we maximise website usage and in the case of online training, learner participation.
- To work with partners to create ever more accessible courses that maximise learner participation.
- To provide moderation to challenge any flagged language or behaviour of learners that may create an intimidating or hostile environment.
- To strive to design courses with learning objectives that are achievable, whenever feasible and reasonable, for learners with impairments and learners for whom English is not their first language.
- To identify and document aspects of course learning that may be challenging for learners with impairments so that learners can be informed of any challenges.
- To avoid any action that could amount to unlawful discrimination under UK law, including failure to make reasonable adjustments to learning materials where necessary.
- To develop courses that recognise, and represent learner diversity, so that learners can put in place or request adjustments that enable them to participate.
We are always looking to improve our accessibility. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact marketing@swiis.com.
Accessibility of Swiis websites
The Swiis websites are fully compliant with the Web Content Accessibility Guidelines version 2.1 A standard and partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard and AAA standards.
Scope of the website evaluation
| Scope of the website | All web content of the public websites of swiis.com, swiisfostercare.com, swiisfostercarescotland.com and swiishealthcare.com. |
|---|---|
| WCAG Version | WCAG 2.1 |
| Evaluation date | 20/12/2021 |
| Conformance target | Level A |
| Accessibility support baseline | axe DevTools for Firefox, Chrome accessibility tools and render options |
| Relied upon technologies |
|
Overview of website audit results
| Principle | Level A |
|---|---|
| 1. Perceivable | 9 / 9 |
| 2. Operable | 14 / 14 |
| 3. Understandable | 5 / 5 |
| 4. Robust | 2 / 2 |
| Total | 30 / 30 |
Detailed website audit results
Principle 1 Perceivable
1.1 Text Alternatives
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.
- Controls, Input If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
- Time-Based Media If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
- Test If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
- Sensory If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
- CAPTCHA If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
- Decoration, Formatting, Invisible If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
Findings: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose
1.2 Time-based Media
For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
- Prerecorded Audio-only An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
- Prerecorded Video-only Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Findings: There is no pre-recorded audio and all videos have descriptive audio.
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Findings: All videos have captions and descriptive audio.
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Findings: All videos have captions that contain descriptive audio.
1.3 Adaptable
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Findings: Semantic HTML elements are used throughout.
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Findings: The DOM order matches the visual order throughout.
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
Findings: All content uses a combination of shape, colour, size, visual location, orientation, or sound.
1.4 Distinguishable
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Findings: Tested with simulations of protanopia, deuteranopia, Tritanopia and Achromatopsia.
If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Findings: Audio is only played through HTML video elements where its volume can be adjusted.
Principle 2 Operable
2.1 Keyboard Accessible
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Findings: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Findings: No iFrames used on the website trap the keyboard navigation.
If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
- Turn off A mechanism is available to turn the shortcut off;
- Remap A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
- Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus.
Findings: There are no keyboard shortcuts that use letters, punctuation, numbers or symbol characters.
2.2 Enough Time
For each time limit that is set by the content, at least one of the following is true:
- Turn off The user is allowed to turn off the time limit before encountering it; or
- Adjust The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception The time limit is longer than 20 hours.
Findings: There is no time-dependent website content
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
- Moving, blinking, scrolling For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Findings: There is no essential content that moves, blinks or scrolls.
2.3 Seizures and Physical Reactions
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Findings: There is no three flash content.
2.4 Navigable
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Findings: There are no blocks of repeated content other than the fixed header.
Web pages have titles that describe topic or purpose.
Findings: All pages have a descriptive title element.
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Findings: The DOM order matches the visual order.
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Findings: The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context.
2.5 Input Modalities
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Findings: There is no functionality that uses multipoint or path-based gestures.
For functionality that can be operated using a single pointer, at least one of the following is true:
- No Down-Event The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
- Up Reversal The up-event reverses any outcome of the preceding down-event;
- Essential Completing the function on the down-event is essential.
Findings: There is no drag and drop functionality.
For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Findings: Visible text label match their associated components.
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface The motion is used to operate functionality through an accessibility supported interface;
- Essential The motion is essential for the function and doing so would invalidate the activity.
Findings: There is no motion based functionality.
Principle 3 Understandable
3.1 Readable
The default human language of each Web page can be programmatically determined.
Findings: All pages use the language attribute on the HTML element.
3.2 Predictable
When any component receives focus, it does not initiate a change of context.
Findings: No changes of context occur when any component receives focus.
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Findings: Entering data or selecting a form control has predictable effects. For example, all forms have submit buttons.
3.3 Input Assistance
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
Findings: Form errors are identified clearly via text.
Labels or instructions are provided when content requires user input.
Findings: All form labels have clear descriptive text and any required fields that were not completed are clearly identified.
Principle 4 Robust
4.1 Compatible
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
Findings: !DOCTYPE html is included on every page. Closing tags are included for every element that require them. id attributes are unique on each page.
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Findings: The name and role of all user interface components (including but not limited to: form elements, links and components generated by scripts) can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.