About this website

Espoonasunnot.fi is the official website of Espoon Asunnot. We want the site to be smooth and easy to use. We are constantly improving the user experience. On this page, we explain the cookies and web analytics we use. You will also find information about the accessibility of the website.

Cookies

A cookie is a small text file that is saved to your browser when you visit a website. Cookies help the site function properly, remember your choices, and collect information about your usage so we can improve our service.

We use the following types of cookies:

  • Necessary cookies enable the safe and technically functional use of the website.
  • Functional cookies remember your preferences, such as language settings.
  • Analytics cookies collect information about how the site is used. The data is anonymous and cannot be used to identify you.
  • Advertising cookies make it possible to show more relevant ads in other services, such as Facebook or Google. If you accept these cookies, data may be shared with advertising platforms, which may link it to their own user information.

Analytics tools in use

  • Google Analytics: Tracks data such as the number of visitors, the most popular pages, and the types of devices used.
  • Google Tag Manager: Technically manages the tracking codes on the website.
  • Askem: Collects feedback and information on how content is read and shared. The data is stored by Espoon Asunnot and is not shared with third parties.

Advertising tools in use

  • Facebook Pixel: Tracks how users arrive at our site from Facebook ads and how they behave on the site. Facebook may link this information to your user profile to personalize advertising.

    You can manage these cookie settings by adjusting the advertising cookies option under the Settings tab in the cookie window, or by changing your ad preferences in your Facebook account.

  • Google Ads: Tracks the effectiveness of ads and helps target advertising within Google services. Google may link this information to your user profile.

    You can manage these cookie settings by adjusting the advertising cookies option under the Settings tab in the cookie window, or by changing your ad preferences in your Google account.

Managing cookies

You can manage cookies in two ways:

  1. Website cookie settings
    In the cookie banner displayed on the site, you can choose which cookies you accept. Necessary cookies cannot be disabled, but you can choose to disable functional, analytics, and advertising cookies if you wish.
  2. Browser Settings
    You can block all cookies or delete previously stored cookies through your browser settings. This may affect how the website functions. The location of these settings depends on your browser and device.

If you clear your browsing history, all cookies will also be deleted. This may also remove saved login information and site-specific preferences.

Accessibility

Our goal is to ensure that the website is accessible to all users. We are developing the site in accordance with accessibility requirements and comply with the Finnish Act on the Provision of Digital Services (306/2019).

Accessibility statement

This statement was produced on 05 November 2025 and is based on a third-party assessment of whether the service meets the requirements presented in the Act on the Provision of Digital Services 306/2019.

This statement was last updated on 5 November 2025.

State of accessibility

Espoon Asunnot partially meets the requirements of Level 2.1 AA of the Web Content Accessibility Guidelines (WCAG). The specific instances of non-compliance are listed below.

Inaccessible content

The following content is not accessible for the following reasons: Non-compliance with the Act on the Provision of Digital Services 306/2019

Espoonasunnot.fi

Visual elements

  • Contrast: The white text that is displayed on the selected day in the calendar does not stand out sufficiently from the green background. (WCAG 1.4.3)
  • Text spacing: Only part of the site’s text content responds to the user’s text-spacing settings. (WCAG 1.4.12)
  • Focus indicator visibility Some elements lack a sufficiently distinct or visible focus indicator style. (WCAG 2.4.7)

Structure

  • Language settings and translations: The error messages on forms, along with their alt texts for screen readers, are partially available in English only. (WCAG 3.1.2)
  • Alt texts: Some images, links, and buttons are missing descriptive alt texts. (WCAG 1.1.1, 1.3.1)
  • Headings: There are issues in the use of headings. Heading hierarchies often do not match the hierarchy of the related page contents. (WCAG 1.3.1)
  • Compatibility between programmatic and visual implementations: The social media links in the footer are missing a list element. The language menu’s programmatic configurations have not been fully implemented. When viewed on a mobile device, the search and main menu buttons are missing programmatic configurations describing their functionality. (WCAG 1.3.1, 4.1.2)
  • Notifications and feedback: Screen readers cannot detect when an update is made to the “Current topics” list when changing the content type. (WCAG 4.1.3)
  • Active item highlights The active page on the breadcrumb trail is missing a programmatic definition indicating its active status. (WCAG 1.3.1)

