Digital accessibility statement
Accessibility statement in Easy Language – (in preparation)
Accessibility statement in German Sign Language (DGS) – (in preparation)
Public body / scope
Berliner Hafen- und Lagerhausgesellschaft mbH (BEHALA)
We strive to make our website accessible. This digital accessibility statement is required by Berlin’s Act on Accessible Information and Communication Technology (BIKTG Bln). The technical requirements are set out in BITV 2.0.
This statement applies to: https://www.behala.de
Preparation of this accessibility statement
This statement was prepared on 12 November 2025.
Digital accessibility was assessed through an internal self-assessment and an evaluation of an external audit report.
How accessible is this website?
This website is currently not fully accessible. Various barriers remain in the areas of perceivability, operability, understandability and robustness.
A complete website relaunch is planned. All existing barriers will be fully addressed in accordance with BITV 2.0 as part of the redevelopment. Publication of the new website is scheduled for March 2026.
Which areas may not be accessible?
A – Critical barriers (WCAG Level A)
#6 Clickable links are not clearly highlighted
a) Some clickable links are not sufficiently recognisable.
b) New, clear link styles will be implemented in the relaunch.
c) Adjustments will be made during the relaunch.
d) Users currently have difficulty identifying links.
#7 Unclear link text (“here”)
a) Some links do not have a clear meaning in context.
b) All link text will be editorially revised during the relaunch.
c) Implementation during the relaunch.
d) The purpose of individual links may be unclear.
#8 / #39 Focus leaves the open hamburger menu
a) Keyboard focus can move outside the open menu.
b) Navigation will be completely redeveloped.
c) Implementation during the relaunch.
d) Keyboard operation is restricted.
#9 No keyboard focus on the cookie banner
a) The banner does not receive automatic focus when the page loads.
b) It will be replaced with an accessible version during the relaunch.
c) Implementation during the relaunch.
d) Operation is difficult.
#12 Image cannot be clicked with a mouse
a) Linked images do not respond correctly to clicks.
b) Technical corrections will be made during the relaunch.
c) Implementation during the relaunch.
d) Mouse use is restricted.
#13 Missing focus indicator
a) Visible focus is missing in some places.
b) A new focus style will be introduced.
c) Implementation during the relaunch.
d) Keyboard navigation is impaired.
#15 Unsuitable alternative text / duplicate link targets
a) Some image links have unsuitable alternative text; duplicate links exist.
b) All alternative text will undergo a complete editorial review.
c) Implementation during the relaunch.
d) Screen readers receive unclear information.
#17 Images without alternative text
a) Some images have no alternative text.
b) Alternative text will be added to all images during the relaunch.
c) Implementation during the relaunch.
d) Screen reader users miss important content.
#41 Illogical tab order
a) Tab focus moves unpredictably.
b) All interactive elements will be restructured.
c) Implementation during the relaunch.
d) Keyboard use is difficult.
#43 Navigation elements are not grouped
a) ARIA grouping is missing or insufficient.
b) Navigation markup will be completely revised.
c) Implementation during the relaunch.
d) Screen reader use is restricted.
#47 Content is not within a landmark region
a) Content is not correctly embedded in main/region landmarks.
b) A new semantic structure will be created.
c) Implementation during the relaunch.
d) Finding one’s way through the content is difficult.
#48–52 Incorrect or duplicate landmarks
a) Duplicate or contradictory ARIA landmarks are present.
b) These will be cleaned up and restructured during the relaunch.
c) Implementation during the relaunch.
d) Screen reader users encounter navigation conflicts.
#55 Links without perceivable text
a) Some links consist only of icons or have no text.
b) ARIA labels or visible text will be added.
c) Implementation during the relaunch.
d) Screen readers cannot identify their purpose.
#56 Unclear page title
a) The document title is ambiguous or not descriptive.
b) A consistent approach to titles will be introduced.
c) Implementation during the relaunch.
d) Orientation is difficult.
#61 Non-functional skip link
a) The skip link does not lead to the actual main content area.
b) Anchor targets will be corrected.
c) Implementation during the relaunch.
d) Keyboard users cannot skip directly to the content.
B – Significant barriers (WCAG Level AA)
#3–5 Missing subtitles / audio description
a) Videos have no accessible alternatives.
b) Subtitles and full-text alternatives will be provided.
c) Implementation during the relaunch.
d) Content is inaccessible to many users.
#16 Elements disappear at certain screen sizes
a) The layout breaks at certain viewport sizes.
b) The responsive structure will be completely redesigned.
c) Implementation during the relaunch.
d) Content is restricted on mobile devices.
#20 Submenus cannot be closed correctly
a) Subnavigation does not respond reliably.
b) New accessible menu behaviour will be introduced.
c) Implementation during the relaunch.
d) Operation is difficult.
#22 Insufficient colour contrast (text)
a) Some text contrasts do not meet AA requirements.
b) A new colour palette will be implemented.
c) Implementation during the relaunch.
d) Readability is restricted.
#25 “We are the port” is not actual text
a) The text is a graphic with no alternative.
b) It will be replaced with actual HTML text.
c) Implementation during the relaunch.
d) Screen readers cannot access the content.
#26 Text overlaps when display settings change
a) The layout does not respond to increased spacing.
b) Responsive CSS will be rebuilt.
c) Implementation during the relaunch.
d) The display may become unreadable.
#27 Overlap when text spacing changes
a) User-defined line heights cause overlaps.
b) All typographic units will be adjusted.
c) Implementation during the relaunch.
d) Content is difficult to read.
#31 Focus is not visible in the footer
a) The focus indicator is obscured.
b) The footer structure will be redesigned.
c) Implementation during the relaunch.
d) Keyboard navigation is restricted.
#32 Focus outline has insufficient contrast
a) Focus highlighting does not meet contrast requirements.
b) A new focus style will be introduced.
c) Implementation during the relaunch.
d) Users cannot identify their current position.
#33 Search button hover state has insufficient contrast
a) The hover state is visually too weak.
b) New states will be introduced in the design system.
c) Implementation during the relaunch.
d) Mouse users have difficulty recognising interactions.
#34 Inconsistent heading structure
a) The heading hierarchy is incorrectly nested in some places.
b) The semantic structure will be completely revised.
c) Implementation during the relaunch.
d) Screen reader users lose context.
#38 Duplicate or unclear headings
a) Some titles are repeated and ambiguous.
b) Editorial revisions will be made.
c) Implementation during the relaunch.
d) Content appears unstructured.
#40 No separate controls for submenus
a) Submenus cannot be opened or closed independently.
b) Clear control buttons will be implemented.
c) Implementation during the relaunch.
d) Operation is difficult.
#46 Dark mode / font size is not taken into account
a) Browser and system settings are ignored.
b) prefers-color-scheme & prefers-reduced-motion will be introduced.
c) Implementation during the relaunch.
d) User preferences are not respected.
#63–64 Incorrect/incomplete accessibility statement
a) The previous statement did not meet the requirements.
b) This new statement provides the correction.
c) Updated in November 2025.
d) Transparency was previously restricted.
C – Additional barriers
#10 English alternative text
a) Some alternative text is available only in English.
b) Editorial adjustments will be made during the relaunch.
c) Implementation during the relaunch.
d) Understandability is restricted.
#11 Non-standard formatting ( )
a) The HTML contains outdated or unsuitable formatting.
b) The source code will be cleaned up.
c) Implementation during the relaunch.