Core & Trust · trust
Accessibility Statement
Star Budapest’s current accessibility approach, known limits and plans for reporting barriers once a secure contact channel exists.
The short version
What matters
- The intended target is WCAG 2.2 AA, not an unverified conformance claim.
- Keyboard focus, labels and reduced motion are built into the shared interface.
- Travel-access information remains route and venue specific.
01
What the site is designed to support
Star Budapest is designed around readable text, semantic headings, visible keyboard focus, labelled controls, a skip link, responsive layouts and a reduced-motion preference. The shared guide renderer exposes sources as links, keeps facts in a definition list, and uses text alongside visual brand devices.
The working target is WCAG 2.2 AA. That is a design and testing target, not a blanket declaration that every future page, photograph, third-party link or dynamic condition will conform without ongoing review.
Sources: wcag-22
02
How accessibility is checked
Accessibility work is part of the build process, not a final visual decoration. The interface is checked for semantic structure, names and labels, keyboard reachability, focus visibility, colour contrast, responsive reflow and reduced-motion behaviour as shared components and pages are added. Automated checks help catch repeatable defects, but they do not stand in for reviewing a real journey through the site.
The practical question is whether a reader can find a guide, understand its hierarchy, use the menu and search, follow a source, and recover from an error without relying on a mouse, a large viewport, colour alone or a particular timing. WCAG 2.2 provides the public reference point for those decisions.
Sources: wcag-22
03
Content and media responsibilities
A text-first guide still needs careful media. Meaningful images require useful alternative text; decorative brand devices should stay out of the accessibility tree; and a caption should add context rather than repeat a filename. As photography, maps and interactive components are introduced, each needs its own accessible fallback or explanation before it can be considered complete.
External content is a limit. A linked operator page, map provider, ticket seller or video player is controlled by another organisation. Star Budapest can identify the destination and avoid presenting it as its own interface, but cannot claim that a third-party page meets this site’s target. Where possible, the guide keeps essential practical information in readable text alongside the link.
Sources: wcag-22, bkk-tickets
04
What we will not claim
No page should claim a level of conformance that has not been tested across the full page and its relevant variations. The working WCAG 2.2 AA target guides the design, but a completed public conformance claim needs a completed audit, known-issue record and ongoing maintenance process.
Likewise, an accessible website does not make Budapest itself universally accessible. The separate travel guides use BKK and venue information to explain route-specific conditions, then direct readers to the controlling operator for a live check.
Sources: wcag-22, bkk-accessibility
05
Known limits and honest language
A travel guide can describe access without speaking for a venue or a transit network. Conditions change: a lift may be out of service, a low-floor vehicle may vary by departure, and a historic building may have limits that a general description cannot resolve. Star Budapest therefore links readers to the controlling operator and dates volatile access facts.
For city movement, BKK provides route-level accessibility information and describes the limits of its network, including which metro stations and vehicle types are step-free. Use that live information for a trip plan rather than treating an editorial summary as an access guarantee.
Sources: bkk-accessibility, bkk-go
06
Reporting a barrier
If an interface barrier prevents you from using this site, the ideal report names the page, device or assistive technology, the action you attempted, and what happened. That lets the team reproduce the issue without asking for unnecessary personal information.
The launch build does not yet expose a secure public contact channel. When it does, this statement will identify the channel and response path. In the meantime, the design system continues to be tested as pages, images and interactive features are added.
Sources: wcag-22
Evidence, not footnotes in the dark