Accessibility Statement for Skapp

Skapp takes the following measures to ensure accessibility of Skapp :

• Include accessibility throughout our internal policies.
• Integrate accessibility into our procurement practices.
• Provide continual accessibility training for our staff.
• Assign clear accessibility goals and responsibilities.
• Employ formal accessibility quality assurance methods.

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Skapp is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

We welcome your feedback on the accessibility of Skapp . Please let us know if you encounter accessibility barriers on Skapp :

• Phone: +94 764 275 373
• E-mail:[email protected]
• Visitor Address: No. 42, Level, 15 Nawam Mawatha, Colombo 00200, Sri Lanka
• Postal Address: No. 42, Level, 15 Nawam Mawatha, Colombo 00200, Sri Lanka

We try to respond to feedback within 24 hours.

Skapp is designed to be compatible with the following assistive technologies:

• Google Chrome (latest) with NVDA (2023.4 or later)
• Mozilla Firefox (latest) with NVDA (2023.4 or later)
• Safari (latest mobile) with VoiceOver
• iOS 15 or later —with VoiceOver
• Android 11 or later — with TalkBack

Accessibility of Skapp relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS
• JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Despite our best efforts to ensure accessibility ofSkapp , there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations forSkapp :

1. Certain pages and UI components at intermediate viewport widths may not display correctly, as our responsive styles are incomplete for these screen sizes : On affected viewports, layout containers can overlap or extend beyond the viewport edge, causing unintended horizontal scrolling or truncated content that is difficult to read or interact with because our current CSS media queries do not include breakpoints for these intermediate device widths, and fluid grid rules are not consistently applied across all components. We are auditing all page templates and stylesheets to identify missing breakpoints, updating our CSS to add these intermediate media queries, refactoring layouts to use relative units. Please try rotating your device orientation, adjusting your browser zoom level, or switching to a desktop view if available. If the issue persists, report it via emailing [email protected] so we can prioritize a fix.

Skapp assessed the accessibility of Skapp by the following approaches:

• Self-evaluation

An evaluation report for Skapp is available at: Accessibility Evaluation Report.

This statement was created on 27 June 2025 using the W3C Accessibility Statement Generator Tool.