Our Commitment
Kulpa is committed to achieving full conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, including the additions for Mobile and Touch. These guidelines define best practices for making digital content accessible to people with a wide range of disabilities — including visual, auditory, motor, and cognitive differences.
While some areas of the platform do not yet fully meet all success criteria, we continuously work to improve accessibility across all aspects of the kulpa platform through user testing, design updates, and accessibility reviews.
How We Support Accessibility
- We design and test features with accessibility in mind from the start.
- We use clear, consistent layouts and intuitive interactions.
- We provide alternative text for images and meaningful labels for controls.
- We aim for strong colour contrast and readable typography.
- We regularly review feedback to identify and fix any barriers that may arise.
For assistance, AbilityNet also has advice on making your device easier to use.
Ongoing Improvements
Accessibility is an evolving goal. We are committed to continuous improvement and are actively enhancing our tools, content, and support to make the kulpa platform even more inclusive over time.
1. Conformance Summary
Standard / Guideline - Web Content Accessibility Guidelines (WCAG) 2.2 Level A, AA, AAA
Conformance Level - Partially Conforms
Remarks and Explanations - Kulpa meets most success criteria for Level A and AA. Continuous improvement is underway for screen reader labelling and other areas. |
Standard / Guideline - Revised Section 508 (U.S.)
Conformance Level - Partially Conforms | Functionality aligns with applicable 508 standards.
Remarks and Explanations - Further testing is planned for embedded multimedia descriptions.
Standard / Guideline - EN 301 549 (EU Accessibility Standard)
Conformance Level - Partially Conforms
Remarks and Explanations - Features support user accessibility under the standard; minor adjustments are being implemented to enhance compliance with interactive component behaviours. |
2. Detailed Accessibility Features
Kulpa includes accessibility features to support inclusive use:
- Keyboard and touch navigation
- Screen reader compatibility
- Meaningful semantic structure and labelling
- Sufficient colour contrast and scalable text
- Alternative text for key visual elements
- Simple, consistent layout to minimise cognitive load
3. Known Accessibility Limitations
We are aware of a few areas currently under review:
- Some non-critical icons and infographics may lack descriptive text.
- Occasional focus order inconsistencies during fast navigation.
- Some videos and animations may not yet include audio descriptions.
We are actively addressing these in upcoming releases and welcome feedback from users and accessibility reviewers.
4. Evaluation Methods
Accessibility conformance was evaluated using:
- Automated WCAG testing tools
- Manual keyboard-only and screen reader testing (VoiceOver, NVDA)
- Internal user testing with assistive technologies
- Conformance reviews guided by WCAG 2.1 and Section 508 standards
5. Contact for Accessibility Feedback
If you experience any difficulty using Kulpa or have suggestions for how we can improve accessibility, please let us know.
Email: Admin@kulpacloud.com
or
Raise a support request
We value your feedback and aim to respond as soon as possible.
6. Future Accessibility Plans
Kulpa is committed to achieving full WCAG 2.2 AA conformance and maintaining transparent accessibility reporting.
Our roadmap includes:
- Expanding screen reader coverage testing
- Adding captions and transcripts for all media content
- Regular accessibility audits before each major release
7. Legal Compliance References
Kulpa aligns with accessibility principles established under:
UK Equality Act 2010
Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 (where applicable)
U.S. Section 508 of the Rehabilitation Act
EU EN 301 549 accessibility framework
8. Compliance Status
Kulpa demonstrates strong alignment with accessibility standards.
Kulpa is actively working towards full WCAG 2.2 Level AA conformance and aligns with accessibility principles under the UK Equality Act 2010 and the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 where applicable.
9. Compliance Review
kulpa's accessibility compliance is reviewed at least annually, and in conjunction with our ISO270001 and BS10008 audits.
10. Compliance Status Checklist - WCAG 2.2
| No. | Title | Level | Plain-language summary | Compliance Status (Yes/No/Partial) |
|------|--------|--------|------------------------|------------------------------------|
| 1.1.1 | Non-text Content | A | All meaningful images, icons, and controls have text alternatives. | Partial |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Provide text or audio alternatives for media. | Partial |
| 1.2.2 | Captions (Prerecorded) | A | Prerecorded videos have captions. | Partial |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Provide audio description or text alternative for video. | Partial |
| 1.2.4 | Captions (Live) | AA | Live video has captions. | Partial |
| 1.2.5 | Audio Description (Prerecorded) | AA | Add audio descriptions for prerecorded video. | Partial |
| 1.3.1 | Info and Relationships | A | Structure and relationships are conveyed programmatically (headings, labels, etc.). | Yes |
| 1.3.2 | Meaningful Sequence | A | Reading and navigation order make sense. | Yes |
| 1.3.3 | Sensory Characteristics | A | Instructions don’t rely only on shape, size, color, or sound. | Yes |
| 1.3.4 | Orientation | AA | Supports both portrait and landscape display. | Partial |
| 1.3.5 | Identify Input Purpose | AA | Inputs that collect user info (e.g., name, email) identify their purpose in code. | Yes |
| 1.3.6 | Identify Purpose | AAA | Components, icons, and regions have programmatically defined purposes. | Yes |
| 1.4.1 | Use of Color | A | Color alone isn’t used to convey information. | Yes |
| 1.4.2 | Audio Control | A | Users can pause or stop audio. | Yes |
| 1.4.3 | Contrast (Minimum) | AA | Text contrast ≥ 4.5 : 1. | Yes |
| 1.4.4 | Resize Text | AA | Text can be zoomed 200 % without loss. | Yes |
| 1.4.5 | Images of Text | AA | Avoid using images of text unless essential. | Yes |
| 1.4.6 | Contrast (Enhanced) | AAA | Text contrast ≥ 7 : 1. | Yes |
| 1.4.7 | Low or No Background Audio | AAA | Audio backgrounds are low or removable. | Yes |
| 1.4.8 | Visual Presentation | AAA | Users can control text spacing and colors. | Yes |
| 1.4.9 | Images of Text (No Exception) | AAA | Images of text are never used. | Yes |
| 1.4.10 | Reflow | AA | Content reflows without horizontal scrolling up to 400 % zoom. | Yes |
| 1.4.11 | Non-text Contrast | AA | Icons, controls, and graphics meet contrast requirements. | Yes |
| 1.4.12 | Text Spacing | AA | Text remains readable when users adjust spacing. | Yes |
| 1.4.13 | Content on Hover or Focus | AA | Pop-ups and tooltips can be dismissed and are accessible. | Partial |
| 2.1.1 | Keyboard | A | All functionality is usable by keyboard. | Partial |
| 2.1.2 | No Keyboard Trap | A | Focus isn’t trapped inside components. | Yes |
| 2.1.4 | Character Key Shortcuts | A | Keyboard shortcuts can be turned off or remapped. | Partial |
| 2.2.1 | Timing Adjustable | A | Users can extend or disable time limits. | Yes |
| 2.2.2 | Pause, Stop, Hide | A | Moving or flashing content can be paused or hidden. | Yes |
| 2.2.3 | No Timing | AAA | No time limits unless essential. | Yes |
| 2.2.4 | Interruptions | AAA | Users can postpone interruptions. | Yes |
| 2.2.5 | Re-authenticating | AAA | Session data is preserved after re-login. | Yes |
| 2.3.1 | Three Flashes or Below Threshold | A | No content flashes more than three times / second. | Yes |
| 2.3.2 | Three Flashes | AAA | No flashes at all. | Partial |
| 2.4.1 | Bypass Blocks | A | Provide “skip to content” links or landmarks. | Partial |
| 2.4.2 | Page Titled | A | Pages have descriptive titles. | Yes |
| 2.4.3 | Focus Order | A | Tab order is logical. | Yes |
| 2.4.4 | Link Purpose (In Context) | A | Link text makes sense on its own. | Yes |
| 2.4.5 | Multiple Ways | AA | Offer more than one way to find pages (search, menu, etc.). | Yes |
| 2.4.6 | Headings and Labels | AA | Headings and labels describe topic or purpose. | Yes |
| 2.4.7 | Focus Visible | AA | Focus indicator is visible. | Partial |
| 2.4.8 | Location | AAA | Provide cues for user’s current location. | Yes |
| 2.4.9 | Link Purpose (Only) | AAA | Link text itself identifies purpose. | Yes |
| 2.4.10 | Section Headings | AAA | Use headings to organize content. | Yes |
| 2.4.11 | Focus Not Obscured (Minimum) **NEW** | AA | Focused elements aren’t hidden behind overlays or fixed headers. | Partial |
| 2.4.12 | Focus Not Obscured (Enhanced) **NEW** | AAA | No part of focused element is hidden. | Partial |
| 2.4.13 | Focus Appearance **NEW** | AA | Focus indicator is large enough and has sufficient contrast. | Partial |
| 2.5.1 | Pointer Gestures | A | Complex gestures have simple alternatives. | Partial |
| 2.5.2 | Pointer Cancellation | A | Actions can be canceled before completion. | Yes |
| 2.5.3 | Label in Name | A | Visible labels match accessible names. | Yes |
| 2.5.4 | Motion Actuation | A | Device motion inputs have alternatives. | Yes |
| 2.5.5 | Target Size | AAA | Targets are at least 44 × 44 px. | Yes |
| 2.5.6 | Concurrent Input Mechanisms | AAA | Support multiple input methods simultaneously. | Yes |
| 2.5.7 | Dragging Movements **NEW** | AA | Drag actions have simple click/tap alternatives. | Yes |
| 2.5.8 | Target Size (Minimum) **NEW** | AA | Targets are at least 24 × 24 px or sufficiently spaced. | Yes |
| 3.1.1 | Language of Page | A | The page language is defined in code. | Yes |
| 3.1.2 | Language of Parts | AA | Changes in language are marked in code. | Yes |
| 3.1.3 | Unusual Words | AAA | Define or explain unusual terms. | Yes |
| 3.1.4 | Abbreviations | AAA | Expand or define abbreviations. | Partial |
| 3.1.5 | Reading Level | AAA | Text is written at a lower-secondary reading level. | Partial |
| 3.1.6 | Pronunciation | AAA | Provide pronunciation guidance where needed. | Partial |
| 3.2.1 | On Focus | A | Focusing on elements doesn’t trigger unexpected changes. | Partial |
| 3.2.2 | On Input | A | Changing inputs doesn’t trigger unexpected context changes. | Yes |
| 3.2.3 | Consistent Navigation | AA | Navigation appears in a consistent order. | Yes |
| 3.2.4 | Consistent Identification | AA | Components with the same function are identified consistently. | Yes |
| 3.2.5 | Change on Request | AAA | Major context changes only happen on explicit user request. | Yes |
| 3.2.6 | Consistent Help **NEW** | A | Help options appear consistently across pages. | Yes |
| 3.3.1 | Error Identification | A | Input errors are identified and explained. | Yes |
| 3.3.2 | Labels or Instructions | A | Forms have clear labels and instructions. | Yes |
| 3.3.3 | Error Suggestion | AA | Suggestions for fixing input errors are provided. | Yes |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Users can review or correct before final submission. | Yes |
| 3.3.5 | Help | AAA | Context-sensitive help is available. | Yes |
| 3.3.6 | Error Prevention (All) | AAA | All submissions are reversible or confirmable. | Yes |
| 3.3.7 | Redundant Entry **NEW** | A | Users don’t need to re-enter previously provided data. | Yes |
| 3.3.8 | Accessible Authentication (Minimum) **NEW** | AA | Logins avoid cognitive tests; support password managers. | Yes |
| 3.3.9 | Accessible Authentication (Enhanced) **NEW** | AAA | No memory/cognitive tests required at all for authentication. | Yes |
| 4.1.1 | Parsing | A | Code uses proper syntax and structure. | Yes |
| 4.1.2 | Name, Role, Value | A | UI elements expose proper accessibility roles, states, and values. | Yes |
| 4.1.3 | Status Messages | AA | Status messages are announced to assistive tech without focus. | Partial |