Giosg accessibility statement (WCAG 2.1)

This accessibility statement applies to the giosg Platform’s accessibility for website visitors. This statement has been updated on 16th June 2025.

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.


Giosg Live (chat)

The digital service complies fully with our target AA accessibility level requirements! 

The chat window language should be set by the Customer to match their web page. Then selected language should be automatically declared for screen readers.

Interaction Builder

The digital service complies fully with our target AA accessibility level requirements! 

IB users can now build interactions which are fully accessible. 

The person who creates the interaction is responsible of setting colours and labels so that it complies with accessibility requirements. IB will warn user on interaction publish page, if user has not set all required attributes in order to have accessible interaction.

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. These files are not automatically described or transcribed. The chat agent is responsible for explaining the content to the visitor. 

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 relevant: The criterion is not relevant to the product.

Latest updates


16th of June
1.4.10 Reflow
: ✅Supported 

6th of June

1.4.12 Text Spacing: ✅
Supported
1.4.10 Reflow:
improved, but full support is only enabled for few selected Customers
1.2.1 Audio-only and Video-only (Prerecorded): Supported
1.2.2. Captions (Prerecorded): Supported
1.2.5 Audio Description (Prerecorded): Supported

30th of May
2.4.6 Headings and Labels:
✅Supported 

30th of May
 
2.4.7 Focus Visible:  ✅
Supported
1.3.1 Info and Relationships: Supported 

28th of May 
Chat service complies fully with accessibility requirements!
1.3.5 Identify Input Purpose:
✅Supported
1.4.12 Text Spacing:
🕓Chat is now fully supported, interaction requires fixing
2.4.2 Page Titled
✅Supported
3.1.2 Language of Parts
✅Supported
3.3.2 Labels or Instructions
✅Supported
4.1.2 Name, Role, Value
✅Supported
4.1.3 Status Messages
✅Supported

27th of May 
1.4.4 Resize text:
Fully supported by chat and interactions
2.5.3 Label in Name: Fully supported by chat and interactions
3.1.2 Language of Parts: This is now supported by interactions


23th of May 
2.4.1 Bypass Blocks:
Both communication and interactions are now Supported
2.4.2 Page Titled: Interactions support is now fixed. Chat will be supported 30th of May.


13th of May
1.4.4 Resize text:
chat support fixed 
3.3.1 Error Identification: chat support fixed
3.3.3 Error Suggestion: chat support fixed

Success Criteria Overview

Supported: 48 criterias
Partial support: 0 criteria
Not supported: 0 criterias
Not relevant: 7 criterias

Table: Full list of Success Criterias

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 ✅Supported Chat: If video MUST be shared, it can be shared as an interaction that provides an accessible alternative

Interactions: Supported by using 3rd party video source in video element (Youtube, Video)
 ✅  
1.2.2. Captions (Prerecorded) A ✅Supported Chat: If video MUST be shared, it can be shared as an interaction that provides an accessible alternative

Interactions: Supported by using 3rd party video (Youtube, Video)
 
1.2.3. Audio Description or Media Alternative (Prerecorded) A ✅Supported Chat: If video MUST be shared, it can be shared as an interaction that provides an accessible alternative

Interactions: Supported by using 3rd party video source in video element (Youtube, Videom). 
 
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 ✅Supported Chat: If video MUST be shared, it can be shared as an interaction that provides an accessible alternative

Interactions: Supported by using 3rd party video source in video element (Youtube, Videom). 
 
1.3.1 Info and Relationships A ✅Supported Chat: Elements are properly named.
Interactions: Designer can define the element names.
 
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 ✅Supported Chat: Chat is labeled correctly
Interactions: Fields in interactions can be labeled by the designer. The expected content for fields can be set in interactions.
 
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 ✅Supported Site's stylesheets can still apply to interactions in some rare cases, where the default font size is changed in the HTML element on the website. This might cause the interaction may have wrong font sizes.  
1.4.5 Images of Text AA ✅Supported Images of text are not used.  
1.4.10 Reflow AA ✅Supported Chat: The chat window supports extreme zoom levels and small viewport sizes.
Interactions: Supports two different layout for each view; one for larger screens and one for smaller ones. IB has also flow constraint, which allows elements to adjust when browser's font size is increased. 
 
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 ✅Supported Chat: supports
Interactions: none
 ✅  
1.4.13 Content on Hover or Focus AA ✅Supported No such content in chat or interactions.  
2.1.1 Keyboard A ✅Supported Chat: Usable with keyboard.
Interactions: All elements are fully usable with the keyboard.
 
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 ✅Supported Both communication and interactions are supported.  Interaction Implement by   ✅  
2.4.2 Page Titled A ✅Supported Chat: Sets a name for the chat window and declares it when entering with a screen reader.
Interactions: This can be now achieved by setting a name for the interaction with IB .
 
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 ✅Supported Interactions: Text fields can be correctly labeled as headings by the designer.  
2.4.7 Focus Visible AA ✅Supported Focus is higlight is clearly visible on both chat and interactions.  
2.5.1 Pointer Gestures A Not relevant    
2.5.2 Pointer Cancellation A ✅Supported Supported in chat and interactions.  
2.5.3 Label in Name A ✅Supported Chat: Button names and labels are declared in chat. Interactions: The designer can define an accessibility label for each element.  
2.5.4 Motion Actuation A Not relevant No motion controls. - -  
3.1.1 Language of Page A Not relevant   - -  
3.1.2 Language of Parts AA ✅Supported
Chat: Language matches the chat window UI language. Interactions: Language matches the language of the website the interaction appears on.

 
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: An error is declared if the user attempts to send a message from an empty message field. Interactions: Errors are detected and declared in interactions.  
3.3.2 Labels or Instructions A ✅Supported Chat: Input fields are declared. Interactions: An accessibility label can be added to inputs, which is declared along with the field placeholder.  
3.3.3 Error Suggestion AA ✅Supported Chat: An error is declared when a user attempts to send a message from an empty input field using a screen reader. Interactions: Errors are detected in interactions and declared by screen readers. A custom error text can be defined by the designer.  
3.3.4 Error Prevention (Legal, Financial, Data) AA ✅Supported    
4.1.1 Parsing  A ✅Supported    
4.1.2 Name, Role, Value  A ✅Supported Chat:  All chat elements are properly declared.
Interactions: Interaction elements and states are properly declared.
 
4.1.3 Status Messages AA ✅Supported Chat: New chat messages are clearly declared when they come in.  
5.1.1 Conformance Level A ✅Supported All A level criterias are supported  
5.1.2 Full Pages A Not relevant   - -  
5.1.3 Complete Processes A  Not relevant   - -  
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