Accessibility Statement

Accessibility Statement

Accessibility Statement

1. Accessibility Status

The website of Crasman Oy is not within the scope of accessibility legislation. However, we strive to ensure the accessibility of crasman.fi in accordance with the requirements of the WCAG 2.2 AA level.

The accessibility of the Crasman.fi website is based on our own assessment as well as a programmatic evaluation conducted with the Accessibility Keeper tool.

Based on the latest evaluation, the crasman.fi website partially meets the WCAG 2.2 guidelines' AA-level criteria. Partial compliance means that some features of the site do not meet accessibility requirements, meaning they do not fully support the use of assistive technologies, such as screen readers.

We want our website to be accessible to all users. Therefore, identified deficiencies on the site are actively corrected. We welcome users' feedback on accessibility and usability. Instructions for providing feedback can be found at the end of this statement.

2. Parts of the Site that do not Meet Accessibility Requirements

Our online service is not yet fully compliant with accessibility requirements. Below is a list of the content and functionalities of our online service that are not yet accessible.

Buttons Lack Accessible Names

All buttons on the website must have an accessible name.

The buttons on the Leadoo chatbot used on the Crasman.fi site do not have accessible names.

WCAG 4.1.2

Embedded Content not Named

Embedded content on the website (frames and iframes) must have a name that describes the embedded content.

The embed of the Leadoo chatbot used on the Crasman.fi site does not contain this information.

WCAG 4.1.2

HTML Document Lacks a Name

Each page on the website must have a name that describes the purpose of the page. The name appears, for example, in the title area of the browser window or tab. The HTML document should contain a title element, and it must not be empty.

The "Page Not Found" page on the Crasman.fi site lacks a title element.

WCAG 2.4.2

Minimum Contrast Between Text and Background is Insufficient

The text on the website must stand out sufficiently from its background so that the letters are easy to distinguish, and the text remains readable under different conditions for all users. The WCAG guidelines provide a formula for the contrast ratio between the color of the text and the color of the background.

On the Crasman.fi site, there are elements where the contrast of white text is insufficient against a light pink background. Additionally, there are text elements on the site where the background is a gradient. The contrast between the gradient and the text on it cannot always be guaranteed or programmatically ensured, but the sufficiency of the contrasts on the crasman-fi site has been checked by experts.

WCAG 1.4.3

Calendar Element ARIA Attribute Value is not Standard Compliant

The values of the ARIA attributes on the website must comply with the accessibility standard.

The appointment calendar from Hubspot used on the Crasman.fi site contains an ARIA attribute in the source code that is not compliant with the accessibility standard.

WCAG 4.1.2

Images Lack Text Alternatives

Image elements on the website must have a text alternative that conveys the meaning of the image. If the image is decorative and has no informational content, the text alternative should be empty.

Individual images on the Crasman.fi site were found to lack text alternatives.

WCAG 1.1.1

Interactive Elements Nested

The HTML standard for websites defines the type of content that each element can contain. User interface elements that can be clicked cannot be nested, for example, a button cannot be located within a link.

The contact form used on the Crasman.fi site has an incorrect HTML structure. The element contains focusable sub-elements.

WCAG 4.1.2

Form Fields Lack Labels

Form fields on the website should have a name that describes the purpose of the field, for example, to assistive technology users. The name of the form field is very important because the element is used for data entry. Form fields should have a defined name either as a visible label or through ARIA techniques.

The search field for site search on the Crasman.fi site lacks a label.

WCAG 4.1.2

Updated 11.11.2024