Accessibility statement
Helsinki City Theatre strives to guarantee the accessibility of its Internet service in accordance with the Act on the Provision of Digital Services 306/2019. This accessibility statement applies to the hkt.fi website.
Compliance status
The website partially meets the requirements of the Act on the Provision of Digital Services 306/2019. Non-compliances and exceptions to the requirements are mentioned below. The accessibility issues we have identified are listed below under Non-accessible content.
We aim to develop our website and fix accessibility problems through programming solutions, content editing and staff training. Detected accessibility issues are documented in our project management tools and are systematically fixed.
Non-accessible content
Accessibility problems have been detected on the current website:
| Attention | Example |
|---|---|
| Generic link text does not indicate the object of the link (WCAG 2.4.4) | The article uses the link text "here" (‘<a href="… ">here</a>’), which takes you to the pdf of the Teatteriin magazine |
| Long tab order on pages (WCAG 2.4.3) | On the News page and other sections, the nav menu and dozens of article links make the Tab navigation long; The user has to tab dozens of keystrokes to get to the footer. |
| Multiple h1 headings on the same page (WCAG 2.4.6) | On the presentation page, “Let’s Play Business” has an h1 heading in both the hero section and the description of the presentation. |
| Hidden call to action “Buy tickets” and “Order refreshments” (WCAG 2.4.7 / 4.1.2) | In the hero section of the presentation page, call-to-action links are hidden in the style visibility:hidden. |
| Focus emphasis is absent or weak (WCAG 2.4.7) | The first interactive element on the homepage (e.g. logo or top menu) does not display a clearly visible focus frame in Tab navigation |
| The chat window is not accessible with a keyboard (WCAG 2.1.1) | At the bottom right, the “Hello! Can I help?” chat widget doesn’t get a tab focus, and its X-close button can’t be operated with a keyboard. |
| Illogical timetable (WCAG 1.3.2) | The schedule of the days in the calendar is unclear with a screen reader. |
| Colour as the only means of communication (WCAG 1.4.1) | In the calendar, the different months and the current day are separated only by color. |
| Button names are not accessible | The cookie banner has a button <button tabindex="0" id="coi-expand"> which has no visible name or aria-label; The screen reader does not know the purpose of the button. |
| Field name | <textarea id="comment" aria-required="true"></textarea> without the label, aria-label, or aria-labelledby attribute. |
| Invalid ARIA attributes (Allowed ARIA attributes) | The paragraph element has an aria-level attribute (e.g. <p aria-level="3">), which is not allowed. |
| Poor color contrast in text (Color contrast) | The text color #2bb976 in the background #ffffff gives a contrast ratio of 2.52 (< 4.5:1). |
| Links are only distinguished by color in text blocks (Link in text block) | Text links #0677c7 with the background text #000000; No underlining and contrast ratio 2.69. |
| Videos do not have subtitles or audio descriptions (Video captions) | Embedded videos without closed captions or transcripts. |
| Link name | The link is in tab order, but it doesn’t have visible text or aria-label; e.g. <a href="#top"><i aria-hidden="true"></i><span>Menu</span></a>. |
| The page is missing the lang attribute (Document language) | The <html> element does not have the lang="fi" attribute. |
| Content has no marked areas (Landmark) | Pages contain content that is not in <main>, <nav>, <header> or other landmark elements. |
| Missing main<main> element (Main landmark) | There are no <main> landmark elements in the document. |
| Unique landmark names | Multiple <nav> elements without aria-label or title. |
| Heading order | The code uses <h5> immediately after the <h1> header without any intermediate steps. |
| Missing <h1> heading (H1 heading) | Some pages don’t have a <h1>level heading at all. |
| Empty headings | <h3></h3> without content. |
| Incorrect use of the ARIA role (Allowed ARIA role) | <a class="header__logo" role="img" … > – anchor must not have a role img. |
| Invalid scope attribute (Valid scope attribute) | <td scope="col"> used in the <td> element. |
| Unnecessary links with href="#" lead nowhere (WCAG 2.4.4) | On the person card on the Contact page, both the image and the name are links with the href attribute “#”, so they are useless focus points |
| Keyboard usability is inadequate (WCAG 2.1.1) | Some menus and functions are not accessible with the tab key. |
| Form fields are missing a label (WCAG 3.3.2/4.1.2 – Field name) | Form elements such as textarea do not have a label or aria-label attribute; Webwarden lists that the fields do not contain any implicit or explicit name |
| Videos are missing subtitles (WCAG 1.2.2 – Captions) | In video embeds (e.g. YouTube) has no subtitles; Webwarden findings suggest that users are not receiving video content without sound |
| Invalid ARIA attributes (WCAG 4.1.2 – Allowed ARIA attributes) | Pages use the forbidden aria-level attribute for basic elements (e.g., <p aria-level="3"> or <p aria-level="5">); Webwarden notes that aria-level is not allowed in that element |
| Incorrect ARIA role (Allowed ARIA role) recommendation | For example, role="img" has been added to the anchor, which is not allowed with that element; Webwarden points out that the role is incorrect |
| Link elements do not have a clear name – WCAG 2.4.4, 4.1.2 | For example. Arrow key link <a href="#top"><i class="fa fa-chevron-up" aria-hidden="true"></i><span>Menu</span></a> does not contain a distinctive name for the screen reader |
| Low contrast (WCAG 1.4.3 & 1.4.11) | The text on top of the images and some of the buttons are difficult to read. |
| Poor color and contrast ratio (WCAG 1.4.3/1.4.11) | Webwarden reports multiple color combinations where the contrast ratio of the text is too low (e.g., #2bb976 on a white background, contrast ratio 2.52), which does not meet the 4.5:1 requirement |
| Page content is not in landmarks (recommended) | Webwarde’s recommendations state that some content is not within the specified landmark areas and can be difficult to navigate with a screen reader |
| Missing main content element (Main landmark) – recommendation | Several pages are missing one clear <main> element; Webwarden notes that there is no main landmark in the document |
| Unique landmarks – recommendation | The site has multiple nav regions with no unique aria-label or title attributes; Webwarden emphasizes that landmarks should be unique |
| Heading Hierarchy Illogical (Heading order) Recommendation | On pages, heading levels are used in jumps (e.g. h1-h3-h5); Webwarden reminds us that headings should be used in ascending order |
| Missing H1 heading (H1 heading) – recommendation | Some pages don’t contain a <h1> heading at all; Webwarden reports 36 cases where h1 is missing |
| Empty heading tag – recommendation | <h3></h3> without content. |
| Scope attribute in the wrong element (Valid scope attribute) – recommendation | In one array, the scope attribute is placed in the td element and not in the th element; Webwarden recognizes this as an error |
| Active tab not indicated (WCAG 4.1.3) | Tab components don’t tell you which tab is open. |
| Incomplete headings (WCAG 2.4.2) | Some page titles don’t describe the content of the page. |
| Generic link texts (WCAG 2.4.7) | The link texts “Read more” do not tell you where they lead. |
| Inconsistent navigation (WCAG 3.2.3) | Some pages lack navigation mechanisms or differ from other pages. |
| The page lacks local navigation (table of contents) | The news page does not have a context-navigation section; other rather lengthy pages, such as the Contact and Arrival pages, have a list of links to different sections (e.g. Customer service, restaurant services) |
| Lacks internal navigation (no jump links to sections) | The source code of the calendar page does not include a context–navigation list, while the Contact page has clear internal navigation (#asiakaspalvelu, #sodexon restaurant services, #laskutustiedot) |
| The long front page lacks a list of internal navigation | The homepage is long and has several sections, but it does not include a context-navigation section; a corresponding table of contents can be found on the Contact Information and City Theatre pages (e.g. Staff, Theatre House, Archive) |
| Anonymous links and icons (WCAG 2.4.4/4.1.2) | Links and buttons are simply icons or images without a visible text description or aria-label attribute; Webwarden says that the links do not have an accessible name |
| Document language is missing (WCAG 3.1.1 – Document language) | Some pages do not specify the lang attribute in the html element; Webwarden states that <html> does not contain the lang attribute |
| The main content does not have a main landmark | The HTML source code uses <nav> elements, but the main content is not inside the <main> element or the role="main" attribute; The screen reader cannot jump directly to the main content. |
| Hidden buttons on the ticket purchase page are visible to the screen reader | In the Hero section, the ‘Buy Tickets’ buttons are hidden with CSS (‘visibility:hidden’), but without aria-hidden, allowing the screen reader to still align the button. |
| The mobile navigation menu icon is not accessible with the keyboard | On mobile, the hamburger icon that opens the menu is an anchor ‘href="#"’ and it doesn’t get a Tab focus and doesn’t have an aria-label |
| Hidden ‘Buy Tickets’ buttons are not accessible on the keyboard | In the hero section of the front page, the Buy Tickets buttons are hidden with CSS (‘visibility:hidden’), so they don’t get a Tab focus but are still in the screen reader |
| The arrows in the monthly navigation of the calendar do not have a name | The previous/next arrows on the calendar are anchors ‘href="#"’ without visible text or aria-label; The screen reader doesn’t know where they will take you. |
| Unnecessary links in ID cards lead nowhere | The ID cards on the Contact page are wrapped in links that have ‘href="#"’ but do nothing; The tab stops unnecessarily at these links |
Certain content is not covered by applicable law
The YouTube channel we manage contains video content published before 23.9.2020. Some of this video content lacks subtitles and/or audio descriptions. According to the law, video content published before 23 September 2020 does not need to be made retroactively available or removed.
Our presentation archives, files in the publications directory and sections of the content of our website implemented with special technologies such as virtual panoramas are not accessible because they are temporarily subject to the exception referred to in Article 5 of Directive (EU) 2016/2102 due to an unreasonable burden. The files in these sections are not accessible in all respects, as the number of files is significant and the site administrator does not have cost-effective or automated methods to make these contents meet the accessibility requirements.
Preparation of this accessibility statement
The statement is based on an accessibility audit conducted by the external expert organisation Knowit Oy on 27 August 2025. The statement was last modified due to corrective measures related to accessibility on 7.12.2025
Feedback and contact information
We will continue to map accessibility problems and fix them as part of the continuous development of our website. Please contact us if you notice any accessibility problems other than those listed above on our website
You can give us accessibility feedback or ask for instructions on how to use our website by email at [javascript protected email address]
If you leave your contact information, we will respond to your feedback as soon as possible.
Enforcement procedure
If you notice accessibility deficiencies on the website, please first contact us as a service provider. We will respond to feedback within 14 days if you have left your contact information. If you are not satisfied with the response you have received or do not receive a response within 14 days, you can contact the supervisory authority, i.e. the Finnish Transport and Communications Agency Traficom. The website of the Finnish Transport and Communications Agency Traficom provides information on how to file a complaint and how to process it.
Contact details of the supervisory authority
Finnish Transport and Communications Agency Traficom
Digital Accessibility Monitoring Unit
P.O. Box 320
00059 TRAFICOM
Phone number switchboard 029 534 5000 (switchboard)