Trust & Compliance

Accessibility Statement

Where our website and client area stand against WCAG 2.1 Level AA, what we have done, what remains limited, and how to tell us about a barrier.

Last updated: 29 October 2026 Applies to all Luveedu Cloud services
Accessibility Statement

Luveedu Cloud · Wenxenith Technologies LLP · Last updated 29 October 2026 · luveedu.cloud

This statement describes the accessibility of the Luveedu Cloud website, the client area at manager.luveedu.cloud, and the public documentation that we publish. It explains the standard we are working towards, the measures already in place, the limitations that remain, and the route for feedback or escalation.

We publish this statement because accessibility is a practical requirement for our customers, not a marketing exercise. It describes our position honestly. It does not claim full conformance, and it does not create a warranty that every page will be usable by every person with every assistive technology.

1.Our Commitment

We intend the website and the client area to be usable by people with a wide range of abilities and access needs, including people who use screen readers, magnification, keyboard-only navigation, speech input, or a combination of methods. Accessibility is treated as part of the quality of the interface, alongside security, performance, and clarity of content.

Our commitment covers the public website, the sign-in and account management flows, the support interface, and the documentation that we publish. It extends to the content that we author and to the templates that we control. It does not extend to customer websites, to applications that a customer installs, or to content that a customer publishes.

We accept that accessibility work is continuous. Interfaces change, browsers change, assistive technology changes, and a page that was usable last year may develop a barrier after a redesign. We therefore review the interface at defined intervals and treat an accessibility report as a defect to be assessed, prioritised, and corrected where feasible.

Accessibility is funded and scheduled like any other engineering obligation. It is not dependent on a single member of staff, and it is not treated as a one-off project that ends when a checklist has been completed.

2.Conformance Status

Our target is Level AA conformance with the Web Content Accessibility Guidelines, version 2.1, published by the World Wide Web Consortium. We use that standard because it is widely recognised, testable, and supported by common accessibility tooling.

The website and client area are partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the content do not fully conform to the standard. We do not describe the site as fully conformant, and we do not describe it as substantially conformant where a known limitation remains in a core flow.

Some legacy content may not fully conform. This includes pages and documents created before our current design system was adopted, archived policy versions, older help articles, and material that was migrated from a previous platform without a full content audit. Legacy content is corrected or replaced when it is edited, and pages in regular use are prioritised over archive material.

This statement is a self-assessment. It is not an independent audit, it is not a certification, and it should not be read as a claim that an external body has verified conformance. Where an independent assessment is carried out, we will describe its scope and its result in this statement.

3.Measures We Have Taken

The following measures are in place across the website and the client area. Each is intended to remove a specific barrier rather than to satisfy a checklist in isolation.

  • Semantic HTML - pages use headings in a logical order, landmarks for navigation and main content, and lists where the content is a list, so that a screen reader can build an accurate outline.
  • Keyboard navigation - interactive elements can be reached and operated with a keyboard, and the tab order follows the visual order of the page.
  • Visible focus states - the element that currently has focus is indicated by a visible outline, so that a keyboard user can track position on the page.
  • Contrast - text and interface controls are designed to meet the contrast ratios in the standard, and contrast is checked when a colour token is introduced or changed.
  • Responsive layout - content reflows on narrow viewports and at high zoom levels without a horizontal scroll for reading, and without loss of function.
  • Form labels - inputs have associated labels, required fields are identified in text, and an error is described in text rather than by colour alone.
  • Reduced motion - animation and reveal effects are reduced or removed where the operating system reports a preference for reduced motion.
  • Icon alternatives - an icon that carries meaning has an accessible name, and a decorative icon is hidden from assistive technology so that it is not announced without purpose.

These measures are maintained through the shared templates and the design tokens that the site uses. A new page inherits them, which is why we require new pages to use the established layout rather than a bespoke structure.

4.Known Limitations

We would rather describe a known barrier than allow a visitor to discover it without explanation. The following limitations are known at the date of this statement.

  • Third-party embedded content - a small number of pages embed a third-party tool, such as a payment form, a chat widget, or a network map. The accessibility of that content depends on the provider, and we cannot guarantee its behaviour with every assistive technology.
  • Legacy documents - some older PDF documents and policy downloads were not produced with a tagged structure. They may be difficult to navigate with a screen reader, and they may not reflow at high zoom.
  • User-generated screenshots - support tickets and knowledge articles may contain screenshots supplied by a customer or by staff. An image of this kind may lack a text alternative where the content was not authored by us.
  • Areas under active remediation - parts of the client area, particularly older billing and domain management screens, are being rebuilt in the current design system. Until that work is complete, some controls in those screens may have an inconsistent focus order or an incomplete label.

Where a limitation prevents a person from completing an essential task, we will provide an alternative route on request. That may be a telephone call, an email exchange, or a manually processed order. The alternative route is described in Chapter 6.

This list is reviewed at each assessment cycle. A limitation is removed from the list when the underlying issue has been corrected and verified, not when a work item has merely been opened.

5.Compatibility

The website and client area are designed for current versions of the major browsers, including Chrome, Firefox, Safari, and Edge, on desktop and mobile operating systems. We test against the current release and the preceding major release of each browser. A browser that no longer receives security updates from its vendor is not supported.

We test with common screen readers, including NVDA with Firefox and Chrome on Windows, JAWS with Chrome on Windows, and VoiceOver with Safari on macOS and iOS. We also test with operating system magnification and with browser zoom at 200 percent and 400 percent.

