This accessibility statement applies to the giosg Platform’s accessibility for website visitors. This statement has been updated on 13 March 2025. The statement is not final, as we are still improving non-accessible content in our services.
giosg is committed to ensuring that our products are accessible to all users. In this accessibility statement we describe the accessibility of the service we provide, and also provide instructions on how to give feedback on accessibility.
Communiction services (chat, video calls)
The digital service complies partly with the accessibility requirements
Our chat service has been audited several times by external accessibility expert service providers as part of accessibility audits performed on our customers’ services. Most of the critical deficiencies identified and reported to us in these audits have been fixed. However, for the time being, the giosg chat service does not fully meet all the requirements of our target AA accessibility level.
The chat window language should be set by the Customer to match their web page, and the selected language should be automatically declared for screen readers.
Interaction Builder
The digital service complies partly with the accessibility requirements
Most of the critical deficiencies identified and reported to us in these audits have been fixed. However, for the time being, the giosg chat service does not fully meet all the requirements of our target AA accessibility level.
The person who creates the interaction is responsible of setting colours and labels so that it complies accessibility requirements.
Disproportionate burden
The giosg chat service includes the possibility for audio and video calls as well as streaming live video. Real-time text transcription for this content is not currently technically possible.
Chatting parties can share any images and videos during chat conversations. The content of these files can not be described or transcribed. The users can be notified that a file of the corresponding type has been shared.
Terms
The terms used in the Conformance Level information are defined as follows:
Supported: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partial support: Some functionality of the product does not meet the criterion.
Not supported: The majority of product functionality does not meet the criterion.
Not applicable: The criterion is not relevant to the product.
Table: Success Criteria
| Criteria | Level | Conformance level | Remarks and explanations | Chat status | IB status | |
| 1.1.1 Non-text content | AA | ✅Supported | Chat: While we are not able to describe the content of media shared in chat, we declare the type of media sent or received. Interactions: For example, we have the possibility to add an accessibility label to a video element, which is used to describe the content of the video. |
|||
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | 🕓Partial support | Interactions: any video can be added, alternate content needs to be provided by interaction creator. Chat: Video can be shared as an attachment, an alternative cannot be provided. |
|||
| 1.2.2. Captions (Prerecorded) | A | Not supported | Chat: Video can be shared as an attachment, captions cannot be provided. Interactions: Adding captions to video is not technically possible in interactions. |
|||
| 1.2.3. Audio Description or Media Alternative (Prerecorded) | A | Not supported | Chat: Video can be shared as an attachment, providing an audio description is not possible. Interactions: Adding an audio description for video is not technically possible in interactions. |
|||
| 1.2.4 Captions (Live) | AA | Not relevant | Live video is possible in interactions and in chat. Adding captions for live video is not technically possible. | |||
| 1.2.5 Audio Description (Prerecorded) | AA | Not supported | Chat: Adding an audio description for video shared during chat is not technically possible. | |||
| 1.3.1 Info and Relationships | A | 🕓 Partial support | Chat: Elements are properly named. The relationship between elements in the chat history needs to be improved. Interactions: Designer can define the element names. |
In progress - Due Jun 2nd (Screen reader update) | ||
| 1.3.2 Meaningful Sequence | A | ✅Supported | Chat: Element order is correct. Interactions: The interactions attempt to define the most logical tab order. |
|||
| 1.3.3 Sensory Characteristics | A | ✅Supported | Chat works, in interactions up to designer | |||
| 1.3.4 Orientation | AA | ✅Supported | Chat and interactions work regardless of orientation. | |||
| 1.3.5 Identify Input Purpose | AA | 🕓Partial support | Chat: Chat is labeled correctly, except for the input field, which needs a small improvement. Interactions: Fields in interactions can be labeled by the designer. The expected content for fields can be set in interactions. |
Ticketed - Due Jun 2nd | ||
| 1.4.1 Use of Color | A | ✅Supported | States in chat are not indicated with color alone. In interactions the color choices are up to the designer to decide. | |||
| 1.4.2 Audio Control A | A | ✅Supported | Chat: No long sounds played through giosg. All sound notifications can be muted by the visitors and disabled completely from the giosg UI settings by admins. Interactions: No sound. |
|||
| 1.4.3 Contrast (minimum) | AA | ✅Supported | Chat: The default chat UI in giosg has sufficient contrast. Colors can be edited in the Brand Editor, and the choices there are up to the person editing. Interactions: Color choices are decided by the designer. |
|||
| 1.4.4 Resize text | AA | Partial support | Chat: The font size can be enlarged in the browser without losing functionality. However, resizing only the font size in Firefox breaks the layout in some cases. Interactions: Font resizing does NOT apply to interactions. |
Done (May 13th) | Ticketed - Due during June | |
| 1.4.5 Images of Text | AA | ✅Supported | Images of text are not used. | |||
| 1.4.10 Reflow | AA | Partial support | Chat: The chat window supports extreme zoom levels and small viewport sizes. Interactions: Limited ability to conform to zoom level and/or viewport size. |
Ticketed - Due during June | ||
| 1.4.11 Non-text Contrast | AA | ✅Supported | Chat: The user interface has adequate contrast. Interactions: Color choices are up to the designer. |
|||
| 1.4.12 Text Spacing | AA | Not supported | Chat: limited Interactions: none |
Ticketed - Due Jun 2nd | Ticketed - Due during June | |
| 1.4.13 Content on Hover or Focus | AA | ✅Supported | No such content in chat or interactions. | |||
| 2.1.1 Keyboard | A | Partial support | Chat: Usable with keyboard. Interactions: Need to confirm that all elements are fully usable with the keyboard. |
To test | ||
| 2.1.2 No Keyboard Trap | A | ✅Supported | Chat: No keyboard traps. Interactions: Keyboard trap can be enabled for views if the designer chooses so, but it is not mandatory. |
|||
| 2.1.4 Character Key Shortcuts | A | ✅Supported | No single-character shortcuts used. | |||
| 2.2.1 Timing Adjustable | A | ✅Supported | No time limits in the user interface. Chat has time limits for service, which are essential. Timelimits can be modified in the settings. | |||
| 2.2.2 Pause, Stop, Hide | A | ✅Supported | Chat: Auto-updating content is essential for chat. Interactions: No such content. |
|||
| 2.3.1 Three Flashes or Below Threshold | A | ✅Supported | No flashing elements. | |||
| 2.4.1 Bypass Blocks | A | Partial support | To test | |||
| 2.4.2 Page Titled | A | Not supported | Chat: Set a name for the chat window and declare it when entering with a screen reader. Interactions: Set a name for the interaction and declare it when entering the interaction. |
In progress - Due Jun 2nd (Screen reader update) | Ticketed - Due during June | |
| 2.4.3 Focus Order | A | ✅Supported | ||||
| 2.4.4 Link Purpose (In Context) | A | ✅Supported | ||||
| 2.4.5 Multiple Ways | AA | Not relevant | Not relevant to giosg ("More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.") | |||
| 2.4.6 Headings and Labels | AA | Partial support | Chat: No content headings in chat. Interactions: Interactions should use the proper <h> elements in HTML to display headings. Heading content is up to the designer to decide. |
Ticketed - Due during June | ||
| 2.4.7 Focus Visible | AA | Partial support | Chat: Focus is higlight is clearly visible. Interactions: Focus higlight appears, but the visibility needs to be improved. |
Ticketed - Due during June | ||
| 2.5.1 Pointer Gestures | A | ✅Supported | Not relevant to giosg | |||
| 2.5.2 Pointer Cancellation | A | ✅Supported | Supported in chat and interactions. | |||
| 2.5.3 Label in Name | A | Partial support | Chat: Button names and labels are declared in chat. Interactions: Need to ensure each element type supports reading the correct label in the right way. |
TBC | ||
| 2.5.4 Motion Actuation | A | Not in scope | No motion controls. | |||
| 3.1.1 Language of Page | A | Not supported | Chat and interactions need to properly declare the correct language. Chat: Shoud match the UI language. Interactions: Should match the selected language for interaction. |
In progress - Due Jun 2nd (Screen reader update) | Ticketed - Due during June | |
| 3.1.2 Language of Parts | AA | Not relevant | Chat messages can include any language, and this language is not possible to know beforehand. | |||
| 3.2.1 On Focus | A | ✅Supported | No actions performed on focus. | |||
| 3.2.2 On Input | A | ✅Supported | No change in context when changing the settings of a UI component. | |||
| 3.2.3 Consistent Navigation | AA | ✅Supported | Chat navigation does not change based on the page it appears on. In interactions, the designer has to make the navigation consistent. | |||
| 3.2.4 Consistent Identification | AA | ✅Supported | Chat functionality does not change based on the page it appears on. In interactions, the designer has to make the navigation consistent. | |||
| 3.3.1 Error Identification | A | ✅Supported | Chat: No error is shown when the user attempts to send a message from an empty input field. Interactions: Errors are detected in interactions. |
Done (May 13th) | ||
| 3.3.2 Labels or Instructions | A | Partial support | Chat: The input field can be declared more clearly. Interaction: A description can be added to any input. |
In progress - Due Jun 2nd (Screen reader update) | ||
| 3.3.3 Error Suggestion | AA | Partial support | Same as with 3.3.1: chat needs an error message suggesting a fix. Interactions: Make sure screen readers read the errors. |
Done (May 13th) | To tested | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not relevant | Should not be relevant to giosg, as the systems used for legal, financial or user data related actions are not provided by giosg. | |||
| 4.1.1 Parsing | A | ✅Supported | ||||
| 4.1.2 Name, Role, Value | A | Partial support | Chat: need to ensure all possible chat elements are properly declared. Interactions: need to ensure all possible interaction elements and states are properly declared. |
In progress - Due Jun 2nd (Screen reader update) | TBC | |
| 4.1.3 Status Messages | AA | Partial support | Chat: need to be sure new chat messages are clearly declared when they come in. | In progress - Due Jun 2nd (Screen reader update) | ||
| 5.1.1 Conformance Level | A | Partial support | ||||
| 5.1.2 Full Pages | A | Not relevant | ||||
| 5.1.3 Complete Processes | A | Partial support | ||||
| 5.1.4 Only Accessibility-Supported Ways of Using Technologies | A | ✅Supported | ||||
| 5.1.5 Non-Interference | A | ✅Supported |
Reporting accessibility issues
If you have discovered an accessibility issue in our chat service, you can report it by sending an email to support@giosg.com. Use “Accessibility feedback” as the message subject and describe the issue in the email. It may take up to 14 days to receive an answer from us. If no answer is received within two weeks, or if you are not satisfied with the answer received, you can file a complaint.
Supervisory Authority
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
www.webaccessibility.fi
saavutettavuus@traficom.fi
telephone switchboard 029 534 5000