Accessibility Statement
Last updated: June 2026
Göbeklitepe Community is committed to making our website and mobile apps usable by as many people as possible, including people with disabilities. This statement describes our current level of conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which is the international benchmark for digital accessibility.
Our compliance is voluntary, but we treat it as a commitment rather than a suggestion.
1. Current conformance status
Partial conformance
gobeklitepeai.com — aiming for WCAG 2.1 AA. Most pages meet or exceed AA; some marketplace and community pages have known shortcomings listed below.
Partial conformance
Göbeklitepe mobile app — aiming for WCAG 2.1 AA via native accessibility APIs. The offline map feature has known barriers (see s.5).
Planned
Third-party external audit — we plan an independent accessibility audit in H2 2026 and will publish the findings and remediation plan.
2. What works well
- Keyboard navigation: all core flows (browse the site, book a tour, sign in, contact form) are fully keyboard-accessible with visible focus states.
- Semantic HTML: pages use headings (
<h1>…<h3>) in document order and ARIA labels on interactive non-text controls.
- Colour contrast: body text (dark text on cream / white) and the primary palette meet WCAG AA; accent colours are reserved for large headings and non-text UI accents (which meet AA for those uses). Colour-only signals are reinforced with icons + labels.
- Text scaling: pages respond to browser text-zoom up to 200% without horizontal scroll or content loss.
- Forms: every input has a programmatically-linked label; errors are announced via
aria-live regions; required fields are marked.
- Images: content images include
alt text; decorative images use alt="".
- Language & locale: the site is published in English. Page
<html lang="en"> is set correctly.
- Mobile touch targets: interactive elements follow platform guidance (44×44 pt minimum) in the mobile app.
- Screen readers: the mobile app has been tested with VoiceOver and TalkBack on common flows (onboarding, map, check-in, booking).
3. Known issues we're actively fixing
| Area | Issue | Planned fix |
|---|
| Site map (interactive) |
The map canvas is not directly screen-reader accessible. We provide a text alternative (site list + directions) but the map itself is not fully announced. |
Add per-location text equivalents and a skip link to "view all locations as a list". H2 2026. |
| Marketplace provider cards |
Star ratings rendered as Unicode characters — screen readers announce them character by character. |
Add aria-label="4.8 out of 5 stars" fallback. H2 2026. |
| Community Feed |
Infinite scroll — reliance on intersection observer may confuse some assistive tech. No "load more" button. |
Add a visible "Load more" button with aria-live. H2 2026. |
| Photo galleries |
Lightbox gallery focus trap works, but the escape-key hint isn't announced. |
Add aria-label="Press Escape to close". H2 2026. |
| Video content |
Some embedded site videos don't have captions. |
Require captions as a condition for publishing new videos from Q3 2026. Legacy content will stay until the uploader adds captions. |
4. Mobile app accessibility
The Göbeklitepe mobile app is built with Flutter. We use the Flutter Semantics widget tree, which bridges to native iOS UIAccessibility and Android accessibility services:
- Screen readers read all buttons, list items, headings, and form fields with meaningful labels.
- Dynamic Type / font scaling is supported on text-based screens. The map and navigation UI use a fixed type size because location coordinates must stay readable at arm's length.
- Reduce Motion is honoured where we use animations (e.g. card transitions).
- High contrast mode is respected.
5. Known mobile app issues
- Offline map: pinch-to-zoom gestures are not equivalent to keyboard zoom. We expose a two-button zoom control visually but it is hidden from screen readers. Workaround: use your device's system Zoom accessibility feature.
- Passive compass: the analogue compass visual isn't announced numerically. Workaround: the direction is also shown as a cardinal letter (N, NE, E…) which screen readers announce.
- Emergency contact setup: the "swipe to remove" gesture in the contact list is not discoverable for screen-reader users. Planned: add a visible delete button when a screen reader is active.
6. Need help using Göbeklitepe?
If you can't complete something because of an accessibility barrier, we want to help you directly while we work on the fix:
- Email [email protected] — we aim to reply within 2 working days.
- Describe the page or screen and what you were trying to do.
- If it's time-sensitive (e.g. finalising a booking), we'll complete the action for you manually by email.
7. Report a new accessibility issue
Please send new barriers to [email protected] with:
- The URL or app screen
- The assistive tech you use (e.g. VoiceOver, TalkBack, NVDA, keyboard only)
- What you expected to happen vs what did happen
We triage every report. Fixes for critical barriers (anything that blocks you from completing a task) are prioritised in our next release.
8. Enforcement
If you are not satisfied with our response, you can contact your local data protection or equality authority, which provides free guidance on disability discrimination and digital accessibility rights.
9. Technical specification
Göbeklitepe Community is built using HTML5, CSS, JavaScript (vanilla — no heavy framework on the marketing site), Flutter/Dart (mobile app), and Django (back-end). These pages are tested against WCAG 2.1 AA criteria using a combination of:
- Manual keyboard-only testing
- axe DevTools browser extension
- Lighthouse Accessibility audit
- NVDA (Windows), VoiceOver (macOS, iOS) and TalkBack (Android) screen readers
- Colour Contrast Analyser for custom palette decisions
10. Commitment to improve
We prepared this statement in June 2026. We review it every 6 months and update it when new features ship. The next scheduled review is December 2026.
Göbeklitepe Community — gobeklitepeai.com. Questions: [email protected].