This is the accessibility statement for the Howspace platform.
This accessibility statement applies to the Howspace service. Howspace strives to meet the criteria outlined in the WCAG 2.2 guidelines at the AA and AAA levels.
Our goal is to provide digital services that are accessible to all users. In this accessibility statement, we outline the accessibility issues found within the service and explain how you can provide feedback and suggestions for improving the service’s accessibility.
This accessibility statement was published on 28.8.2024.
Updates:
| 1.7.2025 | Updated the document based on the accessibility fixes implemented |
| 26.11.2024 | Chatbot accessibility issues solved and removed from the documentation |
The description of the site’s accessibility is based on an assessment by Howspace and an external expert organization.
Status of the Digital Service’s Accessibility
The service largely meets accessibility requirements.
Non-Accessible Content
Accessibility issues are grouped under the following categories:
- Perceivable
- Operable
- Understandable
- Robust
Perceivable
Assistive technology users cannot access all analytics
Assistive technology users cannot access the information from the graphs because they lack text alternatives. (1.1.1)
There are deficiencies in the implementation of tooltip elements for assistive technology users
Tooltip content cannot be read with assistive technologies and the element lacks a role. (1.3.1)
View buttons might be difficult to interpret with assistive technology
View buttons might be difficult to interpret with assistive technology because the active choice isn’t conveyed programmatically. (1.3.1)
Assistive technology users may misunderstand the desired input for the email field
The desired input for the email field may be difficult to interpret with assistive tools. (1.3.1)
The contrast is insufficient in certain areas.
The contrast between the text and the background is not always sufficient. (1.4.3)
Some content is lost when the display is narrowed to 320 CSS pixels wide
When the display is narrowed to 320 CSS pixels wide, some content is lost. (1.4.10)
The contrast of keyboard focus is not always strong enough
In many instances, the contrast of the visible keyboard focus in relation to the background is too weak. (1.4.11)
Additional content that appears on pointer hover is not dismissible and/or hoverable
When the mouse is hovered over some elements, additional content that appears is not always dismissable and/or hoverable. (1.4.13)
Operable
All functionalities aren’t operable with a keyboard
Some functionalities cannot be used with only a keyboard. (2.1.1)
Focus order is not always logical
Occasionally there are deficiencies in the focus order when using the service. (2.4.3)
The purpose of individual links may be unclear to the user
The purpose of the example links may be unclear to the user. (2.4.4)
Focus is not always visible
Individual elements do not receive visible focus. (2.4.7)
Understandable
Input fields do not have a visible label
Some input fields do not have a visible label. (3.3.2)
Robust
Toggle buttons have a wrong attribute
Toggle buttons have an aria-expanded attribute when it is not required. (4.1.2)
Status messages are not conveyed programmatically
Status messages are not conveyed to assistive technology users.
Did you notice an accessibility issue in our digital service?
You can provide us with accessibility feedback or request non-accessible content in an accessible format by emailing to support@howspace.com. Please specify which page you are referring to and describe the issue as accurately as possible in your message.