Following my initial visual research, I wanted to understand which airport accessibility initiatives and related design services already exist before developing a visual identity of my own. My working design ambition is to connect journey information, relevant sensory and environmental options, and traveller-controlled assistance. It would be difficult to justify this as a design opportunity without first examining organisations that already communicate some or all of these functions.
I therefore looked beyond logos and colour palettes to the services behind the identities: what each programme actually offers, where it operates, how a traveller discovers or activates it, and what remains dependent on airport staff or operations. The examples below are a deliberately wide-ranging precedent scan, not a complete global census or an independent usability study. Most evidence comes from official airport, provider and regulatory websites; those sources establish what organisations publicly describe, but not necessarily the quality of each passenger's experience.
Hidden Disabilities Sunflower is one of the clearest examples of a cross-organisational accessibility identity. A recognisable sunflower symbol on a lanyard or other item allows a person to voluntarily signal that they may need additional time, patience or assistance, without having to disclose a diagnosis to everyone they encounter. It originated in an airport setting and is now recognised in many other places. The visual identity has a very specific communication task: signalling a potential need to a person who understands the symbol. Official Sunflower programme and participating locations; London Gatwick's explanation of the lanyard.
I find the simplicity of that identity instructive, but it is not the same as an information or journey-support system. Gatwick explicitly states that staff do not know a person's particular requirements from the lanyard alone and that it does not provide automatic fast-track or queue-jumping. This is a useful distinction for my design: a recognised sign can make a need visible, but it cannot by itself explain a gate change, supply directions, guarantee assistance or convey which sensory options are currently accessible. I also want to preserve a person's right not to wear an identifying symbol.
Dublin Airport's Important Flyer identifier is particularly useful to compare with Sunflower. Dublin describes a lanyard or wristband for autistic passengers or passengers with sensory processing differences, with an application route and a distinct procedure for accessing complimentary Fast Track. The airport also participates in Sunflower, but clarifies that Sunflower itself does not provide the same Fast Track entitlement. Dublin Airport — Autism and non-visible disabilities; Dublin Airport — Accessibility FAQs.
This illustrates how two superficially similar identifiers can communicate different kinds of access and impose different conditions. Dublin's Important Flyer application page describes documentation requirements; that raises design questions about administrative burden, eligibility and whether support can be accessed without a label or advance preparation. My project should not treat identification, service entitlement and an actual request for help as interchangeable actions.
GoodMaps is one of the strongest challenges to any claim that cross-touchpoint, accessible airport navigation does not already exist. Its platform offers indoor mapping and routing through websites, kiosks, embedded products and a dedicated app. The service describes step-by-step directions, multiple presentation modes, accessible routes and centrally managed information that can appear across different surfaces. It names airports as an established sector, including Portland, Louisville and Bradley among its examples. GoodMaps platform; GoodMaps airport deployments.
I am especially interested in GoodMaps' approach to a shared source of wayfinding information across several interfaces. This is directly relevant to my ambition to connect airport touchpoints. However, accessible routing should not automatically be equated with confirmed airline operations, moment-by-moment sensory conditions or the delivery of staff assistance. The provider's own descriptions are evidence of its offered features, not independent proof of outcomes for autistic adults. To distinguish my idea, I would need a precise interaction or communication problem that is not already handled adequately by GoodMaps or a similar platform.
The Heathrow app is another important direct precedent. Heathrow describes personalised flight tracking, check-in and gate information, security waiting times, boarding updates and door-to-gate guidance. This matters because an app that links a passenger's trip to live airport information is already a functioning kind of connected journey interface; it would be inaccurate to describe such connectivity as new in itself. Heathrow — Mobile apps.
From a graphic-design perspective, the more useful question is how changing operational information is explained and how easily a traveller can move between immediate instructions, a wider overview, environmental options and chosen assistance. Heathrow separately describes assistance information, accessible app functions and dedicated airport support. Whether users experience these elements as a sufficiently coherent and accessible whole would require direct evaluation rather than assumptions based on separate webpages. Heathrow — Help in the terminal.
MagnusCards, developed by Magnusmode, is particularly relevant because it explicitly supports people who benefit from staged instructions. Toronto Pearson provides airport-specific digital card decks for processes such as check-in and boarding, and describes the app as a free resource for neurodiverse travellers. Its official page lists 26 Pearson Card Decks. Toronto Pearson — MagnusCards; Magnusmode — Product and partners.