Form elements

  • Form field labels: The list filter menu on the “Current topics” page lack a visible label. (WCAG 2.5.3)
  • Mandatory fields: All mandatory form fields are marked with an asterisk, but the purpose of this character is not explained in the form. (WCAG 3.3.2)
  • Form groups: Checkboxes have not been grouped programmatically. (WCAG 1.3.1)

Element-specific observations

  • Cookies:
    • Some of the alt texts for the cookie consent dialog are only available in English. (WCAG 3.1.2)
    • The switch elements in the cookie consent dialog use only colour to indicate their selected value state. (WCAG 1.4.1)
    • The Save Settings button in the cookie consent dialog changes to a notification when any cookie-related settings are changed. (WCAG 4.1.2)
    • The texts in the cookie consent dialog do not comply with the user’s text-spacing settings. (WCAG 1.4.12)
    • Alt text has not been set for the arrow button in the cookie consent dialog. (WCAG 1.1.1)
    • The help text in the cookie consent dialog relies solely on visual features to describe how the dialog's opening function can be accessed. (WCAG 1.3.3)
  • Chatbot:
    • The contrast between the text and background colours is insufficient. (WCAG 1.3.4)
    • Texts do not comply with the user’s text-spacing settings. (WCAG 1.4.12)
    • The contrast between user interface elements and graphic elements is insufficient. (WCAG 1.4.11)
    • The message field has not been given a label. (WCAG 1.3.1)
    • Some alt texts are only available in English. (WCAG 1.1.1, 3.1.2)
    • There is an invisible, focusable button next to the message field. (WCAG 2.4.3)
    • The number of messages cannot be detected by screen readers. (WCAG 1.1.1, 1.3.1)
    • There is no button for sending a message. Instead of a button, there is an image whose alt text is in English. (WCAG 3.1.2, 4.1.2)
  • Parking space form:
    • The date in the date field cannot be entered in the Finnish format when using a keyboard. (WCAG 2.1.1, 3.3.2)
Online services for applicants and residents

Visual elements

  • Contrast: The contrast between the text and background is insufficient, for example in the ARA application buttons. There are also some shortcomings in the contrasts used for user interface components. (WCAG 1.4.3, 1.4.11)
  • Scalability: Some texts are cut off on a screen that is 320 CSS pixels wide. (WCAG 1.4.10)
  • Focus indicator visibility In some areas, the focus indicator is poorly visible or only distinguishable by its colour. (WCAG 1.4.11)

Structure

  • Alt texts: The alt texts for visual elements are insufficient.  Some visual buttons and links have insufficient alt texts. Many illustrations are not properly hidden from screen readers. (WCAG 1.1.1, 2.5.3, 4.1.2)
  • Headings: Heading element hierarchies do not always match the hierarchy of the related page contents. Some headings and sub-headings share the same heading level. Some headings have not been programmatically marked as headings. Some pages contain extraneous heading markings. (WCAG 1.3.1)
  • Logical ordering: Data is not always read in logical order. When navigating the “Residents” section, screen readers read visually hidden contents on different pages, which can potentially mislead users.  (WCAG 1.3.2)
  • Tables: The markup used in tables is partially insufficient. Some tables have empty column headers. (WCAG 1.3.1)
  • Compatibility between programmatic and visual implementations: Heading-value pairs are not presented programmatically. (WCAG 1.3.1)
  • Programmatic role: The programmatic role of many buttons and links is erroneous. (WCAG 4.1.2)
  • Button purpose: Some buttons lack descriptive names indicating their purpose. (WCAG 2.4.6)
  • Keyboard navigation: Some elements cannot be navigated using a keyboard, for example when attempting to select the “With username" option on the login screen. (WCAG 2.1.1, 4.1.2)
  • Link purpose: The skip link used on the “Housing offer” page to bypass navigation unexpectedly directs the user to the “Welcome” page. (WCAG 2.4.4)
  • Focus order: The focus order includes extraneous focusable elements. The focus order does not always progress logically, for example on the “Log in” page. Focus is not always logically shifted to, for example, modal dialogues. (WCAG 2.4.3)
  • Navigation area names: The names used for navigation areas are not always descriptive. (WCAG 2.4.6)
  • Page names: Page names are not descriptive or unique. (WCAG 2.4.2)
  • Page transitions: Page transitions are not indicated consistently. Screen readers are not always able to announce the name of a new page. (WCAG 2.4.3, 4.1.3)

