EU project
An accessible, multilingual travel-information web app for DANOVA NEXT
A multilingual web application that brings accessibility information from airports, ports, and public-transport partners into one structured, inclusive experience for travellers with disabilities.
- Client
- Danova Next
- Industry
- Airports, ports and public transport
- What we built
- Accessible web app + standardized partner data + inclusive testing
- Status
- EU project
The challenge
What was getting in the way
Travellers with disabilities need practical accessibility information before setting off. Transport partners across the Danube Region held that information on separate websites, in different formats and languages.
Transport partners across the Danube Region need to publish practical accessibility information for airports, ports, and public transport. Travellers with disabilities need that information before a journey, in a format that works across devices, languages, and assistive technologies.
Accessibility information was distributed across partner websites, content structures, and languages. Travellers had to assemble context from separate sources, while partners lacked one consistent way to publish comparable information and keep it current across the regional application.
- Each partner prepares and owns the accessibility information for its locations and services.
- Similar details are published through different website structures, labels, languages, and media formats.
- Travellers move between sources to understand facilities, assistance procedures, and transport options before visiting.
- Content changes need to be reflected in a shared regional application without creating another manual publishing process.
Approach
How the system works
We built a multilingual platform that brings partner accessibility information into one place. Travellers can explore transport locations, while partners publish through a shared content structure.
- 01
Accessible partner template
A repeatable page structure gives every partner a clear way to publish the required accessibility information using stable fields and accessible components.
- 02
Standardized data layer
Partner APIs send the agreed content model to a central database, where records can be validated and kept aligned with their source.
- 03
Danova Next public application
A partner directory and detailed transport pages present the centralized content in an accessible, multilingual, responsive experience.
Rules handle
- Validate partner responses against the agreed field and content structure.
- Associate every update with the correct partner, location, transport mode, and language.
- Store accepted content in the central data model and expose its latest approved state.
- Render consistent partner-list and partner-detail views from the same structured records.
- Keep text, video, sign-language, and language variants attached to the correct content item.
- Surface failed imports or structural changes for review instead of silently publishing incomplete information.
People decide
- Partners approve their accessibility content and provide the required language and media alternatives.
- Accessibility specialists and testers with disabilities validate the interface with assistive technologies and real usage scenarios.
- The delivery team reviews schema mismatches, structural changes, and failed updates before altering the public experience.
- Project owners decide when new partners and content types are ready to enter the shared platform.
No generative AI needed
Generative AI is not required to decide, rewrite, or publish accessibility information in the core application flow.
Travel information, made clear
Choose a place. Find the details that matter.
Danova Next brings partner information into one shared experience, from airports and ports to public transport.Illustrative exploration — information varies by partner.
The website
The published web experience
Explore selected screens from the project. The complete site opens separately for current content and full interaction.
Start from one accessible entry point
The homepage introduces the regional application and gives travellers a direct route to accessibility information from participating transport partners.
Captured from the published website.Stack
Built with
Every tool the system connects, and the job it does.
Partner websites
The source pages and content owned by participating airports, ports, and public-transport organisations.
Standardized partner APIs
A shared response structure that lets different partner systems send comparable accessibility data.
Central data layer
Partner, location, language, transport, accessibility, and media records used by the public application.
Danova Next application
The public directory and detailed information experience used by travellers.
Accessibility validation
Assistive-technology checks and testing with people with visual, hearing, and mobility disabilities.
Limits
Limits of this case
- The freshness and completeness of public information depend on each partner maintaining its source content and API response.
- A standardized response contract reduces inconsistency, but partner-side structural changes still require coordination and validation.
- Accessibility is an ongoing operating responsibility; new content, browsers, devices, and partner additions need continued review.
Possible next phase
Expand the partner network through the same data contract, then add shared monitoring for update health, content freshness, and recurring accessibility checks.
Next case study
