Accessibility and Inclusion Policy

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 VersionWCAG 2.1
Evaluation date20/12/2021
Conformance targetLevel A
Accessibility support baseline

axe DevTools for Firefox, Chrome accessibility tools and render options

Relied upon technologies
  • HTML
  • SVG
  • JavaScript
  • CSS

Overview of website audit results

Results of Level A
PrincipleLevel A
1. Perceivable9 / 9
2. Operable14 / 14
3. Understandable5 / 5
4. Robust2 / 2
Total30 / 30

Detailed website audit results

Principle 1 Perceivable

1.1 Text Alternatives

1.1.1 Non-text Content: (Level A)
Results for the entire sample:
Outcome: Passed

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

1.2.1 Audio-only and Video-only (Prerecorded): (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no pre-recorded audio and all videos have descriptive audio.

1.2.2 Captions (Prerecorded): (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All videos have captions and descriptive audio.

1.2.3 Audio Description or Media Alternative (Prerecorded): (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All videos have captions that contain descriptive audio.

1.3 Adaptable

1.3.1 Info and Relationships: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Semantic HTML elements are used throughout.

1.3.2 Meaningful Sequence: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: The DOM order matches the visual order throughout.

1.3.3 Sensory Characteristics: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All content uses a combination of shape, colour, size, visual location, orientation, or sound.

1.4 Distinguishable

1.4.1 Use of Color: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Tested with simulations of protanopia, deuteranopia, Tritanopia and Achromatopsia.

1.4.2 Audio Control: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Audio is only played through HTML video elements where its volume can be adjusted.

Principle 2 Operable

2.1 Keyboard Accessible

2.1.1 Keyboard: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes

2.1.2 No Keyboard Trap: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: No iFrames used on the website trap the keyboard navigation.

2.1.4 Character Key Shortcuts: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There are no keyboard shortcuts that use letters, punctuation, numbers or symbol characters.

2.2 Enough Time

2.2.1 Timing Adjustable: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no time-dependent website content

2.2.2 Pause, Stop, Hide: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no essential content that moves, blinks or scrolls.

2.3 Seizures and Physical Reactions

2.3.1 Three Flashes or Below Threshold: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no three flash content.

2.4 Navigable

2.4.1 Bypass Blocks: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There are no blocks of repeated content other than the fixed header.

2.4.2 Page Titled: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All pages have a descriptive title element.

2.4.3 Focus Order: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: The DOM order matches the visual order.

2.4.4 Link Purpose (In Context): (Level A)
Results for the entire sample:
Outcome: Passed

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

2.5.1 Pointer Gestures: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no functionality that uses multipoint or path-based gestures.

2.5.2 Pointer Cancellation: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no drag and drop functionality.

2.5.3 Label in Name: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Visible text label match their associated components.

2.5.4 Motion Actuation: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: There is no motion based functionality.

Principle 3 Understandable

3.1 Readable

3.1.1 Language of Page: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: All pages use the language attribute on the HTML element.

3.2 Predictable

3.2.1 On Focus: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: No changes of context occur when any component receives focus.

3.2.2 On Input: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Entering data or selecting a form control has predictable effects. For example, all forms have submit buttons.

3.3 Input Assistance

3.3.1 Error Identification: (Level A)
Results for the entire sample:
Outcome: Passed

Findings: Form errors are identified clearly via text.

3.3.2 Labels or Instructions: (Level A)
Results for the entire sample:
Outcome: Passed

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

4.1.1 Parsing: (Level A)
Results for the entire sample:
Outcome: Passed

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.

4.1.2 Name, Role, Value: (Level A)
Results for the entire sample:
Outcome: Passed

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.