Accessibility Statement
Helsinki City Theatre is committed to ensuring the accessibility of its online service in accordance with the Act on the Provision of Digital Services 306/2019. This accessibility statement applies to the hkt.fi website.
In the event of any ambiguity or discrepancy, the original Finnish-language text on the website will always take precedence and constitute the legally binding source of information.
Compliance status
The website partially complies with the requirements of the Act on the Provision of Digital Services 306/2019. Instances of non-compliance and exemptions applicable to the requirements are listed below. The accessibility issues we have identified are listed below under Non-accessible content.
We are working to improve our website and address accessibility issues through technical solutions, content editing and staff training. The identified accessibility issues have been documented in our project management tools and will be systematically addressed during 2027.
Non-accessible content
The following accessibility issues have been identified on the current website:
| Issue | Example |
|---|---|
| Generic link text does not indicate the link destination (WCAG 2.4.4) | An article uses the link text “here” (`<a href=”…”>täällä</a>`), which links to a PDF of the Teatteriin magazine |
| Long tab order on pages (WCAG 2.4.3) | On the News page and in other sections, the navigation menu and dozens of article links make keyboard navigation lengthy; users must press the Tab key dozens of times to reach the footer. |
| Multiple h1 headings on the same page (WCAG 2.4.6) | On the production page for “Let’s Play Business”, an h1 heading appears both in the hero section and in the production description. |
| Hidden calls to action “Buy tickets” and “Pre-order refreshments” (WCAG 2.4.7 / 4.1.2) | The call-to-action links in the hero section of the production page are hidden using visibility:hidden. |
| Focus indication is missing or insufficient (WCAG 2.4.7) | The first interactive element on the homepage (such as the logo or top navigation) does not display a clearly visible focus outline during keyboard navigation |
| The chat window is not accessible by keyboard (WCAG 2.1.1) | The “Hello! How can I help?” chat widget in the bottom-right corner cannot receive keyboard focus, and its X close button cannot be operated using the keyboard. |
| Illogical reading order (WCAG 1.3.2) | The reading order of the days in the calendar is unclear when using a screen reader. |
| Colour is used as the only means of conveying information (WCAG 1.4.1) | Different months and the current day are distinguished only by colour in the calendar. |
| Buttons do not have accessible names | The cookie banner contains a <button tabindex=”0″ id=”coi-expand”> button with no visible name or aria-label; a screen reader cannot determine the purpose of the button. |
| Input field has no name (Field name) | <textarea id=”comment” aria-required=”true”></textarea> without a label, aria-label or aria-labelledby attribute. |
| Invalid ARIA attributes (Allowed ARIA attributes) | A paragraph element has an aria-level attribute (e.g. <p aria-level=”3″>), which is not permitted. |
| Insufficient text colour contrast (Color contrast) | The text colour #2bb976 on the background #ffffff has a contrast ratio of 2.52 (< 4.5:1). |
| Links in text blocks are distinguished only by colour (Link in text block) | Text links in #0677c7 alongside body text in #000000; no underline and a contrast ratio of 2.69. |
| Videos do not have captions or audio descriptions (Video captions) | Embedded videos without closed captions or transcripts. |
| Link does not have a clear name (Link name) | The link is included in the tab order but has no visible text or aria-label; e.g. <a href=”#top”><i aria-hidden=”true”></i><span>Menu</span></a>. |
| The page has no lang attribute (Document language) | The <html> element has no lang=”fi” attribute. |
| Content is not contained within designated regions (Landmark) | Pages contain content that is not within <main>, <nav>, <header> or other landmark elements. |
| Missing main <main> element (Main landmark) | The document does not contain any <main> landmark elements. |
| Landmark names are not unique (Unique landmark) | Multiple <nav> elements without an aria-label or heading. |
| Heading levels are skipped (Heading order) | The code uses <h5> immediately after an <h1> heading without the intervening levels. |
| Missing <h1> heading (H1 heading) | Some pages have no <h1>-level heading. |
| Empty headings (Empty heading) | <h3></h3> without content. |
| Invalid use of an ARIA role (Allowed ARIA role) | <a class=”header__logo” role=”img” …> – an anchor must not have the img role. |
| Invalid scope attribute (Valid scope attribute) | <td scope=”col”> is used in a <td> element. |
| Redundant links with href=”#” that lead nowhere (WCAG 2.4.4) | In a staff profile on the Contact details page, both the image and name are links whose href attribute is “#”, creating unnecessary focus points |
| Insufficient keyboard accessibility (WCAG 2.1.1) | Some menus and functions cannot be accessed using the Tab key. |
| Form fields have no labels (WCAG 3.3.2/4.1.2 – Field name) | Form elements such as textarea have no label or aria-label attribute; Webwarden reports that the fields have no implicit or explicit name |
| Videos do not have captions (WCAG 1.2.2 – Captions) | Embedded videos (e.g. YouTube) do not have captions; Webwarden’s findings indicate that users cannot access the video content without sound |
| Invalid ARIA attributes (WCAG 4.1.2 – Allowed ARIA attributes) | The pages use the prohibited aria-level attribute in basic elements (e.g. <p aria-level=”3″> or <p aria-level=”5″>); Webwarden notes that aria-level is not permitted in the element concerned |
| Invalid ARIA role (Allowed ARIA role) – recommendation | For example, role=”img” has been added to an anchor, although it is not permitted for that element; Webwarden identifies the role as invalid |
| Link elements do not have clear names (Link name) – WCAG 2.4.4, 4.1.2 | For example, the arrow link <a href=”#top”><i class=”fa fa-chevron-up” aria-hidden=”true”></i><span>Menu</span></a> does not contain a name that can be identified by a screen reader |
| Insufficient contrast (WCAG 1.4.3 & 1.4.11) | Text over images and some buttons are difficult to read. |
| Insufficient colour contrast ratio (WCAG 1.4.3/1.4.11) | Webwarden reports several colour combinations where the text contrast ratio is too low (e.g. #2bb976 on a white background, with a contrast ratio of 2.52), which does not meet the 4.5:1 requirement |
| Page content is not contained within landmarks (recommendation) | Webwarden’s recommendations state that some content is not contained within designated landmark regions and may be difficult to navigate using a screen reader |
| Main content element is missing (Main landmark) – recommendation | Several pages do not have one clear <main> element; Webwarden notes that the document has no main landmark |
| Landmarks are not unique (Unique landmark) – recommendation | The website has multiple nav regions without unique aria-label or title attributes; Webwarden emphasises that landmarks should be unique |
| Illogical heading hierarchy (Heading order) – recommendation | Heading levels are skipped on the pages (e.g. h1-h3-h5); Webwarden notes that headings should be used in ascending order |
| H1 heading is missing (H1 heading) – recommendation | Some pages do not contain an <h1> heading at all; Webwarden reports 36 instances of a missing h1 |
| Empty heading tag (Empty heading) – recommendation | <h3></h3> without content. |
| Scope attribute in the wrong element (Valid scope attribute) – recommendation | In one table, the scope attribute is placed in a td element instead of a th element; Webwarden identifies this as an error |
| Active tab is not indicated (WCAG 4.1.3) | Tab components do not indicate which tab is open. |
| Inadequate page titles (WCAG 2.4.2) | The titles of some pages do not describe the content of the page. |
| Generic link text (WCAG 2.4.7) | “Read more” links do not indicate where they lead. |
| Inconsistent navigation (WCAG 3.2.3) | Some pages lack navigation mechanisms or use mechanisms that differ from those on other pages. |
| Page lacks local navigation (table of contents) | The News page does not have a context–navigation section; other relatively long pages, such as Contact details and Getting here, include a list of links to different sections (e.g. Customer service, Restaurant services) |
| Internal navigation is missing (no skip links to sections) | The source code of the Calendar page does not contain a context–navigation list, whereas the Contact details page has clear internal navigation (#asiakaspalvelu, #sodexon-ravintolapalvelut, #laskutustiedot) |
| The long homepage lacks an internal navigation list | The homepage is long and contains several sections, but it does not include a context–navigation section; a similar table of contents is available on the Contact details and City Theatre pages (e.g. Staff, Theatre building, Archive) |
| Unnamed links and icons (WCAG 2.4.4/4.1.2) | Icons or images are used as links and buttons without visible text descriptions or aria-label attributes; Webwarden reports that the links have no accessible names |
| Document language is missing (WCAG 3.1.1 – Document language) | Some pages do not define a lang attribute in the html element; Webwarden notes that <html> does not contain a lang attribute |
| Main content has no main landmark | The HTML source code uses <nav> elements, but the main content is not contained within a <main> element or an element with the role=”main” attribute; a screen reader cannot skip directly to the main content. |
| Hidden buttons on the ticket purchase page are visible to screen readers | In the hero section, the “Buy tickets” buttons are hidden using CSS (`visibility:hidden`) but do not have aria-hidden, meaning that a screen reader may still focus on the button. |
| The mobile navigation menu icon is not accessible by keyboard | On mobile devices, the hamburger icon that opens the menu is an `href=”#”` anchor that cannot receive keyboard focus and has no aria-label |
| Hidden ‘Buy tickets’ buttons are not accessible by keyboard | The Buy tickets buttons in the homepage hero section are hidden using CSS (`visibility:hidden`), so they cannot receive keyboard focus but are still available to screen readers |
| The calendar’s month navigation arrows have no names | The previous/next arrows in the calendar are `href=”#”` anchors without visible text or aria-labels; a screen reader cannot determine where they lead. |
| Redundant links in staff profiles lead nowhere | The staff profiles on the Contact details page are wrapped in links with `href=”#”` that perform no action; keyboard focus stops unnecessarily on these links |
Certain content is not covered by the applicable legislation
Our YouTube channel contains video content published before 23.9.2020. Some of this video content does not have captions and/or audio descriptions. Under the applicable legislation, video content published before 23.9.2020 does not need to be made accessible retrospectively or removed.
Our production archive, files in the publications directory and sections of the website created using special technologies such as virtual panoramas are not accessible because they are temporarily subject to the disproportionate burden exemption referred to in Article 5 of Directive (EU) 2016/2102. The files in these sections are not fully accessible because the number of files is considerable and the website administrator has no cost-effective or automated means of making this content compliant with the accessibility requirements.
Preparation of this accessibility statement
This statement is based on an accessibility audit conducted by the external expert organisation Knowit Oy on 27.8.2025. The statement was last updated on 14.10.2026 following measures taken to improve accessibility.
Feedback and contact details
We will continue to identify accessibility issues and address them as part of the ongoing development of our website. Please contact us if you identify any accessibility issues on our website that are not listed above.
You can send us accessibility feedback or request guidance on using our website by email at [javascript protected email address]
If you provide your contact details, we will respond to your feedback as soon as possible.
Enforcement procedure
If you identify any accessibility issues on the website, please first contact us as the service provider. We will respond to feedback within 14 days if you have provided your contact details. If you are not satisfied with our response or do not receive a response within 14 days, you can contact the supervisory authority, the Finnish Transport and Communications Agency Traficom. The Finnish Transport and Communications Agency Traficom website explains how to submit a complaint and how it will be processed.
Contact details of the supervisory authority
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
PL 320
00059 TRAFICOM
Switchboard 029 534 5000