DECLARATION ON DIGITAL ACCESSIBILITY
Public body / scope of application
Tegel Projekt GmbH
This declaration on digital accessibility applies to the website https://urbantechrepublic.de/.
We endeavor to make our website barrier-free. This is based on the law on barrier-free information and communication technology in Berlin (BIKTG Bln) and the Barrier-free Information Technology Ordinance (BITV 2.0).
Preparation of this accessibility statement
This declaration was prepared or revised on October 31, 2025.
The statements in this declaration were last reviewed on October 31, 2025.
The review of digital accessibility was carried out by the monitoring body for digital
accessibility of the public authorities of the State of Berlin.
(Testing body: The Governing Mayor of Berlin – Senate Chancellery,
Competence Center for Digital Accessibility)
How barrier-free is the offer?
This website is partially accessible. The requirements of BITV 2.0 are only partially fulfilled.
Which areas are not barrier-free?
The areas listed below are not barrier-free for the following reasons:
Incompatibility with BITV 2.0
1. lack of sign language
a) Description: Content in German Sign Language (DGS) is currently not available at .
b) Measures: Provision of central information and an introduction to German sign language.
c) Timetable: January 2027
d) Barrier-free alternative: Currently no alternative available.
(Additional criteria: German sign language)
2. easy language
a) Description: Texts on navigation, content and declaration on accessibility are not available in plain language.
b) Measures: Creation of a summary of the main content and navigation in easy language.
c) Timetable: July 2026
d) Barrier-free alternative: None currently available.
(Additional criteria: Easy language)
3. lack of semantic structure and heading logic
a) Description: Parts of the website do not have a consistent heading structure (missing <h1>, illogical hierarchies, incorrectly labeled content areas).
b) Measures: Revision of the HTML structure and adaptation of the heading hierarchy.
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.1.3.1 Info and relationships; 9.1.3.2 Meaningful sequence; 9.2.4.1 Skipping blocks; 9.2.4.6 Headings and labels)
4. insufficient color contrast
a) Description: Texts and control elements sometimes have too little contrast (e.g. buttons, links and footer texts).
b) Measures: Revision of the color design to maintain a contrast ratio of at least 4.5:1.
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.1.4.1 Use of color; 9.1.4.3 Contrast (minimum); 9.1.4.11 Non-text contrast)
5. missing alternative texts and insufficient link identification
a) Description: Some graphics and links do not have alternative texts or clear labels.
b) Measures: Addition of missing alternative texts and clear link identifiers.
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.1.1.1 Non-text content; 9.2.4.4 Link purpose (in context); 9.2.5.3 Label in name; 9.4.1.2 Name, role, value)
6. problems with keyboard operation and focus display
a) Description: Some interactive elements are not fully accessible via the keyboard or the visible focus is missing.
b) Measures: Ensure full keyboard operation and visible focus frame (contrast ≥ 3:1).
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.2.1.1 Keyboard; 9.2.4.7 Focus visible)
7. missing or incorrect page titles
a) Description: Some pages have unclear or ambiguous page titles.
b) Measures: Assign precise and meaningful page titles that reflect the content .
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.2.4.2 Page with title)
8. automatically playing or moving content
a) Description: Some content (e.g. videos or animations) start automatically or move without user intervention.
b) Measures: Deactivation of automatic playback and provision of control options (pause/stop).
c) Timetable: July 2026
d) Accessible alternative: Static alternative content is added.
(EN 301 549: 9.2.2.2 Pause, stop, hide)
9. forms and error messages
a) Description: Forms do not contain clear labels or error messages are not meaningful.
b) Measures: Improvement of form fields, labels and error messages.
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.1.3.5 Determine input purpose; 9.3.3.1 Error identification; 9.3.3.3 Suggestion in case of error; 9.4.1.2 Name, role, value)
10. missing menu area descriptions
a) Description: Some navigation areas do not have clear descriptions (“Main”, “Footer” etc.).
b) Measures: Addition of clear descriptions and semantic markings of the navigation areas.
c) Timetable: July 2026
d) Barrier-free alternative: None.
(EN 301 549: 9.1.3.1 Info and relationships; 9.2.4.1 Skip blocks)
Disproportionate burden
Currently no areas for which a disproportionate burden is claimed.
No use case
No exceptions pursuant to Section 4 (4) BIKTG Bln have been asserted.
Feedback mechanism / report barriers
Would you like to report information on the implementation of accessibility or existing
barriers? You cannot sufficiently perceive, operate or understand something on our website or mobile application
Contact the contact person at the public body:
Tegel Projekt GmbH
E-mail: redaktion@berlintxl.de
Phone: +49 (0)30 90223 – 0
URL: https://urbantechrepublic.de/barriere-melden/
Contact the State Commissioner for Digital Accessibility (enforcement procedure)
If your contact with the public body was unsuccessful, you have not received a response within one month or the response was inadequate, you can contact the State Commissioner for Digital Accessibility and seek enforcement proceedings. Please always contact the public body concerned first.
Contact form:
https://www.berlin.de/lb/digitale-barrierefreiheit/includes/formular.1326107.php
Further information:
https://www.berlin.de/lb/digitale-barrierefreiheit/aufgaben/durchsetzungsverfahren/durchsetzungsverfahren-1305830.php