hangel Accessibility Conformance Report
International Edition (Based on VPAT® Version 2.5 INT)
- Name of Product/Version
hangel web application at hangel.org (live version of 18 November 2026)
hangel for Android 2.0.12
hangel for iOS 2.0.7
- Report Date
18 November 2026 (report version 1.0)
- Product Description
hangel is a social impact platform run by a non-profit association. Volunteers find and join events and volunteering opportunities, check in with QR codes and receive certificates. Non-governmental organisations (NGOs) publish events and posts and manage volunteers from an administration panel. The platform also includes Oda (video meetings), a library, a grants and funding guide, a marketplace where shopping generates donations to a chosen NGO, and a disaster module with the hangel Disaster Walkie-Talkie.
The iOS and Android apps are Capacitor shells that display the same web interface in the system WebView, with native extensions such as push notifications, iOS Live Activities, Android widgets, wallet passes, the camera (QR scanning) and Bluetooth (hangel Disaster Walkie-Talkie). The interface is available in 12 languages.
- Contact Information
hangel - Uluslararası Sosyal Fayda Derneği (Social Business Global), Türkiye (Turkey)
Email: turkiye@hangel.org
Accessibility statement and feedback: https://hangel.org/accessibility
- Notes
This report is a self-assessment made by hangel. It is not an independent audit, a certification or an accreditation, and hangel does not claim full conformance with WCAG 2.2. The target is WCAG 2.2 Level AA; applicable Level AAA criteria are reported as goals.
Scope: public pages and main user flows of hangel.org (including the association sub-site), signed-in volunteer screens, the NGO administration panel, and the iOS and Android apps. Because the apps render the same web interface, one conformance level is given for web and apps; remarks name native parts where they differ.
Content uploaded by organisations and users (images, posters, videos) and embedded third-party services (for example maps, partner brand shop pages, bot protection and external meeting tools) are outside hangel’s direct control and are noted where relevant.
Criteria for which hangel has no measured evidence are reported as “Partially Supports” with the remark “Not yet independently audited.” The term “Not Evaluated” is not used.
- Evaluation Methods Used
- Automated testing: axe-core 4.10.3 in headless Chromium (Playwright 1.60) on 24 representative public pages of the live site, run on 12 and 18 November 2026: default theme at 1280 px, 390 px and 320 px; dark theme and the in-app high-contrast setting at 1280 px. Rule sets: WCAG 2.0, 2.1 and 2.2 Level A and AA, WCAG AAA and best practices. Automated tools find only part of the possible issues.
- Keyboard-only testing: the first 40 Tab stops on 8 key pages at 1280 px and 390 px, checking visible focus, focus obscured by other content and the skip link as first stop (12 and 18 November 2026).
- Screen reader testing: macOS VoiceOver with Safari on the main public flows (sign-in, navigation, language selection, event pages, marketplace, footer) and with the hangel iOS app running on an Apple-silicon Mac (4 November 2026). Issues found were fixed.
- Accessibility tree review: Playwright WebKit with an iPhone profile on 17 screens, including signed-in volunteer and NGO-panel screens (6 November 2026): unnamed controls, heading order, landmarks, focus containment in dialogs, label in name, target size.
- Manual review (31 October 2026): accessibility tree and keyboard-only use of the main flows, 320 px width, increased text spacing and forced colours, including signed-in screens.
- Responsive layout scan of signed-in administration panels at 390 px and 360 px (6 November 2026).
- Automated regression tests in the code repository: 20 accessibility test files with 218 tests, passing on 18 November 2026 (colour-contrast calculations, main landmarks, screen reader guards, accessibility settings, the Oda accessibility layer and the post-sign-up accessibility question).
- Source code review.
- Not yet performed: TalkBack on Android; VoiceOver on a physical iPhone; NVDA and JAWS; Switch Control and Switch Access; testing with users with disabilities; an independent third-party audit.
Summary
Number of criteria by conformance level in each table. Heading rows are not counted.
| Table | Supports | Partially Supports | Does Not Support | Not Applicable |
|---|---|---|---|---|
| WCAG 2.2 Report – Table 1: Success Criteria, Level A | 19 | 12 | 1 | 0 |
| WCAG 2.2 Report – Table 2: Success Criteria, Level AA | 13 | 10 | 1 | 0 |
| WCAG 2.2 Report – Table 3: Success Criteria, Level AAA | 5 | 23 | 3 | 0 |
| Revised Section 508 Report – Chapter 3: Functional Performance Criteria (FPC) | 3 | 6 | 0 | 0 |
| Revised Section 508 Report – Chapter 4: Hardware | 0 | 0 | 0 | 1 |
| Revised Section 508 Report – Chapter 5: Software | 1 | 20 | 2 | 3 |
| Revised Section 508 Report – Chapter 6: Support Documentation and Services | 2 | 2 | 0 | 1 |
| EN 301 549 Report – Chapter 4: 4.2 Functional Performance Statements (FPS) | 4 | 7 | 0 | 0 |
| EN 301 549 Report – Chapter 5: Generic Requirements | 3 | 1 | 0 | 7 |
| EN 301 549 Report – Chapter 6: ICT with Two-Way Voice Communication | 1 | 7 | 1 | 8 |
| EN 301 549 Report – Chapter 7: ICT with Video Capabilities | 0 | 5 | 2 | 2 |
| EN 301 549 Report – Chapters 8 to 10: Hardware, Web and Non-web Documents | 0 | 2 | 0 | 3 |
| EN 301 549 Report – Chapter 11: Software | 0 | 19 | 1 | 5 |
| EN 301 549 Report – Chapters 12 and 13: Documentation and Support Services; Relay and Emergency Service Access | 2 | 3 | 0 | 1 |
| All rows (212) | 53 | 117 | 11 | 31 |
Main known gaps
- On the home page, the dimmed “coming soon” app-store badges have text contrast below 4.5:1 (2.3:1 to 4.3:1); in the dark theme, small labels on library item covers also fall below 4.5:1.
- Promotional videos on the press and logo-usage pages have no captions, transcripts or audio description; only the HR introduction film is captioned (Türkiye Turkish and English).
- Oda live captions work only in Chrome and Edge, not in Safari or Firefox; there is no real-time text (RTT).
- PDF certificates and reports exported by the product are untagged (not PDF/UA).
- Event album photos use the file name as alternative text, and most upload forms do not ask for an image description.
- Seven association sub-site pages and the app-support page have no main landmark.
- The iOS app reads Bold Text, Differentiate Without Colour and Button Shapes but does not apply them yet.
- Screen reader testing has been done only with macOS VoiceOver; TalkBack, NVDA, JAWS, Switch Control/Access, VoiceOver on a physical iPhone, testing with users with disabilities and an independent audit are still to be done.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards and guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) · Level AA (Yes) · Level AAA (Yes, reported in Table 3) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) · Level AA (Yes) · Level AAA (Yes, reported in Table 3) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) · Level AA (Yes) · Level AAA (Yes, reported in Table 3 as goals) |
| Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017; Corrections to the ICT Final Rule as published by the U.S. Access Board in the Federal Register on January 22, 2018 | Yes |
| EN 301 549 Accessibility requirements for ICT products and services – V3.2.1 (2021-03) | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports:
- The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports:
- Some functionality of the product does not meet the criterion.
- Does Not Support:
- The majority of product functionality does not meet the criterion.
- Not Applicable:
- The criterion is not relevant to the product.
- Not Evaluated:
- The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria. Not used in this report.
WCAG 2.2 Report
When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.x Conformance Requirements.
Table 1: Success Criteria, Level A
Each criterion also applies to: EN 301 549 Clause 9 (Web), Clause 10 (Non-web documents), Clause 11 (Open functionality software), 11.8.2 (Authoring tool), 12.1.2 (Product documentation) and 12.2.4 (Support documentation); Revised Section 508: 501 (Web and Software), 504.2 (Authoring tool) and 602.3 (Support documentation). Conformance levels apply to the web application and to the iOS and Android apps.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Interface icons have an accessible name or are hidden from assistive technology as decorative; automated scans (12 and 18 November 2026) found no image without a text alternative on the 24 scanned pages. Known gaps: photos in event albums use the file name as alternative text; images and posters uploaded by organisations and users may have no description, and most upload forms do not ask for one. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Partially Supports | Some prerecorded promotional media on the press and logo-usage pages have no text alternative or transcript. Not yet independently audited. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | The hangel HR introduction film has Türkiye Turkish and English WebVTT captions. Promotional videos on the press and logo-usage pages do not have caption files yet. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Does Not Support | No audio description or full text alternative is provided for prerecorded promotional videos yet. |
| 1.3.1 Info and Relationships | Partially Supports | Pages use landmarks, headings, lists and programmatically associated form labels (the shared label component binds every label to its field). Known gaps: seven pages of the association sub-site and the app-support page have no main landmark; some generated PDF documents are untagged (see EN 301 549 Clause 10). |
| 1.3.2 Meaningful Sequence | Supports | Reading and focus order were checked with keyboard-only use, accessibility-tree review and macOS VoiceOver on the main flows (31 October, 4 and 6 November 2026). The order issues found (brand cards, volunteering cards, event page heading) were fixed. |
| 1.3.3 Sensory Characteristics | Partially Supports | Instructions are written as text, but not all instructional text has been reviewed for reliance on shape, colour, size or location. Not yet independently audited. |
| 1.4.1 Use of Color | Supports | Status is shown with text labels as well as colour. Users can turn on link underlines and colour filters in the accessibility settings. |
| 1.4.2 Audio Control | Supports | No audio starts automatically for more than 3 seconds. A setting to mute automatic sounds is available. |
| 2.1.1 Keyboard | Partially Supports | Keyboard-only testing (12 and 18 November 2026): on 8 key pages at 1280 px and 390 px, all 634 Tab stops tested were reachable with visible focus; the main flows were operated with the keyboard in earlier reviews (31 October and 4 November 2026). Map views have not been tested with the keyboard only. |
| 2.1.2 No Keyboard Trap | Supports | No keyboard trap was found in keyboard-only testing (12 and 18 November 2026) or in VoiceOver testing. Dialogs keep focus inside while open and close with Esc. |
| 2.1.4 Character Key Shortcuts | Supports | Single-key shortcuts exist only in Oda video meetings (M, V, H, S, C, A) and can be turned off in the Oda accessibility panel; a general “limit shortcuts” setting is also available. |
| 2.2.1 Timing Adjustable | Supports | Sessions do not expire on inactivity. In certificate exams, the “remove time limits” setting triples the time for each question. Live quiz questions during real-time events fall under the real-time exception. |
| 2.2.2 Pause, Stop, Hide | Supports | Auto-advancing carousels and page animations have pause controls. The “reduce motion” setting and the system reduced-motion preference stop non-essential movement. |
| 2.3.1 Three Flashes or Below Threshold | Partially Supports | The interface itself has no flashing content. Videos and images uploaded by organisations and users are not screened for flashes. |
| 2.4.1 Bypass Blocks | Partially Supports | All 24 scanned pages have a main landmark, and in keyboard testing the first Tab stop on every tested page is a skip link to the main content (16 of 16 page and width combinations, 18 November 2026). Known gap: seven association sub-site pages and the app-support page have no main landmark for the skip link to target. |
| 2.4.2 Page Titled | Supports | Every page has a title; screens without their own title take it from the main heading. Automated scans found no page without a title (18 November 2026). |
| 2.4.3 Focus Order | Supports | Focus order was checked with keyboard-only testing at desktop and phone widths and with VoiceOver on the main flows; it follows the visual order. Dialogs move focus into the dialog and back when closed. |
| 2.4.4 Link Purpose (In Context) | Supports | Links on 22 public pages were reviewed for ambiguous text (4 November 2026); link text, alone or with its sentence or list item, describes the destination. |
| 2.5.1 Pointer Gestures | Supports | No function requires multipoint or path-based gestures. Image cropping offers arrow buttons as well as dragging. |
| 2.5.2 Pointer Cancellation | Supports | Controls activate on release. The push-to-talk button of the hangel Disaster Walkie-Talkie records while held and sends on release; it also works with Space or Enter. |
| 2.5.3 Label in Name | Supports | Visible labels and accessible names were compared on 22 public pages (4 November 2026) and on 17 phone screens (6 November 2026); the accessible name contains the visible label. |
| 2.5.4 Motion Actuation | Supports | No function is operated by shaking or tilting the device. |
| 3.1.1 Language of Page | Supports | The page language attribute matches the selected interface language (12 languages). Automated scans found the correct lang attribute on all scanned pages. |
| 3.2.1 On Focus | Supports | No change of context on focus was observed in keyboard-only testing (18 November 2026) or VoiceOver testing (4 November 2026). |
| 3.2.2 On Input | Partially Supports | Form fields do not submit or navigate when their value changes in the forms reviewed. Not all forms, including administration panel filters, have been reviewed. Not yet independently audited. |
| 3.2.6 Consistent Help | Partially Supports | Help, support and feedback links are in the shared menu and footer. It has not been verified on every screen (for example the administration panels) that they appear in the same relative order. Not yet independently audited. |
| 3.3.1 Error Identification | Supports | Forms such as event, post and organisation profile forms name the field in error in text and connect the message to the field. |
| 3.3.2 Labels or Instructions | Supports | Form fields have visible labels that are programmatically associated with the field; automated scans found no unlabelled form field on the scanned pages. |
| 3.3.7 Redundant Entry | Partially Supports | Drafts are saved automatically and profile data is reused. It has not been verified across every multi-step process that information is never requested twice. Not yet independently audited. |
| 4.1.1 Parsing | Supports | WCAG 2.2 marks this criterion as obsolete and always satisfied. It is reported for WCAG 2.0/2.1 and EN 301 549: pages are generated by React/Next.js, which produces well-formed markup. |
| 4.1.2 Name, Role, Value | Partially Supports | Controls use native HTML elements or WAI-ARIA patterns. Automated scans (18 November 2026) found no button, link or form field without an accessible name on the scanned pages; 78 ARIA attribute values flagged by the tool still need manual review. Screen reader testing has been done with macOS VoiceOver only; TalkBack, NVDA and JAWS have not been tested, and VoiceOver has not been tested on a physical iPhone. |
1.1.1 Non-text Content
Partially Supports
Interface icons have an accessible name or are hidden from assistive technology as decorative; automated scans (12 and 18 November 2026) found no image without a text alternative on the 24 scanned pages. Known gaps: photos in event albums use the file name as alternative text; images and posters uploaded by organisations and users may have no description, and most upload forms do not ask for one.
1.2.1 Audio-only and Video-only (Prerecorded)
Partially Supports
Some prerecorded promotional media on the press and logo-usage pages have no text alternative or transcript. Not yet independently audited.
1.2.2 Captions (Prerecorded)
Partially Supports
The hangel HR introduction film has Türkiye Turkish and English WebVTT captions. Promotional videos on the press and logo-usage pages do not have caption files yet.
1.2.3 Audio Description or Media Alternative (Prerecorded)
Does Not Support
No audio description or full text alternative is provided for prerecorded promotional videos yet.
1.3.1 Info and Relationships
Partially Supports
Pages use landmarks, headings, lists and programmatically associated form labels (the shared label component binds every label to its field). Known gaps: seven pages of the association sub-site and the app-support page have no main landmark; some generated PDF documents are untagged (see EN 301 549 Clause 10).
1.3.2 Meaningful Sequence
Supports
Reading and focus order were checked with keyboard-only use, accessibility-tree review and macOS VoiceOver on the main flows (31 October, 4 and 6 November 2026). The order issues found (brand cards, volunteering cards, event page heading) were fixed.
1.3.3 Sensory Characteristics
Partially Supports
Instructions are written as text, but not all instructional text has been reviewed for reliance on shape, colour, size or location. Not yet independently audited.
1.4.1 Use of Color
Supports
Status is shown with text labels as well as colour. Users can turn on link underlines and colour filters in the accessibility settings.
1.4.2 Audio Control
Supports
No audio starts automatically for more than 3 seconds. A setting to mute automatic sounds is available.
2.1.1 Keyboard
Partially Supports
Keyboard-only testing (12 and 18 November 2026): on 8 key pages at 1280 px and 390 px, all 634 Tab stops tested were reachable with visible focus; the main flows were operated with the keyboard in earlier reviews (31 October and 4 November 2026). Map views have not been tested with the keyboard only.
2.1.2 No Keyboard Trap
Supports
No keyboard trap was found in keyboard-only testing (12 and 18 November 2026) or in VoiceOver testing. Dialogs keep focus inside while open and close with Esc.
2.1.4 Character Key Shortcuts
Supports
Single-key shortcuts exist only in Oda video meetings (M, V, H, S, C, A) and can be turned off in the Oda accessibility panel; a general “limit shortcuts” setting is also available.
2.2.1 Timing Adjustable
Supports
Sessions do not expire on inactivity. In certificate exams, the “remove time limits” setting triples the time for each question. Live quiz questions during real-time events fall under the real-time exception.
2.2.2 Pause, Stop, Hide
Supports
Auto-advancing carousels and page animations have pause controls. The “reduce motion” setting and the system reduced-motion preference stop non-essential movement.
2.3.1 Three Flashes or Below Threshold
Partially Supports
The interface itself has no flashing content. Videos and images uploaded by organisations and users are not screened for flashes.
2.4.1 Bypass Blocks
Partially Supports
All 24 scanned pages have a main landmark, and in keyboard testing the first Tab stop on every tested page is a skip link to the main content (16 of 16 page and width combinations, 18 November 2026). Known gap: seven association sub-site pages and the app-support page have no main landmark for the skip link to target.
2.4.2 Page Titled
Supports
Every page has a title; screens without their own title take it from the main heading. Automated scans found no page without a title (18 November 2026).
2.4.3 Focus Order
Supports
Focus order was checked with keyboard-only testing at desktop and phone widths and with VoiceOver on the main flows; it follows the visual order. Dialogs move focus into the dialog and back when closed.
2.4.4 Link Purpose (In Context)
Supports
Links on 22 public pages were reviewed for ambiguous text (4 November 2026); link text, alone or with its sentence or list item, describes the destination.
2.5.1 Pointer Gestures
Supports
No function requires multipoint or path-based gestures. Image cropping offers arrow buttons as well as dragging.
2.5.2 Pointer Cancellation
Supports
Controls activate on release. The push-to-talk button of the hangel Disaster Walkie-Talkie records while held and sends on release; it also works with Space or Enter.
2.5.3 Label in Name
Supports
Visible labels and accessible names were compared on 22 public pages (4 November 2026) and on 17 phone screens (6 November 2026); the accessible name contains the visible label.
2.5.4 Motion Actuation
Supports
No function is operated by shaking or tilting the device.
3.1.1 Language of Page
Supports
The page language attribute matches the selected interface language (12 languages). Automated scans found the correct lang attribute on all scanned pages.
3.2.1 On Focus
Supports
No change of context on focus was observed in keyboard-only testing (18 November 2026) or VoiceOver testing (4 November 2026).
3.2.2 On Input
Partially Supports
Form fields do not submit or navigate when their value changes in the forms reviewed. Not all forms, including administration panel filters, have been reviewed. Not yet independently audited.
3.2.6 Consistent Help
Partially Supports
Help, support and feedback links are in the shared menu and footer. It has not been verified on every screen (for example the administration panels) that they appear in the same relative order. Not yet independently audited.
3.3.1 Error Identification
Supports
Forms such as event, post and organisation profile forms name the field in error in text and connect the message to the field.
3.3.2 Labels or Instructions
Supports
Form fields have visible labels that are programmatically associated with the field; automated scans found no unlabelled form field on the scanned pages.
3.3.7 Redundant Entry
Partially Supports
Drafts are saved automatically and profile data is reused. It has not been verified across every multi-step process that information is never requested twice. Not yet independently audited.
4.1.1 Parsing
Supports
WCAG 2.2 marks this criterion as obsolete and always satisfied. It is reported for WCAG 2.0/2.1 and EN 301 549: pages are generated by React/Next.js, which produces well-formed markup.
4.1.2 Name, Role, Value
Partially Supports
Controls use native HTML elements or WAI-ARIA patterns. Automated scans (18 November 2026) found no button, link or form field without an accessible name on the scanned pages; 78 ARIA attribute values flagged by the tool still need manual review. Screen reader testing has been done with macOS VoiceOver only; TalkBack, NVDA and JAWS have not been tested, and VoiceOver has not been tested on a physical iPhone.
Table 2: Success Criteria, Level AA
Each criterion also applies to: EN 301 549 Clause 9 (Web), Clause 10 (Non-web documents), Clause 11 (Open functionality software), 11.8.2 (Authoring tool), 12.1.2 (Product documentation) and 12.2.4 (Support documentation); Revised Section 508: 501 (Web and Software), 504.2 (Authoring tool) and 602.3 (Support documentation). Conformance levels apply to the web application and to the iOS and Android apps.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Partially Supports | Oda video meetings generate live captions in Chrome and Edge; captions are not available in Safari and Firefox. Online events held on external meeting tools rely on those tools’ captions. |
| 1.2.5 Audio Description (Prerecorded) | Does Not Support | Prerecorded promotional videos have no audio description yet. |
| 1.3.4 Orientation | Supports | The web application does not lock the display orientation; the iOS app declares portrait and both landscape orientations, and the Android app does not lock orientation. |
| 1.3.5 Identify Input Purpose | Supports | Fields that collect the user’s own personal data (name, email, phone, address, one-time code) use the matching autocomplete values. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Automated scans (18 November 2026, 24 pages at 1280, 390 and 320 px) found one failing component: on the home page, the “coming soon” app-store badges (AppGallery, Galaxy Store) are dimmed and their text reaches only 2.3:1 to 4.3:1. In the dark theme, small labels on library item covers also fail on one library page (16 text nodes). No other text failed 4.5:1; text over images and gradients, which the tool marks for manual review, has not been checked by hand. The “hangel” logotype in the footer is a logotype and outside the scope of this criterion. |
| 1.4.4 Resize Text | Supports | Text can be enlarged to 200% with browser zoom and the in-app text size setting without loss of content (layouts were tested down to 320 px). The iOS app follows Dynamic Type and the Android app follows the system font scale. |
| 1.4.5 Images of Text | Partially Supports | Interface text is HTML text. Some posters and banners uploaded by organisations and brands contain text inside images. |
| 1.4.10 Reflow | Partially Supports | At 390 px and 320 px, none of the 24 scanned public pages scrolls horizontally (18 November 2026). Data tables in the administration panels scroll horizontally inside their container (an allowed exception for data tables); signed-in panels were last scanned at 390 px and 360 px on 6 November 2026. |
| 1.4.11 Non-text Contrast | Partially Supports | Input borders and focus indicators use high-contrast colours. The colours of some charts and graphics have not been checked. Not yet independently audited. |
| 1.4.12 Text Spacing | Supports | Content stays readable with increased line, letter, word and paragraph spacing (main flows tested 31 October 2026). Line, word and paragraph spacing can also be set in the accessibility settings. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips and popovers can be dismissed with Esc, stay visible while hovered and do not disappear until the pointer or focus moves away. |
| 2.4.5 Multiple Ways | Supports | Pages can be reached through the main menu, search, the site map page (hangel.org/sitemap) and footer links. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose; every scanned page has one main heading. |
| 2.4.7 Focus Visible | Supports | Keyboard-only testing (18 November 2026): all 634 Tab stops on 8 key pages at 1280 px and 390 px showed a visible focus indicator. A setting for a stronger focus indicator is also available. |
| 2.4.11 Focus Not Obscured (Minimum) | Partially Supports | Keyboard-only testing (18 November 2026): 1 of 634 Tab stops was partly covered: at 390 px, the “Apply” button on a volunteering detail page is overlapped by an adjacent element (see 2.5.8). The cookie notice no longer covers focused elements, which was fixed after the 12 November 2026 test. |
| 2.5.7 Dragging Movements | Supports | Drag operations (image cropping and reordering) have button alternatives. |
| 2.5.8 Target Size (Minimum) | Partially Supports | Automated scans (18 November 2026) found one failure: at phone widths, the sticky “Apply” button on volunteering detail pages does not have enough spacing from an adjacent element. No other target failed on the scanned pages. |
| 3.1.2 Language of Parts | Partially Supports | Language names in the language selector are marked with their own language. Passages in another language inside content written by organisations and users are not marked. |
| 3.2.3 Consistent Navigation | Supports | The header, bottom tab bar and footer are shared components and appear in the same relative order across pages; the association sub-site uses its own header and footer, also consistently. |
| 3.2.4 Consistent Identification | Supports | Components with the same function use shared components and the same translated labels from a single translation source. |
| 3.3.3 Error Suggestion | Partially Supports | The main forms (sign-up, sign-in, event and post creation) suggest how to fix an error. Not all administration panel forms have been reviewed. Not yet independently audited. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially Supports | Irreversible actions such as deleting content or cancelling an application ask for confirmation, and a “confirm before sending” setting extends this to more actions. Not every flow has been reviewed. Not yet independently audited. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Sign-in uses a one-time code sent by email (the code field supports pasting and one-time-code autofill) or Google or Apple sign-in; no cognitive function test is required. Invisible, score-based bot protection can occasionally reject a genuine attempt; the email code route remains available. |
| 4.1.3 Status Messages | Supports | Search results, form errors, notifications, check-in confirmation and Oda status changes (microphone, camera, captions) are announced through live regions; covered by automated screen reader guard tests. |
1.2.4 Captions (Live)
Partially Supports
Oda video meetings generate live captions in Chrome and Edge; captions are not available in Safari and Firefox. Online events held on external meeting tools rely on those tools’ captions.
1.2.5 Audio Description (Prerecorded)
Does Not Support
Prerecorded promotional videos have no audio description yet.
1.3.4 Orientation
Supports
The web application does not lock the display orientation; the iOS app declares portrait and both landscape orientations, and the Android app does not lock orientation.
1.3.5 Identify Input Purpose
Supports
Fields that collect the user’s own personal data (name, email, phone, address, one-time code) use the matching autocomplete values.
1.4.3 Contrast (Minimum)
Partially Supports
Automated scans (18 November 2026, 24 pages at 1280, 390 and 320 px) found one failing component: on the home page, the “coming soon” app-store badges (AppGallery, Galaxy Store) are dimmed and their text reaches only 2.3:1 to 4.3:1. In the dark theme, small labels on library item covers also fail on one library page (16 text nodes). No other text failed 4.5:1; text over images and gradients, which the tool marks for manual review, has not been checked by hand. The “hangel” logotype in the footer is a logotype and outside the scope of this criterion.
1.4.4 Resize Text
Supports
Text can be enlarged to 200% with browser zoom and the in-app text size setting without loss of content (layouts were tested down to 320 px). The iOS app follows Dynamic Type and the Android app follows the system font scale.
1.4.5 Images of Text
Partially Supports
Interface text is HTML text. Some posters and banners uploaded by organisations and brands contain text inside images.
1.4.10 Reflow
Partially Supports
At 390 px and 320 px, none of the 24 scanned public pages scrolls horizontally (18 November 2026). Data tables in the administration panels scroll horizontally inside their container (an allowed exception for data tables); signed-in panels were last scanned at 390 px and 360 px on 6 November 2026.
1.4.11 Non-text Contrast
Partially Supports
Input borders and focus indicators use high-contrast colours. The colours of some charts and graphics have not been checked. Not yet independently audited.
1.4.12 Text Spacing
Supports
Content stays readable with increased line, letter, word and paragraph spacing (main flows tested 31 October 2026). Line, word and paragraph spacing can also be set in the accessibility settings.
1.4.13 Content on Hover or Focus
Supports
Tooltips and popovers can be dismissed with Esc, stay visible while hovered and do not disappear until the pointer or focus moves away.
2.4.5 Multiple Ways
Supports
Pages can be reached through the main menu, search, the site map page (hangel.org/sitemap) and footer links.
2.4.6 Headings and Labels
Supports
Headings and labels describe their topic or purpose; every scanned page has one main heading.
2.4.7 Focus Visible
Supports
Keyboard-only testing (18 November 2026): all 634 Tab stops on 8 key pages at 1280 px and 390 px showed a visible focus indicator. A setting for a stronger focus indicator is also available.
2.4.11 Focus Not Obscured (Minimum)
Partially Supports
Keyboard-only testing (18 November 2026): 1 of 634 Tab stops was partly covered: at 390 px, the “Apply” button on a volunteering detail page is overlapped by an adjacent element (see 2.5.8). The cookie notice no longer covers focused elements, which was fixed after the 12 November 2026 test.
2.5.7 Dragging Movements
Supports
Drag operations (image cropping and reordering) have button alternatives.
2.5.8 Target Size (Minimum)
Partially Supports
Automated scans (18 November 2026) found one failure: at phone widths, the sticky “Apply” button on volunteering detail pages does not have enough spacing from an adjacent element. No other target failed on the scanned pages.
3.1.2 Language of Parts
Partially Supports
Language names in the language selector are marked with their own language. Passages in another language inside content written by organisations and users are not marked.
3.2.3 Consistent Navigation
Supports
The header, bottom tab bar and footer are shared components and appear in the same relative order across pages; the association sub-site uses its own header and footer, also consistently.
3.2.4 Consistent Identification
Supports
Components with the same function use shared components and the same translated labels from a single translation source.
3.3.3 Error Suggestion
Partially Supports
The main forms (sign-up, sign-in, event and post creation) suggest how to fix an error. Not all administration panel forms have been reviewed. Not yet independently audited.
3.3.4 Error Prevention (Legal, Financial, Data)
Partially Supports
Irreversible actions such as deleting content or cancelling an application ask for confirmation, and a “confirm before sending” setting extends this to more actions. Not every flow has been reviewed. Not yet independently audited.
3.3.8 Accessible Authentication (Minimum)
Supports
Sign-in uses a one-time code sent by email (the code field supports pasting and one-time-code autofill) or Google or Apple sign-in; no cognitive function test is required. Invisible, score-based bot protection can occasionally reject a genuine attempt; the email code route remains available.
4.1.3 Status Messages
Supports
Search results, form errors, notifications, check-in confirmation and Oda status changes (microphone, camera, captions) are announced through live regions; covered by automated screen reader guard tests.
Table 3: Success Criteria, Level AAA
Level AAA criteria are hangel’s goals; no AAA conformance is claimed. WCAG notes that it is not recommended to require Level AAA conformance for entire sites.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) | Does Not Support | Prerecorded content has no sign language interpretation. |
| 1.2.7 Extended Audio Description (Prerecorded) | Does Not Support | No extended audio description is provided. |
| 1.2.8 Media Alternative (Prerecorded) | Does Not Support | No full text alternative is provided for prerecorded videos yet. |
| 1.2.9 Audio-only (Live) | Partially Supports | Live audio in Oda meetings can be followed through live captions in Chrome and Edge; not in Safari and Firefox. Not yet independently audited. |
| 1.3.6 Identify Purpose | Partially Supports | Landmarks and ARIA roles identify regions and controls. Personalisation of icons or symbols is not supported. |
| 1.4.6 Contrast (Enhanced) | Partially Supports | With the default brand colours, 2,689 text nodes on the 24 scanned pages (desktop, 18 November 2026) are below 7:1; apart from the items listed under 1.4.3, they are between 4.5:1 and 7:1. With the in-app high-contrast setting, 482 nodes remain, mostly in sections with fixed colours (library 171, marketplace 83, grants guide 58, Oda 39). |
| 1.4.7 Low or No Background Audio | Partially Supports | Prerecorded videos have not been checked for background sound levels. Not yet independently audited. |
| 1.4.8 Visual Presentation | Partially Supports | Users can choose colour themes, a reading view with limited line length, line and paragraph spacing and text size. Some sections with fixed colours change only in the yellow-on-black theme. |
| 1.4.9 Images of Text (No Exception) | Partially Supports | Interface text is HTML text; some posters and banners uploaded by organisations and brands contain text inside images. |
| 2.1.3 Keyboard (No Exception) | Partially Supports | See 2.1.1. Map views have not been tested with the keyboard only. |
| 2.2.3 No Timing | Partially Supports | Apart from certificate exams (where time can be tripled) and live quizzes in real-time events, there are no time limits. |
| 2.2.4 Interruptions | Partially Supports | Notifications can be turned off by channel and a focus mode reduces interruptions. Not yet independently audited. |
| 2.2.5 Re-authenticating | Supports | Sessions do not expire on their own; when a user signs in again, drafts saved on the device are kept. |
| 2.2.6 Timeouts | Supports | There is no inactivity time limit that causes data loss. |
| 2.3.2 Three Flashes | Partially Supports | The interface itself has no flashing content; videos and images uploaded by users are not screened. |
| 2.3.3 Animation from Interactions | Supports | The “reduce motion” setting and the system reduced-motion preference turn off non-essential animation triggered by interaction. |
| 2.4.8 Location | Partially Supports | The current section is marked in the main navigation and tab bar; breadcrumbs are not used on all pages. Not yet independently audited. |
| 2.4.9 Link Purpose (Link Only) | Partially Supports | Most links make sense on their own; some links rely on their surrounding text. Not yet independently audited. |
| 2.4.10 Section Headings | Partially Supports | Content sections have headings. Automated scans (18 November 2026) found the heading level skipping from h2 to h4 in two places (an organisation profile page and the contact page). |
| 2.4.12 Focus Not Obscured (Enhanced) | Partially Supports | See 2.4.11. |
| 2.4.13 Focus Appearance | Partially Supports | A focus ring is present on every tested Tab stop and can be made stronger with the focus indicator setting. The area and contrast of the focus indicator were not measured in this round. |
| 2.5.5 Target Size (Enhanced) | Partially Supports | By default, 1 to 92 interactive elements per scanned page are smaller than 44 × 44 px (mostly inline links and icon buttons). The “large touch targets” setting enlarges controls to at least 44 px. |
| 2.5.6 Concurrent Input Mechanisms | Supports | Touch, mouse, keyboard and voice input can be used at the same time; the product does not restrict the input method. |
| 3.1.3 Unusual Words | Partially Supports | Plain-language texts are available for the main flows; a glossary for specialised terms is not provided. Not yet independently audited. |
| 3.1.4 Abbreviations | Partially Supports | Abbreviations are not expanded systematically. Not yet independently audited. |
| 3.1.5 Reading Level | Partially Supports | A plain-language mode covers the main flows (sign-up, sign-in code, accessibility question, NGO selection) and a read-aloud feature is available; other content has not been simplified. |
| 3.1.6 Pronunciation | Partially Supports | No pronunciation aids are provided. Not yet independently audited. |
| 3.2.5 Change on Request | Partially Supports | Changes of context have not been reviewed against this criterion. Not yet independently audited. |
| 3.3.5 Help | Partially Supports | Help, support and feedback pages are available; context-sensitive help is not offered on every form. |
| 3.3.6 Error Prevention (All) | Partially Supports | Settings forms and irreversible actions ask for confirmation; single-button actions are not all covered. |
| 3.3.9 Accessible Authentication (Enhanced) | Supports | See 3.3.8: sign-in requires no cognitive function test and no object or personal content recognition. |
1.2.6 Sign Language (Prerecorded)
Does Not Support
Prerecorded content has no sign language interpretation.
1.2.7 Extended Audio Description (Prerecorded)
Does Not Support
No extended audio description is provided.
1.2.8 Media Alternative (Prerecorded)
Does Not Support
No full text alternative is provided for prerecorded videos yet.
1.2.9 Audio-only (Live)
Partially Supports
Live audio in Oda meetings can be followed through live captions in Chrome and Edge; not in Safari and Firefox. Not yet independently audited.
1.3.6 Identify Purpose
Partially Supports
Landmarks and ARIA roles identify regions and controls. Personalisation of icons or symbols is not supported.
1.4.6 Contrast (Enhanced)
Partially Supports
With the default brand colours, 2,689 text nodes on the 24 scanned pages (desktop, 18 November 2026) are below 7:1; apart from the items listed under 1.4.3, they are between 4.5:1 and 7:1. With the in-app high-contrast setting, 482 nodes remain, mostly in sections with fixed colours (library 171, marketplace 83, grants guide 58, Oda 39).
1.4.7 Low or No Background Audio
Partially Supports
Prerecorded videos have not been checked for background sound levels. Not yet independently audited.
1.4.8 Visual Presentation
Partially Supports
Users can choose colour themes, a reading view with limited line length, line and paragraph spacing and text size. Some sections with fixed colours change only in the yellow-on-black theme.
1.4.9 Images of Text (No Exception)
Partially Supports
Interface text is HTML text; some posters and banners uploaded by organisations and brands contain text inside images.
2.1.3 Keyboard (No Exception)
Partially Supports
See 2.1.1. Map views have not been tested with the keyboard only.
2.2.3 No Timing
Partially Supports
Apart from certificate exams (where time can be tripled) and live quizzes in real-time events, there are no time limits.
2.2.4 Interruptions
Partially Supports
Notifications can be turned off by channel and a focus mode reduces interruptions. Not yet independently audited.
2.2.5 Re-authenticating
Supports
Sessions do not expire on their own; when a user signs in again, drafts saved on the device are kept.
2.2.6 Timeouts
Supports
There is no inactivity time limit that causes data loss.
2.3.2 Three Flashes
Partially Supports
The interface itself has no flashing content; videos and images uploaded by users are not screened.
2.3.3 Animation from Interactions
Supports
The “reduce motion” setting and the system reduced-motion preference turn off non-essential animation triggered by interaction.
2.4.8 Location
Partially Supports
The current section is marked in the main navigation and tab bar; breadcrumbs are not used on all pages. Not yet independently audited.
2.4.9 Link Purpose (Link Only)
Partially Supports
Most links make sense on their own; some links rely on their surrounding text. Not yet independently audited.
2.4.10 Section Headings
Partially Supports
Content sections have headings. Automated scans (18 November 2026) found the heading level skipping from h2 to h4 in two places (an organisation profile page and the contact page).
2.4.12 Focus Not Obscured (Enhanced)
Partially Supports
See 2.4.11.
2.4.13 Focus Appearance
Partially Supports
A focus ring is present on every tested Tab stop and can be made stronger with the focus indicator setting. The area and contrast of the focus indicator were not measured in this round.
2.5.5 Target Size (Enhanced)
Partially Supports
By default, 1 to 92 interactive elements per scanned page are smaller than 44 × 44 px (mostly inline links and icon buttons). The “large touch targets” setting enlarges controls to at least 44 px.
2.5.6 Concurrent Input Mechanisms
Supports
Touch, mouse, keyboard and voice input can be used at the same time; the product does not restrict the input method.
3.1.3 Unusual Words
Partially Supports
Plain-language texts are available for the main flows; a glossary for specialised terms is not provided. Not yet independently audited.
3.1.4 Abbreviations
Partially Supports
Abbreviations are not expanded systematically. Not yet independently audited.
3.1.5 Reading Level
Partially Supports
A plain-language mode covers the main flows (sign-up, sign-in code, accessibility question, NGO selection) and a read-aloud feature is available; other content has not been simplified.
3.1.6 Pronunciation
Partially Supports
No pronunciation aids are provided. Not yet independently audited.
3.2.5 Change on Request
Partially Supports
Changes of context have not been reviewed against this criterion. Not yet independently audited.
3.3.5 Help
Partially Supports
Help, support and feedback pages are available; context-sensitive help is not offered on every form.
3.3.6 Error Prevention (All)
Partially Supports
Settings forms and irreversible actions ask for confirmation; single-button actions are not all covered.
3.3.9 Accessible Authentication (Enhanced)
Supports
See 3.3.8: sign-in requires no cognitive function test and no object or personal content recognition.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Controls expose name, role and state, live regions announce changes and the interface detects VoiceOver. Testing has been done with macOS VoiceOver only; TalkBack has not been tested and there has been no testing with blind users. See 1.1.1 and 4.1.2. |
| 302.2 With Limited Vision | Partially Supports | Text size, high-contrast, colour theme, reading view and magnification-friendly reflow are available. Some default colour combinations do not meet 4.5:1 (see 1.4.3). |
| 302.3 Without Perception of Color | Supports | Information is not conveyed by colour alone; link underlines and colour filters can be turned on (see 1.4.1). |
| 302.4 Without Hearing | Partially Supports | Sounds have a visual-alert option and Oda offers live captions in Chrome and Edge. Some promotional videos have no captions (see 1.2.2 and 1.2.4). |
| 302.5 With Limited Hearing | Partially Supports | See 302.4. Oda offers noise suppression and a “listen with translation” option. |
| 302.6 Without Speech | Supports | No function requires speech. Oda has written chat; the walkie-talkie and voice features have text alternatives (messages and help requests). |
| 302.7 With Limited Manipulation | Partially Supports | Full keyboard use, large touch targets, ignore-repeated-taps and long-press duration settings are available. Push-to-talk requires holding a button or key. Switch Control and Switch Access have not been tested. |
| 302.8 With Limited Reach and Strength | Supports | Software only; no physical reach or strength is required beyond the user’s own device and its accessibility features. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | Simple view, plain-language mode for the main flows, read aloud, focus mode, step-by-step posting form and automatic drafts are available. No testing with users with cognitive disabilities has been done. |
302.1 Without Vision
Partially Supports
Controls expose name, role and state, live regions announce changes and the interface detects VoiceOver. Testing has been done with macOS VoiceOver only; TalkBack has not been tested and there has been no testing with blind users. See 1.1.1 and 4.1.2.
302.2 With Limited Vision
Partially Supports
Text size, high-contrast, colour theme, reading view and magnification-friendly reflow are available. Some default colour combinations do not meet 4.5:1 (see 1.4.3).
302.3 Without Perception of Color
Supports
Information is not conveyed by colour alone; link underlines and colour filters can be turned on (see 1.4.1).
302.4 Without Hearing
Partially Supports
Sounds have a visual-alert option and Oda offers live captions in Chrome and Edge. Some promotional videos have no captions (see 1.2.2 and 1.2.4).
302.5 With Limited Hearing
Partially Supports
See 302.4. Oda offers noise suppression and a “listen with translation” option.
302.6 Without Speech
Supports
No function requires speech. Oda has written chat; the walkie-talkie and voice features have text alternatives (messages and help requests).
302.7 With Limited Manipulation
Partially Supports
Full keyboard use, large touch targets, ignore-repeated-taps and long-press duration settings are available. Push-to-talk requires holding a button or key. Switch Control and Switch Access have not been tested.
302.8 With Limited Reach and Strength
Supports
Software only; no physical reach or strength is required beyond the user’s own device and its accessibility features.
302.9 With Limited Language, Cognitive, and Learning Abilities
Partially Supports
Simple view, plain-language mode for the main flows, read aloud, focus mode, step-by-step posting form and automatic drafts are available. No testing with users with cognitive disabilities has been done.
Chapter 4: Hardware
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4 Hardware | Not Applicable | hangel is software; no hardware is provided. |
4 Hardware
Not Applicable
hangel is software; no hardware is provided.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | Heading cell – no response required | The iOS and Android apps display the web interface in the system WebView; see the WCAG 2.x tables for the user interface. The rows below cover the apps as software. |
| 502.2.1 User Control of Accessibility Features | Not Applicable | Applies to platform software only; hangel is an application. |
| 502.2.2 No Disruption of Accessibility Features | Partially Supports | The apps apply the system text size (iOS Dynamic Type, Android font scale) and do not override system accessibility gestures in the tests done (macOS VoiceOver with the iOS app). Not tested with TalkBack, Switch Control or Switch Access. |
| 502.3 Accessibility Services | Heading cell – no response required | The WebView exposes the web interface to the platform accessibility API (UIAccessibility on iOS, AccessibilityNodeInfo on Android). Web content conformance is reported under WCAG 4.1.2. Native parts (push notifications, Live Activities, widgets, wallet passes) use system components. |
| 502.3.1 Object Information | Partially Supports | Name, role and state come from HTML and ARIA through the WebView; the iOS Live Activity and the Android widget were given concise accessibility labels. Not tested with TalkBack. See 4.1.2. |
| 502.3.2 Modification of Object Information | Partially Supports | Through the WebView and standard HTML controls. See 4.1.2. Not yet independently audited. |
| 502.3.3 Row, Column, and Headers | Partially Supports | Data tables use HTML table markup with header cells. Not yet independently audited. |
| 502.3.4 Values | Partially Supports | Values of inputs, sliders and selections are exposed through HTML and ARIA. See 4.1.2. |
| 502.3.5 Modification of Values | Partially Supports | Through standard HTML controls in the WebView. Not yet independently audited. |
| 502.3.6 Label Relationships | Partially Supports | Form labels are programmatically associated (see 1.3.1 and 3.3.2). Not yet independently audited. |
| 502.3.7 Hierarchical Relationships | Partially Supports | Lists, menus and trees use HTML or ARIA structure. Not yet independently audited. |
| 502.3.8 Text | Partially Supports | Text content is exposed through the WebView. Not yet independently audited. |
| 502.3.9 Modification of Text | Partially Supports | Text fields are standard HTML inputs. Not yet independently audited. |
| 502.3.10 List of Actions | Partially Supports | Actions are exposed through standard controls. Not yet independently audited. |
| 502.3.11 Actions on Objects | Partially Supports | Actions can be performed through standard controls and the keyboard. Not yet independently audited. |
| 502.3.12 Focus Cursor | Partially Supports | Keyboard focus is visible and tracked by the WebView (see 2.4.7). Not yet independently audited. |
| 502.3.13 Modification of Focus Cursor | Partially Supports | Focus can be moved programmatically by assistive technology through the WebView. Not yet independently audited. |
| 502.3.14 Event Notification | Partially Supports | Changes are announced through live regions (see 4.1.3). Not yet independently audited. |
| 502.4 Platform Accessibility Features | Not Applicable | Applies to platform software only. |
| 503.2 User Preferences | Partially Supports | System text size, reduced motion, increased contrast, reduced transparency and forced colours are honoured. The iOS app reads Bold Text, Differentiate Without Colour and Button Shapes, but the interface does not apply them yet. |
| 503.3 Alternative User Interfaces | Supports | The read-aloud feature uses the platform speech synthesis service (Web Speech API) rather than a proprietary engine. |
| 503.4 User Controls for Captions and Audio Description | Heading cell – no response required | |
| 503.4.1 Caption Controls | Partially Supports | Prerecorded videos use the browser’s native player, which shows a captions menu next to the volume control when caption tracks exist. Oda has a captions button in the meeting toolbar; captions themselves work only in Chrome and Edge. |
| 503.4.2 Audio Description Controls | Not Applicable | The product provides no program selection and no audio description tracks. |
| 504.2 Content Creation or Editing | Partially Supports | Organisations create events, posts and mini-sites with forms that produce accessible HTML. Image descriptions are not requested for most uploads, and event album photos use the file name as alternative text. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Partially Supports | Preservation of alternative text when presentations (PPTX) are converted for the event stage has not been verified. Not yet independently audited. |
| 504.2.2 PDF Export | Does Not Support | PDF files exported by the product (for example certificates and reports) are not tagged and do not conform to PDF/UA-1. Certificates also have an HTML verification page. |
| 504.3 Prompts | Does Not Support | Authors are not prompted to add accessibility information such as image descriptions or captions. |
| 504.4 Templates | Partially Supports | Mini-site and event templates are built from accessible components; templates are not labelled for accessibility. Not yet independently audited. |
501.1 Scope – Incorporation of WCAG 2.0 AA
Heading cell – no response required
The iOS and Android apps display the web interface in the system WebView; see the WCAG 2.x tables for the user interface. The rows below cover the apps as software.
502.2.1 User Control of Accessibility Features
Not Applicable
Applies to platform software only; hangel is an application.
502.2.2 No Disruption of Accessibility Features
Partially Supports
The apps apply the system text size (iOS Dynamic Type, Android font scale) and do not override system accessibility gestures in the tests done (macOS VoiceOver with the iOS app). Not tested with TalkBack, Switch Control or Switch Access.
502.3 Accessibility Services
Heading cell – no response required
The WebView exposes the web interface to the platform accessibility API (UIAccessibility on iOS, AccessibilityNodeInfo on Android). Web content conformance is reported under WCAG 4.1.2. Native parts (push notifications, Live Activities, widgets, wallet passes) use system components.
502.3.1 Object Information
Partially Supports
Name, role and state come from HTML and ARIA through the WebView; the iOS Live Activity and the Android widget were given concise accessibility labels. Not tested with TalkBack. See 4.1.2.
502.3.2 Modification of Object Information
Partially Supports
Through the WebView and standard HTML controls. See 4.1.2. Not yet independently audited.
502.3.3 Row, Column, and Headers
Partially Supports
Data tables use HTML table markup with header cells. Not yet independently audited.
502.3.4 Values
Partially Supports
Values of inputs, sliders and selections are exposed through HTML and ARIA. See 4.1.2.
502.3.5 Modification of Values
Partially Supports
Through standard HTML controls in the WebView. Not yet independently audited.
502.3.6 Label Relationships
Partially Supports
Form labels are programmatically associated (see 1.3.1 and 3.3.2). Not yet independently audited.
502.3.7 Hierarchical Relationships
Partially Supports
Lists, menus and trees use HTML or ARIA structure. Not yet independently audited.
502.3.8 Text
Partially Supports
Text content is exposed through the WebView. Not yet independently audited.
502.3.9 Modification of Text
Partially Supports
Text fields are standard HTML inputs. Not yet independently audited.
502.3.10 List of Actions
Partially Supports
Actions are exposed through standard controls. Not yet independently audited.
502.3.11 Actions on Objects
Partially Supports
Actions can be performed through standard controls and the keyboard. Not yet independently audited.
502.3.12 Focus Cursor
Partially Supports
Keyboard focus is visible and tracked by the WebView (see 2.4.7). Not yet independently audited.
502.3.13 Modification of Focus Cursor
Partially Supports
Focus can be moved programmatically by assistive technology through the WebView. Not yet independently audited.
502.3.14 Event Notification
Partially Supports
Changes are announced through live regions (see 4.1.3). Not yet independently audited.
502.4 Platform Accessibility Features
Not Applicable
Applies to platform software only.
503.2 User Preferences
Partially Supports
System text size, reduced motion, increased contrast, reduced transparency and forced colours are honoured. The iOS app reads Bold Text, Differentiate Without Colour and Button Shapes, but the interface does not apply them yet.
503.3 Alternative User Interfaces
Supports
The read-aloud feature uses the platform speech synthesis service (Web Speech API) rather than a proprietary engine.
503.4 User Controls for Captions and Audio Description
Heading cell – no response required
503.4.1 Caption Controls
Partially Supports
Prerecorded videos use the browser’s native player, which shows a captions menu next to the volume control when caption tracks exist. Oda has a captions button in the meeting toolbar; captions themselves work only in Chrome and Edge.
503.4.2 Audio Description Controls
Not Applicable
The product provides no program selection and no audio description tracks.
504.2 Content Creation or Editing
Partially Supports
Organisations create events, posts and mini-sites with forms that produce accessible HTML. Image descriptions are not requested for most uploads, and event album photos use the file name as alternative text.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion
Partially Supports
Preservation of alternative text when presentations (PPTX) are converted for the event stage has not been verified. Not yet independently audited.
504.2.2 PDF Export
Does Not Support
PDF files exported by the product (for example certificates and reports) are not tagged and do not conform to PDF/UA-1. Certificates also have an HTML verification page.
504.3 Prompts
Does Not Support
Authors are not prompted to add accessibility information such as image descriptions or captions.
504.4 Templates
Partially Supports
Mini-site and event templates are built from accessible components; templates are not labelled for accessibility. Not yet independently audited.
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | Heading cell – no response required | |
| 602.2 Accessibility and Compatibility Features | Supports | hangel.org/accessibility lists all accessibility settings, the accessibility statement with known issues and this report, in 12 languages. |
| 602.3 Electronic Support Documentation | Partially Supports | Support, help and policy pages are web pages covered by the WCAG 2.x tables above; the same partial conformance applies. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All support documentation is electronic. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Support by email (turkiye@hangel.org) and the feedback form answers questions about accessibility features; the accessibility statement explains how to report barriers. |
| 603.3 Accommodation of Communication Needs | Partially Supports | Support is offered in writing (email and feedback form), and feedback is answered within 10 working days. There is no live help, and sign language or video relay support is not offered. |
601.1 Scope
Heading cell – no response required
602.2 Accessibility and Compatibility Features
Supports
hangel.org/accessibility lists all accessibility settings, the accessibility statement with known issues and this report, in 12 languages.
602.3 Electronic Support Documentation
Partially Supports
Support, help and policy pages are web pages covered by the WCAG 2.x tables above; the same partial conformance applies.
602.4 Alternate Formats for Non-Electronic Support Documentation
Not Applicable
All support documentation is electronic.
603.2 Information on Accessibility and Compatibility Features
Supports
Support by email (turkiye@hangel.org) and the feedback form answers questions about accessibility features; the accessibility statement explains how to report barriers.
603.3 Accommodation of Communication Needs
Partially Supports
Support is offered in writing (email and feedback form), and feedback is answered within 10 working days. There is no live help, and sign language or video relay support is not offered.
EN 301 549 Report
Chapter 4: 4.2 Functional Performance Statements (FPS)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | Partially Supports | See Section 508 302.1. |
| 4.2.2 Usage with limited vision | Partially Supports | See Section 508 302.2. |
| 4.2.3 Usage without perception of colour | Supports | See Section 508 302.3. |
| 4.2.4 Usage without hearing | Partially Supports | See Section 508 302.4. |
| 4.2.5 Usage with limited hearing | Partially Supports | See Section 508 302.5. |
| 4.2.6 Usage with no or limited vocal capability | Supports | See Section 508 302.6. |
| 4.2.7 Usage with limited manipulation or strength | Partially Supports | See Section 508 302.7. |
| 4.2.8 Usage with limited reach | Supports | See Section 508 302.8. |
| 4.2.9 Minimize photosensitive seizure triggers | Partially Supports | The interface has no flashing content and honours reduced motion; content uploaded by users is not screened (see 2.3.1). |
| 4.2.10 Usage with limited cognition, language or learning | Partially Supports | See Section 508 302.9. |
| 4.2.11 Privacy | Supports | Accessibility features work without asking about disability. Disability information is not stored on the server; only the resulting setting preferences are saved. Accessibility settings do not expose personal information to others. |
4.2.1 Usage without vision
Partially Supports
See Section 508 302.1.
4.2.2 Usage with limited vision
Partially Supports
See Section 508 302.2.
4.2.3 Usage without perception of colour
Supports
See Section 508 302.3.
4.2.4 Usage without hearing
Partially Supports
See Section 508 302.4.
4.2.5 Usage with limited hearing
Partially Supports
See Section 508 302.5.
4.2.6 Usage with no or limited vocal capability
Supports
See Section 508 302.6.
4.2.7 Usage with limited manipulation or strength
Partially Supports
See Section 508 302.7.
4.2.8 Usage with limited reach
Supports
See Section 508 302.8.
4.2.9 Minimize photosensitive seizure triggers
Partially Supports
The interface has no flashing content and honours reduced motion; content uploaded by users is not screened (see 2.3.1).
4.2.10 Usage with limited cognition, language or learning
Partially Supports
See Section 508 302.9.
4.2.11 Privacy
Supports
Accessibility features work without asking about disability. Disability information is not stored on the server; only the resulting setting preferences are saved. Accessibility settings do not expose personal information to others.
Chapter 5: Generic Requirements
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 5.1 Closed functionality (5.1.2 to 5.1.6.2) | Not Applicable | The product is not closed to assistive technology; it runs in web browsers and on iOS and Android, which support assistive technologies. |
| 5.2 Activation of accessibility features | Supports | Accessibility settings can be opened from Settings › Accessibility, are offered in a question after sign-up and are applied without sign-in; system preferences are applied automatically. |
| 5.3 Biometrics | Supports | Biometrics are not used for identification or control. An optional face-matching feature helps users find their own photos in event albums; albums can be browsed without it. |
| 5.4 Preservation of accessibility information during conversion | Partially Supports | See Section 508 504.2.1. |
| 5.5.1 Means of operation | Not Applicable | No hardware operable parts. |
| 5.5.2 Operable parts discernibility | Not Applicable | No hardware operable parts. |
| 5.6.1 Tactile or auditory status | Not Applicable | No locking or toggle hardware controls. |
| 5.6.2 Visual status | Not Applicable | No locking or toggle hardware controls. |
| 5.7 Key repeat | Not Applicable | The product provides no keyboard of its own; platform keyboard settings apply. An in-app “ignore repeated taps” setting is also available. |
| 5.8 Double-strike key acceptance | Not Applicable | The product provides no keyboard of its own; platform keyboard settings apply. |
| 5.9 Simultaneous user actions | Supports | No function requires simultaneous actions such as multi-finger gestures (see 2.5.1). |
5.1 Closed functionality (5.1.2 to 5.1.6.2)
Not Applicable
The product is not closed to assistive technology; it runs in web browsers and on iOS and Android, which support assistive technologies.
5.2 Activation of accessibility features
Supports
Accessibility settings can be opened from Settings › Accessibility, are offered in a question after sign-up and are applied without sign-in; system preferences are applied automatically.
5.3 Biometrics
Supports
Biometrics are not used for identification or control. An optional face-matching feature helps users find their own photos in event albums; albums can be browsed without it.
5.4 Preservation of accessibility information during conversion
Partially Supports
See Section 508 504.2.1.
5.5.1 Means of operation
Not Applicable
No hardware operable parts.
5.5.2 Operable parts discernibility
Not Applicable
No hardware operable parts.
5.6.1 Tactile or auditory status
Not Applicable
No locking or toggle hardware controls.
5.6.2 Visual status
Not Applicable
No locking or toggle hardware controls.
5.7 Key repeat
Not Applicable
The product provides no keyboard of its own; platform keyboard settings apply. An in-app “ignore repeated taps” setting is also available.
5.8 Double-strike key acceptance
Not Applicable
The product provides no keyboard of its own; platform keyboard settings apply.
5.9 Simultaneous user actions
Supports
No function requires simultaneous actions such as multi-finger gestures (see 2.5.1).
Chapter 6: ICT with Two-Way Voice Communication
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 6.1 Audio bandwidth for speech | Partially Supports | Oda video meetings use WebRTC with the Opus codec (wideband or better). Online walkie-talkie messages use Opus at 32 kbit/s. The audio bandwidth of the offline Bluetooth walkie-talkie mode has not been measured. |
| 6.2.1.1 RTT communication | Does Not Support | Oda offers message-based text chat alongside voice, but not character-by-character real-time text (RTT). |
| 6.2.1.2 Concurrent voice and text | Not Applicable | RTT is not provided (see 6.2.1.1). Written chat can be used at the same time as voice in Oda. |
| 6.2.2.1 Visually distinguishable display | Not Applicable | RTT is not provided. |
| 6.2.2.2 Programmatically determinable send and receive direction | Not Applicable | RTT is not provided. |
| 6.2.2.3 Speaker identification | Not Applicable | RTT is not provided. |
| 6.2.2.4 Visual indicator of Audio with RTT | Not Applicable | RTT is not provided. |
| 6.2.3 Interoperability | Not Applicable | RTT is not provided. |
| 6.2.4 RTT responsiveness | Not Applicable | RTT is not provided. |
| 6.3 Caller ID | Partially Supports | In the NGO virtual call centre, the caller’s number is shown as text. A second modality has not been verified. Not yet independently audited. |
| 6.4 Alternatives to voice-based services | Partially Supports | The NGO virtual call centre can use voicemail and a configurable call flow for phone callers. The same organisations can be reached by written messages and web forms on hangel, but the call-flow content itself is not offered in text. |
| 6.5.1 General (video communication) | Heading cell – no response required | |
| 6.5.2 Resolution | Partially Supports | Oda captures camera video at 960 × 540. On low bandwidth, adaptive streaming may deliver a 320 × 180 layer, below QVGA. |
| 6.5.3 Frame rate | Partially Supports | Oda captures camera video at 24 frames per second; the received frame rate under low bandwidth has not been measured. |
| 6.5.4 Synchronization between audio and video | Partially Supports | Audio and video are synchronised by WebRTC; the 100 ms limit has not been measured. Not yet independently audited. |
| 6.5.5 Visual indicator of audio with video | Supports | Oda shows a visual indicator on the participant who is speaking. |
| 6.5.6 Speaker identification with video (sign language) communication | Partially Supports | A sign language interpreter can be pinned as a large tile on every participant’s screen. Signing participants are not automatically identified as the active speaker. |
| 6.6 Alternatives to video-based services | Not Applicable | The product provides no video answering machine, auto attendant or interactive video response. |
6.1 Audio bandwidth for speech
Partially Supports
Oda video meetings use WebRTC with the Opus codec (wideband or better). Online walkie-talkie messages use Opus at 32 kbit/s. The audio bandwidth of the offline Bluetooth walkie-talkie mode has not been measured.
6.2.1.1 RTT communication
Does Not Support
Oda offers message-based text chat alongside voice, but not character-by-character real-time text (RTT).
6.2.1.2 Concurrent voice and text
Not Applicable
RTT is not provided (see 6.2.1.1). Written chat can be used at the same time as voice in Oda.
6.2.2.1 Visually distinguishable display
Not Applicable
RTT is not provided.
6.2.2.2 Programmatically determinable send and receive direction
Not Applicable
RTT is not provided.
6.2.2.3 Speaker identification
Not Applicable
RTT is not provided.
6.2.2.4 Visual indicator of Audio with RTT
Not Applicable
RTT is not provided.
6.2.3 Interoperability
Not Applicable
RTT is not provided.
6.2.4 RTT responsiveness
Not Applicable
RTT is not provided.
6.3 Caller ID
Partially Supports
In the NGO virtual call centre, the caller’s number is shown as text. A second modality has not been verified. Not yet independently audited.
6.4 Alternatives to voice-based services
Partially Supports
The NGO virtual call centre can use voicemail and a configurable call flow for phone callers. The same organisations can be reached by written messages and web forms on hangel, but the call-flow content itself is not offered in text.
6.5.1 General (video communication)
Heading cell – no response required
6.5.2 Resolution
Partially Supports
Oda captures camera video at 960 × 540. On low bandwidth, adaptive streaming may deliver a 320 × 180 layer, below QVGA.
6.5.3 Frame rate
Partially Supports
Oda captures camera video at 24 frames per second; the received frame rate under low bandwidth has not been measured.
6.5.4 Synchronization between audio and video
Partially Supports
Audio and video are synchronised by WebRTC; the 100 ms limit has not been measured. Not yet independently audited.
6.5.5 Visual indicator of audio with video
Supports
Oda shows a visual indicator on the participant who is speaking.
6.5.6 Speaker identification with video (sign language) communication
Partially Supports
A sign language interpreter can be pinned as a large tile on every participant’s screen. Signing participants are not automatically identified as the active speaker.
6.6 Alternatives to video-based services
Not Applicable
The product provides no video answering machine, auto attendant or interactive video response.
Chapter 7: ICT with Video Capabilities
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 7.1.1 Captioning playback | Partially Supports | Prerecorded videos use the native HTML5 player, which displays available WebVTT caption tracks. Oda live captions work in Chrome and Edge only. |
| 7.1.2 Captioning synchronization | Partially Supports | WebVTT captions are synchronised by the browser player; Oda live captions appear after speech is recognised. Not yet independently audited. |
| 7.1.3 Preservation of captioning | Partially Supports | Whether captions are kept in Oda meeting recordings has not been verified. Not yet independently audited. |
| 7.1.4 Captions characteristics | Partially Supports | Browser players apply the platform caption style settings where the browser supports them; in Oda, caption size and position can be adjusted only to a limited extent. |
| 7.1.5 Spoken subtitles | Does Not Support | Captions are not offered as spoken output. |
| 7.2.1 Audio description playback | Does Not Support | No mechanism to select and play audio description is provided. |
| 7.2.2 Audio description synchronization | Not Applicable | Audio description is not provided. |
| 7.2.3 Preservation of audio description | Not Applicable | Audio description is not provided. |
| 7.3 User controls for captions and audio description | Partially Supports | See Section 508 503.4.1. There is no audio description control. |
7.1.1 Captioning playback
Partially Supports
Prerecorded videos use the native HTML5 player, which displays available WebVTT caption tracks. Oda live captions work in Chrome and Edge only.
7.1.2 Captioning synchronization
Partially Supports
WebVTT captions are synchronised by the browser player; Oda live captions appear after speech is recognised. Not yet independently audited.
7.1.3 Preservation of captioning
Partially Supports
Whether captions are kept in Oda meeting recordings has not been verified. Not yet independently audited.
7.1.4 Captions characteristics
Partially Supports
Browser players apply the platform caption style settings where the browser supports them; in Oda, caption size and position can be adjusted only to a limited extent.
7.1.5 Spoken subtitles
Does Not Support
Captions are not offered as spoken output.
7.2.1 Audio description playback
Does Not Support
No mechanism to select and play audio description is provided.
7.2.2 Audio description synchronization
Not Applicable
Audio description is not provided.
7.2.3 Preservation of audio description
Not Applicable
Audio description is not provided.
7.3 User controls for captions and audio description
Partially Supports
See Section 508 503.4.1. There is no audio description control.
Chapters 8 to 10: Hardware, Web and Non-web Documents
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 8 Hardware | Not Applicable | hangel is software; no hardware is provided. |
| 9.1–9.4 Web content (WCAG 2.1 Level A and AA) | Heading cell – no response required | See the WCAG 2.x section, Tables 1 and 2. EN 301 549 V3.2.1 references WCAG 2.1; the additional WCAG 2.2 criteria are also reported there. |
| 9.6 WCAG conformance requirements | Partially Supports | The web content does not yet fully meet WCAG 2.1 Level AA; see the Partially Supports rows in Tables 1 and 2. |
| 10.1–10.4 Non-web documents | Partially Supports | Documents produced by the product (for example PDF certificates and reports) are not tagged, so headings, reading order and table structure are not exposed. Certificates have an accessible HTML verification page. This report’s PDF is tagged. |
| 10.5 Caption positioning | Not Applicable | Non-web documents produced by the product contain no captions. |
| 10.6 Audio description timing | Not Applicable | Non-web documents produced by the product contain no synchronised media. |
8 Hardware
Not Applicable
hangel is software; no hardware is provided.
9.1–9.4 Web content (WCAG 2.1 Level A and AA)
Heading cell – no response required
See the WCAG 2.x section, Tables 1 and 2. EN 301 549 V3.2.1 references WCAG 2.1; the additional WCAG 2.2 criteria are also reported there.
9.6 WCAG conformance requirements
Partially Supports
The web content does not yet fully meet WCAG 2.1 Level AA; see the Partially Supports rows in Tables 1 and 2.
10.1–10.4 Non-web documents
Partially Supports
Documents produced by the product (for example PDF certificates and reports) are not tagged, so headings, reading order and table structure are not exposed. Certificates have an accessible HTML verification page. This report’s PDF is tagged.
10.5 Caption positioning
Not Applicable
Non-web documents produced by the product contain no captions.
10.6 Audio description timing
Not Applicable
Non-web documents produced by the product contain no synchronised media.
Chapter 11: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.0 General | Heading cell – no response required | The iOS and Android apps display the web interface in the system WebView. |
| 11.1–11.4 Software: WCAG-equivalent requirements (open functionality) | Heading cell – no response required | See the WCAG 2.x section; the same conformance levels apply to the apps. |
| 11.5.1 Closed functionality | Not Applicable | The apps are not closed to assistive technology. |
| 11.5.2.1 Platform accessibility service support for software that provides a user interface | Not Applicable | Applies to platform software only. |
| 11.5.2.2 Platform accessibility service support for assistive technologies | Not Applicable | Applies to platform software only. |
| 11.5.2.3 Use of accessibility services | Partially Supports | See Section 508 502.3. |
| 11.5.2.4 Assistive technology | Not Applicable | hangel is not assistive technology. |
| 11.5.2.5 Object information | Partially Supports | See Section 508 502.3.1. |
| 11.5.2.6 Row, column, and headers | Partially Supports | See Section 508 502.3.3. |
| 11.5.2.7 Values | Partially Supports | See Section 508 502.3.4. |
| 11.5.2.8 Label relationships | Partially Supports | See Section 508 502.3.6. |
| 11.5.2.9 Parent-child relationships | Partially Supports | See Section 508 502.3.7. |
| 11.5.2.10 Text | Partially Supports | See Section 508 502.3.8. |
| 11.5.2.11 List of available actions | Partially Supports | See Section 508 502.3.10. |
| 11.5.2.12 Execution of available actions | Partially Supports | See Section 508 502.3.11. |
| 11.5.2.13 Tracking of focus and selection attributes | Partially Supports | See Section 508 502.3.12. |
| 11.5.2.14 Modification of focus and selection attributes | Partially Supports | See Section 508 502.3.13. |
| 11.5.2.15 Change notification | Partially Supports | See Section 508 502.3.14. |
| 11.5.2.16 Modifications of states and properties | Partially Supports | See Section 508 502.3.2. |
| 11.5.2.17 Modifications of values and text | Partially Supports | See Section 508 502.3.5 and 502.3.9. |
| 11.6.1 User control of accessibility features | Not Applicable | Applies to platform software only. |
| 11.6.2 No disruption of accessibility features | Partially Supports | See Section 508 502.2.2. |
| 11.7 User preferences | Partially Supports | See Section 508 503.2. |
| 11.8.1 Content technology | Heading cell – no response required | Content created by organisations is published as HTML. |
| 11.8.2 Accessible content creation | Partially Supports | See Section 508 504.2. |
| 11.8.3 Preservation of accessibility information in transformations | Partially Supports | See Section 508 504.2.1. |
| 11.8.4 Repair assistance | Does Not Support | The product does not check authored content for accessibility problems or suggest repairs. |
| 11.8.5 Templates | Partially Supports | See Section 508 504.4. |
11.0 General
Heading cell – no response required
The iOS and Android apps display the web interface in the system WebView.
11.1–11.4 Software: WCAG-equivalent requirements (open functionality)
Heading cell – no response required
See the WCAG 2.x section; the same conformance levels apply to the apps.
11.5.1 Closed functionality
Not Applicable
The apps are not closed to assistive technology.
11.5.2.1 Platform accessibility service support for software that provides a user interface
Not Applicable
Applies to platform software only.
11.5.2.2 Platform accessibility service support for assistive technologies
Not Applicable
Applies to platform software only.
11.5.2.3 Use of accessibility services
Partially Supports
See Section 508 502.3.
11.5.2.4 Assistive technology
Not Applicable
hangel is not assistive technology.
11.5.2.5 Object information
Partially Supports
See Section 508 502.3.1.
11.5.2.6 Row, column, and headers
Partially Supports
See Section 508 502.3.3.
11.5.2.7 Values
Partially Supports
See Section 508 502.3.4.
11.5.2.8 Label relationships
Partially Supports
See Section 508 502.3.6.
11.5.2.9 Parent-child relationships
Partially Supports
See Section 508 502.3.7.
11.5.2.10 Text
Partially Supports
See Section 508 502.3.8.
11.5.2.11 List of available actions
Partially Supports
See Section 508 502.3.10.
11.5.2.12 Execution of available actions
Partially Supports
See Section 508 502.3.11.
11.5.2.13 Tracking of focus and selection attributes
Partially Supports
See Section 508 502.3.12.
11.5.2.14 Modification of focus and selection attributes
Partially Supports
See Section 508 502.3.13.
11.5.2.15 Change notification
Partially Supports
See Section 508 502.3.14.
11.5.2.16 Modifications of states and properties
Partially Supports
See Section 508 502.3.2.
11.5.2.17 Modifications of values and text
Partially Supports
See Section 508 502.3.5 and 502.3.9.
11.6.1 User control of accessibility features
Not Applicable
Applies to platform software only.
11.6.2 No disruption of accessibility features
Partially Supports
See Section 508 502.2.2.
11.7 User preferences
Partially Supports
See Section 508 503.2.
11.8.1 Content technology
Heading cell – no response required
Content created by organisations is published as HTML.
11.8.2 Accessible content creation
Partially Supports
See Section 508 504.2.
11.8.3 Preservation of accessibility information in transformations
Partially Supports
See Section 508 504.2.1.
11.8.4 Repair assistance
Does Not Support
The product does not check authored content for accessibility problems or suggest repairs.
11.8.5 Templates
Partially Supports
See Section 508 504.4.
Chapters 12 and 13: Documentation and Support Services; Relay and Emergency Service Access
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | See Section 508 602.2. |
| 12.1.2 Accessible documentation | Partially Supports | See Section 508 602.3. |
| 12.2.2 Information on accessibility and compatibility features | Supports | See Section 508 603.2. |
| 12.2.3 Effective communication | Partially Supports | See Section 508 603.3. |
| 12.2.4 Accessible documentation | Partially Supports | See Section 508 602.3. |
| 13 ICT providing relay or emergency service access (13.1.2 to 13.3) | Not Applicable | hangel provides no relay service and no access to emergency services. Its emergency and disaster features are information and peer-to-peer messaging tools that tell users to call 112 first. |
12.1.1 Accessibility and compatibility features
Supports
See Section 508 602.2.
12.1.2 Accessible documentation
Partially Supports
See Section 508 602.3.
12.2.2 Information on accessibility and compatibility features
Supports
See Section 508 603.2.
12.2.3 Effective communication
Partially Supports
See Section 508 603.3.
12.2.4 Accessible documentation
Partially Supports
See Section 508 602.3.
13 ICT providing relay or emergency service access (13.1.2 to 13.3)
Not Applicable
hangel provides no relay service and no access to emergency services. Its emergency and disaster features are information and peer-to-peer messaging tools that tell users to call 112 first.
Legal Disclaimer (hangel)
This Accessibility Conformance Report is a self-assessment of the product versions named above on the report date. It is not an independent audit, a certification or an accreditation, and it must not be presented as one. The information is provided in good faith, based on the measurements and tests described under “Evaluation Methods Used”. The product changes often; hangel updates this report when it does and welcomes reports of accessibility barriers at turkiye@hangel.org or hangel.org/feedback.
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).