Accessibility Policy

1. Purpose and place of this document

To set out our principles for making hangel usable by everyone, including people with visual, hearing, motor and cognitive disabilities. Details of the current status, the measurement method and known issues are in the Accessibility Statement (hangel.org/accessibility). If this policy and the statement differ, the statement is the reference for the current status.

2. Scope

The hangel.org website, the hangel Android and iOS apps, Oda meeting rooms, documents generated on the platform (certificates, reports, PDFs) and the Association's own events.

3. Principles

1. Minimum target: WCAG 2.2 AA and the accessibility checklist for websites and mobile apps of Türkiye's Ministry of Family and Social Services.
2. Higher target: Meet the WCAG 2.2 AAA criteria that do not change the brand's appearance (for example touch targets of at least 44 pixels, visible focus, section headings, no time limits) everywhere, and criteria such as enhanced contrast when a person turns on a system or in-app accessibility setting.
3. Respect for system settings: Aim to work smoothly with VoiceOver and TalkBack, text enlargement, bold text, increased contrast, reduced motion, inverted colours and high-contrast mode, Voice Control and Switch Control.
4. Honesty: We do not use phrases such as "fully compliant", "AAA" or "certified"; if the status is "partially conformant", we say so. Automated scanning does not replace testing with real users.

4. Roles and responsibilities

• Board of Directors: approves this policy and allocates resources.
• Product and development team: checks new screens for keyboard use, screen reader names, contrast and touch targets before release, and records any issues found in the statement.
• Event organisers (the Association): plan venue and content accessibility (captions, sign language needs).

5. How it works at hangel today

• Statement and measurement: The accessibility statement follows the W3C structure: target, status (partially conformant), scope, method, known issues and feedback. Measurements use automated axe-core scans, keyboard-only navigation, inspection of the accessibility tree, a 320-pixel width check and forced-colours mode.
• Simple view: A view with large buttons and only the core flows is available; it can be turned on in Settings → Accessibility and switches on automatically when Assistive Access is active on iPhone.
• Every page has a "Skip to main content" link.
• Fix cycle: Issues found are fixed, measured again and the "known issues" list in the statement is updated.

6. Not yet in place and our goals

• No independent accessibility audit has been commissioned.
• Comprehensive manual testing with real screen readers (VoiceOver, TalkBack) and testing with disabled users have not yet been done; they are planned.
• Some PDFs are untagged, some videos lack captions and some third-party components (for example bot protection) are outside our control. The current list is in the statement.
• Oda meetings do not offer sign language interpreter support.
• The minimum target in the statement is AA; reflecting the higher AAA target in the statement is pending.

7. How to raise a concern

Access barriers or suggestions: info@hangel.org. Feedback is added to the known issues list and queued for fixing.

8. Review

The policy at least once a year; the statement after every measurement round and every significant fix.

9. Related documents

hangel.org/accessibility (Accessibility Statement) · Diversity, Equity and Inclusion Policy · Language and Translation Policy · Existing "Accessibility Policy" and "ISO/IEC 25010 / EN 301 549 Status and Roadmap Statement"