CloudEffects

Accessibility

How far cloudeffects.com and the OS iXanagi console conform to WCAG 2.2 Level AA today, what we know does not conform yet, and how to tell us when something is in your way.

Contents7 chapters

Our commitment

Last updated: 2026-10-20

CloudEffects LLC wants everyone who runs a business on OS iXanagi, and everyone who reads cloudeffects.com, to be able to do so regardless of ability or the assistive technology they use. We work toward the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C, for the public website at cloudeffects.com and for the OS iXanagi Platform Console that customers sign in to.

We treat accessibility as part of building the product, not as a document: findings are fixed in the shared theme and shell so that a fix reaches every page and every screen at once.

Conformance status

Partially conformant. "Partially conformant" means that some parts of the content do not yet fully conform to WCAG 2.2 Level AA.

This status is a self-assessment. We have not yet commissioned an evaluation by an external accessibility body; the cost of such an evaluation is not justified at our current size, so we are instead fixing what we can find ourselves and publishing the results here. We will update this page when that changes.

The status applies to:

  • cloudeffects.com (the public website, English and Japanese)
  • the OS iXanagi Platform Console (the signed-in product)

It does not apply to websites that customers build and publish with OS iXanagi: each customer is responsible for the accessibility of their own content, though the shared theme and page templates are built to the same guidelines.

How we assessed it

In October 2026 we measured both surfaces with automated testing (axe-core 4.11 run through Playwright against every WCAG 2.0, 2.1 and 2.2 Level A and AA rule it covers) on 21 public pages and 30 console screens, with keyboard-only navigation checks, a 320-pixel-wide reflow check, and a review of the source code for the things automated tools cannot see: landmarks, heading levels, labels, focus handling, drag-and-drop alternatives and the language of interface text.

Automated testing finds only part of what WCAG covers. We have not yet tested with screen readers (VoiceOver, NVDA) or with users of assistive technology, and we say so below rather than claim a result we do not have.

What we fixed

From the October 2026 assessment, the following were corrected before this page was published.

Public website: text colors that fell below the 4.5:1 contrast minimum (footer headings, dates, table-of-contents numbers, the "required" marker on forms); touch targets smaller than 24 by 24 pixels (carousel dots, footer accordions, card links, the consent checkbox); heading levels that skipped a step; unnamed navigation landmarks; an invalid ARIA role on article summaries; English-only labels on the Japanese site; and a carousel that could not be reached with the keyboard.

Platform Console: every screen now has a header, navigation and main landmark, a "skip to content" link, a level-one heading and its own page title; a visible focus indicator on every button and link; input fields with a visible border and a focus ring that meets 3:1; icon buttons with an accessible name; form fields and table checkboxes with labels; clickable cards that can be operated with the keyboard; and browser autofill re-enabled on form fields. The warning color of status labels, the sidebar list structure and the heading hierarchy have also been corrected.

Known non-accessible content

The following is known not to conform yet. Each item names the WCAG success criterion involved.

Public website

  • Text placed over photographs: contrast cannot be verified by tools and has only been checked by eye on the home page (1.4.3 Contrast).
  • A small number of data tables in page content have an empty header cell (1.3.1 Info and Relationships).
  • Opening the mobile menu does not move keyboard focus into it; the menu closes with the Escape key (2.4.3 Focus Order).
  • Enlarging text to 200% and adjusting text spacing have not been verified (1.4.4 Resize Text, 1.4.12 Text Spacing).

Platform Console

  • Reordering layers in the page designer and rearranging dashboard widgets is drag-and-drop only; a keyboard alternative is being added (2.5.7 Dragging Movements).
  • In the knowledge graph, nodes and edges are smaller than the 24-pixel minimum and are not individually reachable by keyboard (2.5.8 Target Size, 2.1.1 Keyboard).
  • Confirmation messages disappear automatically after a few seconds; the underlying state remains visible on the screen (2.2.1 Timing Adjustable).
  • Behaviour with screen readers has not been verified.

Feedback

If something on cloudeffects.com or in the OS iXanagi console is in your way, tell us at official@cloudeffects.com with "Accessibility" in the subject line. Please include the page or screen, what you were trying to do, and the browser and assistive technology you were using. We reply within five business days and, where we can, tell you the workaround while a fix is on its way.

If you need any of our legal documents in another format, ask at the same address.

Technical notes

The public website is server-rendered HTML with CSS and a small amount of JavaScript; it reads without JavaScript. The Platform Console is a web application that requires JavaScript and is built on the MUI component library with WAI-ARIA roles and properties. Both respect the operating system's "reduce motion" setting and reflow to a 320-pixel-wide viewport without horizontal scrolling.

This page was first published on 2026-10-20 and is reviewed whenever we re-run the assessment described above.