Transport and Logistics Companies. 1-Year Compliance Period.

Are your online ticketing and customer portal KVKK and WCAG 2.2 compliant?

For airline, bus, maritime and cargo logistics companies, cookie consent management and the accessibility obligation meet within the same legal framework. Manage your online ticketing, seat selection, check-in and customer portal interfaces from one platform.

Start a free site scan Request a demo The obligation is in force

Legal basis: Presidential Circular 2025/10 (Official Gazette 32933), Law No. 5378 on Persons with Disabilities, Road Transport Regulation, SHGM airline accessibility directives, Law No. 6698 KVKK. Standard: WCAG 2.2 Level A.

0
Share of citizens with disabilities in Türkiye's population (TÜİK 2023)
0
WCAG 2.2 A success criteria (Ministry checklist)
0
Line of code for cookie + accessibility widget integration
0
Accessibility settings. 11 ready-made profiles (senior, visual, dyslexia...)
Sector-specific problems

4 critical gaps in the digital interfaces of transport companies.

Online ticketing, seat selection, check-in and the customer portal; each carries risk under both KVKK and WCAG 2.2 A.

Cookies, KVKK

Online ticket booking cannot run without cookie consent.

On airline and bus ticketing sites, analytics, remarketing and session cookies are triggered when the page loads. Under KVKK Article 5 and GDPR Article 6, these cookies are not legal without obtaining explicit consent from each visitor. Passing the passenger's IP to business partners poses an additional risk.

  • Marketing cookies run during the ticket search step are a KVKK risk
  • Without Google Consent Mode v2, GA4 and Google Ads data sit in a legal gap
  • The time-stamped consent log keeps a record for the KVKK burden of proof
Run a free cookie scan
Accessibility. WCAG 2.2 A.

Your passenger with a disability must be able to buy their ticket independently.

Date pickers, seat maps, payment forms and check-in modules are mostly custom JavaScript components. When keyboard navigation, ARIA roles and screen reader announcements are missing, a visually impaired passenger or one with motor difficulties cannot buy their ticket. This is a legal violation under Law No. 5378 and Circular 2025/10.

  • The seat map cannot be navigated with the keyboard. WCAG 4.1.2 violation.
  • Occupied/available seats are coded by color only. WCAG 1.4.1 violation.
  • Mobile WebView check-in modules fall under WCAG 2.2 A
See your WCAG 2.2 scan score
Honest positioning

There is no such thing as "we added a script, we became accessible."

Overlay tools inject a single line of JS and claim instant compliance; the majority of these violations are not accepted as legally valid. We chose a real path.

Overlay approach

A single line of script, a big promise.

  • Does not fix the source code; hides the problem rather than solving it
  • Does not skip critical violations like WCAG 4.1.2, 1.4.1
  • Does not produce an auditable report or EAA statement
  • Cookie management is a separate tool, a separate invoice

"We added a widget, the site became accessible." It does not really work that way.

cerez.io approach

Helper widget + real scanner + documentation.

  • Actually measures WCAG 2.2 A/AA rules
  • 0-100 Accessibility Health + prioritized violation report
  • Document your obligation with the EAA statement generator
  • Cookies + accessibility, one panel, one invoice

We say it plainly: full compliance requires source code fixes and manual review. We shorten the path and produce the evidence.

Solution map

One feature for every pain point.

For the four critical risks of the transport sector cerez.io's concrete counterpart.

Cookie Management

Cookie consent flow during the ticket search and payment step.

Performs a BFS scan of the site with a database of 217 defined cookies; third-party scripts (Google Analytics, remarketing pixels, live chat) are blocked automatically until consent is obtained. Google Consent Mode v2 integration comes as standard.

  • Automatic scanning + categorization + script blocking before consent
  • Google Consent Mode v2
  • Time-stamped consent log. Ready for the KVKK burden of proof.
Try a cookie scan for free
Accessibility Widget

Finding the barriers in seat selection, date pickers and check-in forms.

The Shadow DOM widget gives the visitor extra options with 30 settings: reading guide, large cursor, contrast mode, senior profile and mobility impairment profile. A real WCAG 2.2 scanner runs in the background: 0-100 Accessibility Health, severity-rated violation list and EAA statement generator.

  • 30 settings. Senior, mobility impairment, visual and dyslexia profiles.
  • Real scanner: 0-100 Accessibility Health + prioritized violations
  • EAA statement generator. Documents your legal obligation.
Start a free WCAG scan
Real scan, real output

Not guesswork, measurable compliance.

The WCAG 2.2 scanner analyzes the ticket search, seat selection and check-in steps page by page. The report below is a sample output.

