{"id":5679,"date":"2026-06-19T11:35:58","date_gmt":"2026-06-19T08:35:58","guid":{"rendered":"https:\/\/www.riigikogu.ee\/?page_id=5679"},"modified":"2026-09-17T13:26:07","modified_gmt":"2026-09-17T10:26:07","slug":"accessibility","status":"publish","type":"page","link":"https:\/\/www.riigikogu.ee\/en\/accessibility\/","title":{"rendered":"Accessibility"},"content":{"rendered":"\n
\n
\n

On this page, you can find information about access to Toompea Castle, and using the Riigikogu website.<\/strong><\/p>\n\n\n\n

Access to Toompea Castle<\/h3>\n\n\n\n

Toompea Castle is accessible to visitors with mobility disabilities. All major rooms \u2013 the visitors\u2019 gallery of the Session Hall, the Conference Hall of the Riigikogu, the White Hall and most of the working rooms \u2013 are wheelchair accessible. However, not all working rooms are accessible to visitors with mobility disabilities. When planning a visit, please consult the person who invited you about accessibility, or write to info@riigikogu.ee<\/a>.<\/p>\n\n\n\n

Visiting the Riigikogu<\/h4>\n\n\n\n

The left entrance of Toompea Castle is accessible by a ramp without steps. Next to the door, at the wheelchair level, there is a doorphone through which the reception desk can be contacted. An employee of the Riigikogu Chancellery will be called to receive the guest with mobility disability and accompany them to the building. All visitors of the Riigikogu are always accompanied by an official of the Chancellery in the Riigikogu buildings. Toompea Castle can be entered on wheelchair through the car gate.<\/p>\n\n\n\n

If a guest with mobility disability arrives by a taxi, the taxi can stop at the lay-by next to the entrance of the parking lot, and the guest has to reach the entrance of the Riigikogu by themselves. Guests with mobility disabilities arriving by car have to apply for a parking permit first, like all other visitors. The car park workers allow to park the car on the parking lot after a permit has been issued.<\/p>\n\n\n\n

Toompea Castle has a WC and two lifts accessible for disabled persons, and two platform elevators for moving between different parts of the building complex.<\/p>\n\n\n\n

Accessibility notice of the Riigikogu home page<\/h3>\n\n\n\n

This website is owned by the Chancellery of the Riigikogu. We want www.riigikogu.ee<\/a> to be in compliance with the accessibility requirements established under Section 32 of the Public Information Act.<\/p>\n\n\n\n

At the end of this notice, you will find contact details you can turn to if you experience problems with the accessibility of the website.<\/p>\n\n\n

\n \n \n Compliance status<\/accordion-trigger>\n \n
\n

This website is partially compliant with accessibility requirements for the reasons listed below.<\/p>\n\n <\/div>\n <\/accordion-content>\n <\/accordion-item>\n \n Non-accessible content and features<\/accordion-trigger>\n \n

\n

The content and functions listed below are not in compliance with the requirements of standard EN 301 549.<\/p>\n

Images are missing alternative text<\/h4>\n

Some pages contain images or images used as links that do not have alternative text. As a result, screen reader users may not receive information about the content of the image or the purpose of the link.<\/p>\n

Therefore, accessibility requirement 9.1.1.1 (Non-text Content) is not met.<\/strong><\/p>\n

Videos and live broadcasts have accessibility shortcomings<\/h4>\n

Some prerecorded videos do not provide captions, audio descriptions, or text alternatives for visual information that is not conveyed through audio. In addition, captions are not always provided for live broadcasts. As a result, users who are deaf, hard of hearing, blind, or visually impaired may not be able to access all of the information presented.<\/p>\n

Therefore, accessibility requirements 9.1.2.2 (Captions (Prerecorded)), 9.1.2.3 (Audio Description or Media Alternative (Prerecorded)), 9.1.2.4 (Captions (Live)), and 9.1.2.5 (Audio Description (Prerecorded)) are not met.<\/strong><\/p>\n

Heading structure and headings are not always correct<\/h4>\n

On some pages, heading levels are not used in a logical sequence or heading levels are skipped. Empty headings are also present, and some page headings do not adequately describe the content or purpose of the page. As a result, the structure of the content and the relationships within it may not be correctly conveyed to assistive technologies, and users may have difficulty understanding the purpose of the page or the topic of the content that follows.<\/p>\n

Therefore, accessibility requirements 9.1.3.1 (Info and Relationships) and 9.2.4.6 (Headings and Labels) are not met.<\/strong><\/p>\n

Some information is conveyed by colour alone<\/h4>\n

On certain pages, information is communicated using colour without an alternative method of identification. As a result, users who cannot distinguish colours may not be able to perceive all available information.<\/p>\n

Therefore, accessibility requirement 9.1.4.1 (Use of Color) is not met.<\/strong><\/p>\n

Insufficient contrast<\/h4>\n

Some pages contain text with insufficient contrast against the background. This may make content difficult to read for users with visual impairments.<\/p>\n

Therefore, accessibility requirement 9.1.4.3 (Contrast (Minimum)) is not met.<\/strong><\/p>\n

Content does not always adapt properly when displayed on smaller screens or with customised text settings<\/h4>\n

On some pages, horizontal scrolling occurs on narrow screens or when content is enlarged. In addition, some text becomes truncated when text spacing is increased. As a result, users may have difficulty accessing or reading content when using magnification or customised text settings.<\/p>\n

Therefore, accessibility requirements 9.1.4.10 (Reflow) and 9.1.4.12 (Text Spacing) are not met.<\/strong><\/p>\n

Content displayed on hover cannot always be dismissed properly<\/h4>\n

Some user interface components appear when the mouse pointer hovers over an element and may obscure page content. Such content cannot always be dismissed without moving the pointer or changing focus.<\/p>\n

Therefore, accessibility requirement 9.1.4.13 (Content on Hover or Focus) is not met.<\/strong><\/p>\n

Links are missing descriptive text<\/h4>\n

Some pages contain links without text or another accessible name. As a result, users may not understand the purpose of the link.<\/p>\n

Therefore, accessibility requirement 9.2.4.4 (Link Purpose (In Context)) is not met.<\/strong><\/p>\n

Page titles do not always describe the page topic<\/h4>\n

On some subpages, the browser page title does not adequately describe the content or purpose of the page. As a result, users may find it difficult to distinguish between pages and understand their topic.<\/p>\n

Therefore, accessibility requirement 9.2.4.2 (Page Titled) is not met.<\/strong><\/p>\n

Form fields are missing labels or accessible names<\/h4>\n

Some search, date, and other form fields do not have a programmatically determinable name, label, or other accessible identifier. As a result, assistive technologies may not be able to correctly convey the purpose of the field to users.<\/p>\n

Therefore, accessibility requirements 9.3.3.2 (Labels or Instructions) and 9.4.1.2 (Name, Role, Value) are not met.<\/strong><\/p>\n

Embedded frames are missing titles<\/h4>\n

Some embedded frames (iframes) do not have descriptive titles that identify their content or purpose. As a result, screen reader users may not be able to determine the purpose of the frame.<\/p>\n

Therefore, accessibility requirement 9.4.1.2 (Name, Role, Value) is not met.<\/strong><\/p>\n

Some PDF documents are not fully accessible<\/h4>\n

Some PDF documents contain non-standard structural elements or do not include the tags required for accessibility. In addition, document titles may be missing from the metadata. As a result, the document structure, content, or purpose may not be correctly conveyed to assistive technologies.<\/p>\n

Therefore, accessibility requirements 10.1.3.1 (Info and Relationships) and 10.2.4.2 (Page Titled) are not met.<\/strong><\/p>\n\n <\/div>\n <\/accordion-content>\n <\/accordion-item>\n \n User guide<\/accordion-trigger>\n \n

\n

The homepage of the Riigikogu has been designed to comply with the accessibility guidelines of WCAG\u00a02.1 Level AA and the accessibility standard EN\u00a0301\u00a0549\u00a0V.3.2.1. This means that certain technical tools have been used to help users with visual, hearing, physical, speech, cognitive, language, learning and neurological disabilities to have access to the content of the homepage. This objective has also been kept in mind when designing the content. Access to information can be further improved by configuring your computer at browser and operating system level.<\/p>\n\n <\/div>\n <\/accordion-content>\n <\/accordion-item>\n \n Overview of main tools<\/accordion-trigger>\n \n

\n

Navigating by keyboard<\/h4>\n

It is possible to navigate the website by keyboard alone. To do this, use the\u00a0TAB key<\/strong>. Each press moves the focus to the next element. The currently active element is marked by a box surrounding it. To activate a link in focus, press the\u00a0\u201cEnter\u201d<\/strong>\u00a0key on the keyboard.<\/p>\n

Enlarging the content<\/h4>\n

To enlarge the content of the homepage, we first recommend to use the functionality built into the web browser.<\/p>\n

Web browsers<\/h4>\n

In all popular web browsers, it is possible to zoom in and out of the page by holding down the \u201cCtrl\u201d key (\u201cCmd\u201d key in OS X operating system) and at the same time pressing either \u201c+\u201d or \u201c\u2013\u201d. Another convenient option is to hold down the \u201cCtrl\u201d key and at the same time roll the mouse wheel. To restore the normal size, press \u201cCtrl\u201d and \u201c0\u201d keys simultaneously.<\/p>\n

Using the screen reader<\/h4>\n

Screen reader is a program for interpreting the content displayed on the screen and conveying it in other forms, e.g. as sounds or audio comments. It is mainly a tool for visually impaired persons.<\/p>\n

A selection of popular screen readers:<\/p>\n