← Back to Swipcall
Accessibility Statement
Last updated: April 3, 2026
About this statement
This accessibility statement applies to the website www.swipcall.com and the Swipcall Android application, operated by Swipcall (individual developer).
This statement was prepared on April 3, 2026, based on a self-assessment carried out by the developer.
Compliance status
This website is partially compliant with EN 301 549 V3.2.1 (2021-03) and the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, due to the non-compliances and exemptions listed below.
This statement has been drafted with reference to the requirements of Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies, and in the spirit of the European Accessibility Act (EAA) - Directive (EU) 2019/882.
Accessibility features of this website
The following measures have been taken to ensure accessibility:
- Semantic HTML structure with proper heading hierarchy
- Sufficient color contrast ratios (meeting WCAG AAA for text on backgrounds)
- Full keyboard navigation support throughout the site
- Skip-to-content link for keyboard users
- ARIA labels on all interactive elements and icons
- Responsive design that supports browser zoom up to 200% without loss of content or functionality
- Respects user motion preferences via the prefers-reduced-motion media query
- Visible focus indicators on all interactive elements
- Focus trapping in modal dialogs for assistive technology users
- Ability to pause all animations
Built-in accessibility widget
This website includes a built-in accessibility widget, accessible via the orange button at the bottom-left corner of every page. The widget provides the following adjustments:
- Text adjustments: Font size scaling, line height, word spacing, readable font (dyslexia-friendly)
- Display adjustments: High contrast mode, grayscale mode, link highlighting
- Navigation aids: Large cursor, pause all animations
- All settings persist across pages and sessions
- Reset all adjustments with one click
Android application accessibility
The Swipcall Android app is designed with accessibility in mind:
- Minimum touch targets of 48x48dp for all interactive elements (per WCAG 2.5.5)
- High contrast dark theme with WCAG AAA compliant color ratios
- Content descriptions on all buttons and icons for screen readers (TalkBack)
- Support for Android system font scaling up to 200%
- Respects the Android "reduce motion" system setting
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with EN 301 549 / WCAG 2.1 AA
- Decorative SVG illustrations: Some decorative SVG graphics on the landing page may not be fully hidden from all screen readers in all configurations, though they are marked with appropriate ARIA attributes (aria-hidden="true"). This relates to WCAG 1.1.1 (Non-text Content).
- Language of parts: Some interface strings or content sections may not have explicit lang attributes when they contain text in a language different from the page's primary language. This relates to WCAG 3.1.2 (Language of Parts).
Disproportionate burden
No disproportionate burden is claimed at this time.
Content not within the scope of applicable legislation
- Android system overlay (post-call popup): The Swipcall Android app uses a system overlay popup that appears after phone calls. This overlay relies on Android system overlay permissions (SYSTEM_ALERT_WINDOW), which may interact differently with assistive technologies such as TalkBack depending on the device manufacturer and Android version. Full accessibility of system overlays is constrained by the Android platform and falls outside the developer's direct control.
Assessment method
The accessibility of this website and the Android application was assessed through a self-assessment conducted by the developer. This self-assessment included:
- Manual testing of keyboard navigation and focus management
- Review of color contrast ratios using automated contrast checking tools
- Testing with screen reader software (TalkBack on Android, browser-based readers on the web)
- Review of HTML markup for semantic correctness and ARIA usage
- Automated accessibility scanning with browser developer tools
The assessment was last conducted on April 3, 2026.
A formal third-party audit has not been performed. We intend to pursue independent evaluation as the project grows.
Technical specifications
The accessibility of this website relies on the following technologies:
- HTML5
- CSS3
- JavaScript (ES6+)
- WAI-ARIA 1.1
These technologies are relied upon for conformance with the accessibility standards referenced in this statement.
Compatibility with assistive technologies
This website is designed to be compatible with the following assistive technologies:
- Screen readers (NVDA, JAWS, VoiceOver, TalkBack)
- Screen magnification software
- Speech recognition software
- Operating system accessibility features (high contrast mode, reduced motion, large text)
The website is designed to work with current versions of major browsers (Chrome, Firefox, Safari, Edge) and their built-in accessibility features.
Known limitations
Despite our efforts to ensure accessibility of this website and the Android application, some limitations may exist. Below is a description of known limitations and potential solutions:
- Accessibility widget persistence: The built-in accessibility widget stores settings in the browser's localStorage. If localStorage is disabled or cleared, previously selected accessibility preferences will be reset. Users may need to reconfigure their settings in such cases.
- Third-party content: Links to external services such as the Google Play Store are outside our control and may not meet the same accessibility standards.
- Overlay interaction on Android: The post-call overlay popup may not be fully navigable via TalkBack on all Android devices, due to platform-level constraints on system overlay windows. We are actively monitoring Android platform updates that may improve this experience.
Feedback and contact information
We welcome your feedback on the accessibility of Swipcall. If you encounter any accessibility barriers, need information in an alternative format, or have suggestions for improvement, please contact us:
Email: eitaymcc@gmail.com
Please include the following in your message where possible:
- A description of the accessibility problem you encountered
- The URL of the page or the screen in the app where you experienced the issue
- The assistive technology and browser or device you were using
We aim to respond to all accessibility feedback within 5 business days. We will do our best to address reported issues promptly and provide an accessible alternative where a fix is not immediately possible.
Enforcement procedure
If you have contacted us regarding an accessibility issue and are not satisfied with our response, you may escalate the matter to the relevant national enforcement body in your country.
In the European Union, each Member State has designated a national enforcement body under Directive (EU) 2016/2102. You can find the contact details for your country's enforcement body through the European Commission's Web Accessibility Directive monitoring page.
Under the European Accessibility Act (Directive (EU) 2019/882), market surveillance authorities in each Member State oversee compliance for products and services within scope.
Applicable standards
This statement references the following standards and legislation:
Swipcall