Accessibility Statement

ENA Innovation aims to build EnaFeedback so that everyone, including people with disabilities, can use it. This statement describes the product's accessibility target, its current status, the measures taken and the known limitations.

1. Nature of this statementCopy Anchor Link

This document is a supplier accessibility statement prepared for use in audit, compliance and tender files. It is not a third-party conformance certificate, a VPAT/ACR or a laboratory report. "Met" is used only for items closed by internal review. Full WCAG 2.2 AA conformance is a target; it is not awarded by this statement.

2. ScopeCopy Anchor Link

This statement covers the whole EnaFeedback product.

Visitor surface (patients, companions, guests and field staff):

• visitor home screen, feedback, hygiene ratings, surveys, content pages and ticket tracking
• QR scanning, location and staff screens
• visitor interface in Turkish, English, German and Arabic (including page language and text direction)

Admin panel (organization staff; Turkish and English):

• buildings and locations, templates, feedback and hygiene operations, team inbox
• survey, page, staff and cleaning reports and records
• user management, resolution teams, system settings and preferences

Out of scope or limited:

• Accessibility of content the organization enters itself: image alternative text, video caption files and free text
• Third-party components: the identity service's sign-in pages, the browser's camera permission prompt, the operating system and assistive technologies
• Cover photo and brand color combinations chosen by the organization. Primary color contrast is checked; the choice of cover image is the organization's responsibility.
• The canvas of the content and poster template editor. Keyboard drawing is not claimed.
• Report charts. Charts have an accessible name; keyboard exploration of charts is not claimed. Most reports also present the same data in tables.

This statement does not cover the www.enafeedback.com marketing website.

3. Conformance statusCopy Anchor Link

Status: partial conformance. The visitor and admin surfaces were designed to WCAG 2.2 AA and reviewed again across the product in an internal code review dated 19 September 2026. Field testing with screen readers (VoiceOver, TalkBack, NVDA) and an independent laboratory audit have not yet been completed. Full AA conformance is therefore not claimed.

ISO/IEC 40500:2012 is identical to WCAG 2.0 AA. Because the WCAG 2.2 AA target includes the 2.0 AA criteria, it covers the technical scope of 40500:2012.

Status of the AA criteria added in WCAG 2.2:

4. Measures takenCopy Anchor Link

Across all surfaces

• Skip link to the main content (2.4.1)
• Keyboard access; focus trap in dialogs, closing with Escape and focus returning on close (2.1.1, 2.1.2, 2.4.3)
• Respect for the operating system's "reduce motion" preference (2.2.2)
• Labelled controls and ARIA relationships; automated accessibility linting (eslint-plugin-jsx-a11y) in continuous integration (1.3.1, 4.1.2)

Visitor surface

• Form labels, marking of invalid fields and error messages announced to screen readers (1.3.1, 3.3.1, 3.3.2, 4.1.2)
• Radio groups following the WAI-ARIA Authoring Practices (APG) for the rating scale, category choice, personnel code recovery and single-choice survey questions (2.1.1, 4.1.2)
• A consistent main heading on every page; accessible names that match visible labels (2.4.6, 2.5.3)
• Correct page language and text direction; source language marked on untranslated content blocks (3.1.1, 3.1.2)
• Strengthened contrast in the photo header, location popover, footer and focus ring (1.4.3, 1.4.11)

Admin panel

• Cards and report rows open with Enter or Space; action buttons that appear on mouse hover also appear on keyboard focus (2.1.1)
• Table captions and column header relationships for screen readers in operations and report tables (1.3.1)
• Accessible names on icon buttons; labels on switches and checkboxes; dialog role and focus trap in the location drawer (4.1.2)
• Turkish and English interface; report indicators and notification templates in the organization language (3.1.2)
• Image role and an accessible name in the organization language on report charts (1.1.1)
• Target size of at least 24 CSS pixels on icon buttons (2.5.8)
• Accessible names on audio play, option delete, grid cell and search clear buttons (4.1.2)

5. Language accessCopy Anchor Link

The Arabic visitor interface uses right-to-left text direction, mirrored icons and direction-aware layout. Key parity between language catalogs is checked in continuous integration. See the Multilingual Statement for details.

Status: Partial. End-to-end delivery of every channel in every language is not claimed.

6. Known limitationsCopy Anchor Link

• The quality of image alternative text and caption files is the responsibility of the organization writing the content.
• WCAG 2.5.5 (44-pixel targets, AAA) is not claimed. 2.5.8 (24 pixels, AA) is the target; unmeasured small targets may remain.
• 2.5.7: logo cropping, dragging images and tables in the text editor and panning a zoomed image do not yet have a full single-pointer alternative.
• Screen reader field testing has not yet been recorded.
• The text and poster editor canvas and report charts are not claimed as accessible interactive widgets.
• Some automated accessibility warnings are intentionally left at warning level.

7. Evaluation methodCopy Anchor Link

8. Planned workCopy Anchor Link

Screen reader field testing is planned to cover these paths:

1. Visitor home screen, language selection (including Arabic), QR and tiles
2. Feedback, hygiene rating, survey and ticket tracking
3. Staff sign-in and code recovery
4. Admin panel: skip link, building cards and location drawer
5. Admin panel: feedback and hygiene lists and detail dialogs
6. Admin panel: report tables and chart names
7. The "reduce motion" preference

This statement will be updated when testing is complete.

9. Feedback and contactCopy Anchor Link

If you run into an accessibility problem or need content in another format, contact us:

We aim to respond to feedback within 10 business days.

Content on visitor screens (page text, images, survey questions) is prepared by the organization concerned. We recommend raising problems with that content with the organization first.

10. Framework mapping (for tenders and audits)Copy Anchor Link

11. ReviewCopy Anchor Link

This statement is reviewed at least once a year or on a major product release.

This statement is published in Turkish and English. Both versions contain the same information.