0/ 100 Accessibility Health

WCAG 2.2 A. 18 pages scanned.

Last scan: today 10:31

+11 points over last month
Priority violations. Ticket flow.14 findings, sample
Critical Seat map without keyboardCannot be navigated with Tab + Enter; the screen reader cannot enter. WCAG 4.1.2. Guide
Critical Date picker missing ARIAThe selected date is not announced to the screen reader. WCAG 4.1.3. AI suggestion
Serious Seat status color-onlyOnly color is used to distinguish occupied/available/selected. WCAG 1.4.1. Fix in source
Serious Payment form unlabeledCard number and CVV fields have no label/aria-label. WCAG 3.3.2. Guide
Moderate Low text contrastOrange "Cheapest" badge 2.8:1. 4.5:1 required for AA. WCAG 1.4.3. Fix in source

Automatic scanning catches a significant portion of violations; full WCAG compliance requires source code fixes and manual review. "Auto-fix" offers a temporary solution at the SDK level only for certain violations.

Transport segments

Integration suited to your transport type.

Air, road and sea travel have different accessibility priorities; the Shadow DOM architecture does not break the GDS/PSS interface.

Airline

High volume, multiple languages, mobile check-in. GDS (Amadeus, Sabre, Travelport) integration is the core system. WCHR/WCHS assistance notification is mandatory.

Bus Companies

Intercity booking, online seat selection. High share of elderly passengers. Keyboard navigability of the seat map is critical.

Ferry and Maritime

Seasonal volume, vehicle and passenger booking combined. Missing alt text is common on image-heavy pages (ship plan, gallery).

Cargo and Logistics

B2B customer portal, sender/recipient forms, tracking page. Form labels, status notifications and keyboard navigation are critical violation areas.

Risk calculation

What does non-compliance cost a carrier?

The risk is not only an administrative fine; SHGM audits, passenger complaints and reputational damage are included too.

Sanctions and Audits

The real risk on the web side

  • The Law 5378 tariff targets physical accessibility
  • No web fine tariff has been set yet
  • Additional Ministry and SHGM audits

Reputational Damage

Viral social media risk

  • Complaints from passengers with disabilities spread quickly
  • Blacklist risk on travel blogs
  • Accessibility criterion in public tenders

Opportunity Size

Accessibility = new passengers

  • 12 percent of Türkiye's population has a disability
  • NPS increase in the elderly passenger segment
  • In the EU tourism market, WCAG is a prerequisite

An accessible ticketing site provides both legal and commercial advantages.

Frequently asked questions

Frequently asked questions for transport companies

What is a practical solution for the interactive seat map component?
Offering a keyboard-navigable table or list alternative next to the seat map addresses a WCAG 1.3.1 violation. cerez.io generates a recommendation for a compliant component; your development team applies it to the source code. During this process, the widget offers temporary assistive tools to elderly and visually impaired passengers.
Our GDS/PSS system is Amadeus or Sabre. What should we do?
The responsibility lies with the transport company. Request WCAG 2.2 A compliance from your GDS provider. cerez.io the widget offers assistive tools to passengers with disabilities; the violation report is used as a vendor brief. Documenting that the GDS module cannot be modified can be a mitigating factor in SHGM audits.
Is the mobile app also within scope?
Platform criteria apply to native iOS/Android apps. WebView modules embedded in the app (ticket search, seat selection, payment) fall within WCAG 2.2 A scope, and cerez.io its scanner can target the URLs of these modules.
Is urban transport (taxi, minibus app) within scope?
For the 1-year group, Circular 2025/10 primarily covers intercity bus, airline, maritime and rail companies. If a web or mobile app exists for the urban segment, scope can be assessed via that platform; for a definitive classification, we recommend consulting a legal advisor.
What do you recommend for the PNR and ticket PDF?
Generating tagged PDFs is essential. Use the tagged output option of your PDF library (for example DOMPdf, wkhtmltopdf). Alternatively, you can provide an HTML ticket page; this is more reliable for screen reader access.
Is IAB TCF 2.3 included in every tier?
No. Google Consent Mode v2 is supported. The IAB TCF framework is in development (alpha): cerez.io is not a registered or certified IAB Europe CMP and is not yet suitable for ad networks that require TCF. No timeline has been set for IAB registration.

Can your passengers with disabilities buy their ticket independently?

Find out your ticketing flow's WCAG 2.2 A compliance with a free scan, and start KVKK cookie management the same day. The obligation is in force.

Start a free scan Request a transport company demo
  • 10-language support. For international passengers.
  • Local hosting. Data stays in the country.
  • TL invoicing only