Logouts

  • Login time limit: Sessions remain valid only for a set period of time. The user is not warned of this fact in advance or provided with any means for staying logged in. (WCAG 2.2.1)

Form elements

  • Passive buttons: Some applications use passive buttons to indicate when mandatory information has not been filled in. (WCAG 1.3.1, 3.3.1)
  • Form field labels:  The label for the “Password” field on the “Log in” page has not been programmatically linked to the form field. (WCAG 1.3.1)
  • Form groups: Not all form groups are programmatically marked as groups, and the groups’ headings are not linked to the groups. (WCAG 1.3.1)
  • Programmatic marking of forms: Radio buttons have been programmatically marked as links. The "Select theme" option has been programmatically implemented as accordions.  (WCAG 2.1.3, 4.1.1)
  • Mandatory fields: All mandatory form fields are marked with an asterisk, but the purpose of this character is not explained in the form. (WCAG 3.3.2)
  • Field-specific instructions: Field-specific instructions are not always visible to screen readers. (WCAG 3.3.2)
  • Differentiation of form elements: The checkboxes and radio buttons in the ARA application are not always distinguishable from one another. (WCAG 3.2.4)

Element-specific observations

  • Settings:
    • The button's accessible name does not contain the text displayed on the button. (WCAG 2.5.3)
    • The close button on the opened menu has been implemented programmatically as a link. (WCAG 4.1.2)
    • Focus is not maintained in the open area, and the area has not been programmatically marked. (WCAG 1.3.1, 2.4.3)
  • Cookies:
    • The contrast between the text and background colours is insufficient. (WCAG 1.3.4)
    • When the switch is in the off position, the contrast of the switch is insufficient. (WCAG 1.4.11)
    • In the case of accordions, screen reader users are provided with extraneous information. (WCAG 4.1.2)
    • When the browser’s zoom level is set to 200%, some of the text is cut off. (WCAG 1.4.4)
  • Language menu and social media menu:
    • The accessible name of the buttons is not descriptive enough. The button that opens the language menu does not contain the text displayed on the button. The arrow icon has not been properly hidden from screen readers. (WCAG 1.1.1, 2.5.3, 4.1.2)
    • The status of the button is not indicated programmatically. (WCAG 4.1.2)
    • The selections are not available programmatically within the list. (WCAG 1.3.1)
    • Users must navigate backwards to access language options. (WCAG 2.4.3)
  • Progress indicator:
    • No name has been given to the progress indicator. (WCAG 1.3.1)
    • The completed steps and current step on the progress indicator are marked visually but not programmatically. (WCAG 1.3.1)
    • The percentage figure has been given an additional and undescriptive aria-label in some places. (WCAG 1.3.1)
    • The mobile button used to open the progress indicator is deficient. The button’s name is not descriptive, and it has been implemented programmatically as a link. The button’s state is not fully defined. Focus is not shifted to the opened progress indicator. (WCAG 2.4.3, 4.1.2)

Give feedback on accessibility

We welcome feedback on the accessibility of this website. If you notice any accessibility issues, please let us know. We will respond within 14 days.

Email: asiakaspalvelu@espoonasunnot.fi
Phone: 09 3544 5000

If you do not receive a response or are not satisfied with the reply, you can contact the supervisory authority, Traficom. Instructions on how to make a complaint and how it will be handled are available on Traficom's website.

Contact Information of the Supervisory Authority
Finnish Transport and Communications Agency Traficom
Accessibility Monitoring Unit
www.saavutettavuusvaatimukset.fi/en
saavutettavuus@traficom.fi
Phone: 029 534 5000 

See also

Data protection