Content is expected to reflow at a viewport width equivalent to 320 CSS pixels without a loss of information or function, and text is expected to remain readable when it is enlarged. Mobile layouts are tested on a small handset and on a tablet, in both portrait and landscape orientation.

The interface does not rely on a single input method. A task that can be completed with a mouse can also be completed with a keyboard, and no task requires a gesture that has no keyboard equivalent. Where a drag interaction exists, an alternative control is provided.

6.Feedback and Assistance

If you encounter a barrier, please tell us at [email protected]. We welcome reports about a page that is difficult to use, a control that cannot be reached by keyboard, a label that a screen reader does not announce, or content that does not reflow at high zoom.

A useful report includes the address of the page, the task you were attempting, the browser and operating system, the assistive technology and version, and a description of what happened. A screenshot is helpful but not essential. If you prefer, you may describe the issue by telephone or request a call back, and we will arrange one during our normal business hours.

We will acknowledge accessibility feedback within 5 Business Days. We will explain what we have understood, whether we can reproduce the barrier, and what we propose to do. Where a workaround exists, we will describe it. Where the barrier blocks an essential task, we will offer an alternative format or a direct assistance route while a fix is developed.

Alternative formats are available on request. This includes a policy document in plain text, in a larger font, or in a tagged format suitable for a screen reader. Please tell us which format you need and we will provide it within a reasonable period, normally within 10 Business Days.

7.Assessment Approach

Accessibility is assessed through a combination of internal review, automated checks, and manual testing. Each method finds a different category of issue, and none of them is sufficient on its own.

  • Internal review - a member of the team reviews a page or a flow against the standard, records each issue, and assigns an owner and a priority.
  • Automated checks - tooling is used to detect contrast failures, missing labels, missing alternative text, duplicate identifiers, and invalid structure. Automated results are treated as a starting point, not as evidence of conformance.
  • Manual testing - a person navigates the interface with a keyboard and with a screen reader, checks focus order and focus visibility, enlarges text, and confirms that a task can be completed without a mouse.
  • Review cadence - a full review is carried out at least once every 12 months, and an incremental review is carried out whenever a shared template, a navigation element, or a form component is changed.

Findings are recorded in the same tracking system as other defects. A finding that blocks a core task, such as signing in, paying an invoice, or opening a support ticket, is prioritised above a cosmetic issue in archive content. Where a fix depends on a third-party provider, we record that dependency and follow up with the provider.

The outcome of an assessment is used to update this statement. Where a limitation has been corrected, it is removed. Where a new limitation is identified, it is added with a description that a reader can understand.

8.Enforcement and Escalation

We ask that a barrier be reported to us first, so that we have the opportunity to correct it. A report sent to [email protected] is recorded, acknowledged, and assigned to an owner.

We aim to resolve a reported barrier within 30 days where a resolution is feasible. Where a fix requires a redesign, a migration, or a change by a third party, the period may be longer. In that case we will explain the constraint, provide a workaround where one exists, and give an expected date for the change.

If you are not satisfied with the response, you may ask for the matter to be escalated. An escalation is reviewed by a more senior member of the team, who will consider the original report, the response given, and any alternative route offered. We will provide a written outcome within 30 days of the escalation request.

Nothing in this Chapter limits a right that you have under applicable law, including a right to complain to a consumer protection body or to another competent authority. Where a statutory remedy is available, this statement does not replace it, and an internal escalation is not a precondition to exercising it.

9.Continuous Improvement

Our accessibility work follows a rolling plan rather than a fixed end date. The plan gives priority to the flows that a customer must complete in order to use a service, and to the components that appear on the largest number of pages.

Current priorities include the completion of the client area rebuild in the current design system, the replacement of untagged legacy documents with structured versions, the review of focus management in modal dialogs and multi-step forms, and the improvement of error messaging so that every error is described in text and associated with the field it concerns.

We also intend to strengthen the accessibility requirements applied at the design stage, so that a component is reviewed before it is built rather than after it is released. This reduces the number of defects that reach a customer and makes remediation cheaper and more reliable.

Progress is reported internally at each review cycle and is reflected in this statement. We do not publish a dated roadmap, because a date that cannot be met creates a commitment that we should not make. We do publish the direction of travel and the areas that are currently being addressed.

10.Contact

Accessibility feedback, requests for an alternative format, and escalation requests should be sent to [email protected]. General service questions should be sent to [email protected], which is the correct channel for account and technical support.

Our postal address is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India. The entity responsible for the website and client area described in this statement is Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud.

We acknowledge accessibility feedback within 5 Business Days and aim to resolve a reported barrier within 30 days where feasible. Where a barrier cannot be resolved within that period, we will explain why and provide an alternative route in the meantime.

This statement is governed by the laws of India, and the courts of Tripura have exclusive jurisdiction in respect of any dispute connected with it, subject to any right that cannot be excluded by agreement.

Grievance Redressal

Grievance Officer

Wenxenith Technologies LLP has appointed a Grievance Officer for complaints and notices under this policy. He acts independently of our sales and support teams, and there is no charge to raise a grievance.

Email the Grievance Officer at [email protected]
Include your account email, the policy concerned, and any reference number
Expect an acknowledgement within 48 hours
We provide a written outcome within 30 days
Technical support remains available at [email protected]
Designated Grievance Officer
Shyamal Debnath
Grievance Officer
[email protected]
+91 7641818218
Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India
We acknowledge every grievance within 48 hours and aim to resolve it within 30 days.