Accessibility statement for Visma Sign Forms service / Visma Solutions Oy
This accessibility statement applies to the Visma Sign Forms service and has been created / updated on 29.01.2024.
We have assessed the accessibility of the service ourselves.
The state of accessibility of the digital service
This service partially meets the accessibility requirements.
Non-accessible content
- Not covered by accessibility requirements
- content published on the service by users or other third parties that is not produced, funded or controlled by the service provider itself
The author of the form may define headings for form fields that are not understandable. The form author may also add links in the text that may be incomprehensible or foreign-language words in the text of the form.
The website is not yet fully compliant
Perceivable: contrast of graphic elements
Inaccessible content and its shortcomings
The alignment borders of the text fields, the ID type selection, the Add Signer and Sign buttons do not have enough contrast with the background.
Accessibility requirements that are not met
1.4.11 Contrast of non-textual content
Perceivable: Missing header levels
Inaccessible content and its shortcomings
The page does not use any heading level H1.
Accessibility requirements that are not met
1.3.1 Information and relations
Operable: page title
Inaccessible content and its shortcomings
The page title is always Visma Sign Forms.
Accessibility requirements that are not met
2.4.2 Page headers
Operable: Visibility of targeting
Inaccessible content and its shortcomings
There is no visible cursor in the Add File area.
Accessibility requirements that are not met
2.4.7 Focus visible
Understandable: Error handling
Inaccessible content and its shortcomings
The error messages for ID and file insertion do not explain how the user can cope with an error situation.
Accessibility requirements that are not met
3.3.3 Error suggestion
Understandable: Page language
Unaccessible content and its shortcomings
Regardless of the language specified for the form, the language of the page is always specified in English.
Accessibility requirements that are not met
3.1.1 Language of page
Robust: Name of buttons
Inaccessible content and its shortcomings
The buttons to delete the added file and the added signatories do not have a programmatically identifiable name.
Accessibility requirements that are not met
4.1.2 Name, role, value
Robust: The screen reader does not display error messages
Inaccessible content and its shortcomings
The screen reader does not read error messages in the personal identification number field and the file insertion area.
Accessibility requirements that are not met
4.1.3 Status messages
Did you notice an accessibility gap in our digital service? Let us know and we will do our best to remedy the deficiency
You can send feedback on accessibility issues with this feedback form. If there is an accessibility issue with the content of the form within the service, please contact the person who sent you the form.
We are constantly working to improve accessibility
This website/application was published in 2017.