Accessibility statement for a demonstration site of a fictitious entity

Demonstration build · entirely fictitious entity and data · built by Exec Logic Company

ALMUTAIRI Legal is an entirely fictitious entity, and this site is a static demonstration. There is no law firm behind it, no legal service is offered, and using it creates no relationship with a lawyer. It was built and is operated by Exec Logic Company as a technical demonstration. This page describes its accessibility: the level being aimed at, the measures actually in place, one known gap stated plainly, and how to report a problem to Exec Logic Company — and the closing section must give that operator's own address, never demo@almutairi.ai and never the contact form.

1. What this page describes

This statement describes how the demo was built so that it can be used with a screen reader, with the keyboard alone, with magnification, and across different display settings. It describes what is actually present in the repository's code. It is not a declaration of conformance.

The level being aimed at is WCAG 2.2 Level AA. The word aimed means that we design and test against it, not that we have attained it and demonstrated it.

Because this site is a demonstration of a fictitious entity, there is no law firm and no client-service team behind it. What follows is a technical description, not a service commitment.

2. Conformance status: a target, not a certificate

No independent third-party accessibility audit has been carried out on this demo. It holds no certificate, no accreditation, and no external review from any body.

This page should therefore not be read as a declaration of conformance with WCAG 2.2 Level AA or with any other standard. What we can honestly say is three things: this is the target, these are the measures in place, and this is the known gap.

Every sentence on this page describes technical behaviour that can be verified by reading the code and the tests in this repository.

3. Measures in place on every page

The site is a set of static pages. Every page declares its language and writing direction on the root element, and every page opens with a skip link to the main content that appears on the first press of the tab key.

Semantic landmarks are used throughout — a header, a main region, a footer, and navigation elements with descriptive names — together with an ordered heading structure, so that a screen reader can jump between sections instead of reading the page line by line.

Fonts are self-hosted under the SIL Open Font License, and nothing is loaded from an external content delivery network. Text therefore renders in its intended typeface without depending on a third party and without a network request leaving the site.

The light and dark theme switch keeps your preference in the browser's local storage. That value stays on your device, is sent nowhere, and carries no name or identifier.

4. Automated checks and build gates

An automated axe scan covers every page of the site within the end-to-end test suite, at a desktop viewport and a mobile viewport, using WCAG rules up to version 2.2 Level AA. Any violation fails the test.

Four browser configurations are defined: Chromium desktop, Chromium mobile, WebKit and Firefox. The axe scan and the WCAG 2.2 geometry checks run on the two Chromium configurations only; what runs on all four engines is the language-marking and 404 spec.

A colour-contrast gate reads the visual design tokens directly and fails the build if a colour used in a text role falls below the required threshold. It is a blocking gate: the build does not pass with a failing colour.

The Lighthouse accessibility category is asserted at a minimum score of 1.00; anything lower fails the check.

These are build gates that prevent regression, not conformance certificates. Automated tools detect only a limited class of defects, and their passing does not mean a page is free of barriers.

5. Language, and the language of parts

The site is served in three languages: Arabic right-to-left, and English and Simplified Chinese left-to-right. The three versions are linked by reciprocal hreflang references that declare, for each page, its counterparts in the other two languages. Because every page carries index,follow and robots.txt allows crawling, those references are a working discovery path that crawlers can follow, not merely declared structure in the code.

A change of language inside a page is marked: any Arabic text appearing on a non-Arabic page carries lang="ar" and a right-to-left direction, so that a screen reader pronounces it by Arabic rules rather than by the rules of the page language. WCAG success criterion 3.1.2 (Language of Parts) is what addresses this case.

6. A known gap: the services-guide answers are Arabic in every language

The services guide on this site is canned: it matches the words of your question against a fixed local table of answers written into the site's own script. No model is called, your text never leaves the browser, and the guide issues no legal opinion.

Its interface strings — the welcome message, the suggestions and the buttons — are translated into all three languages. The answer texts themselves are still in Arabic on the English and Chinese versions.

Those answers are correctly marked with lang="ar" and a right-to-left direction, so a screen reader pronounces them as proper Arabic. But correct marking is not translation: a reader who does not read Arabic hears correctly pronounced text they cannot understand. This is stated as an outstanding gap, not as a deliberate design.

7. What this page does not establish

Automated checking does not replace testing with real assistive technology. No documented testing sessions have been carried out on this demo with a screen reader, magnification, voice control or switch access, and no testing has been done with disabled users.

Whole classes of defect therefore remain unmeasured: whether the reading order makes sense when heard, whether alternative texts and accessible names are adequate in meaning rather than merely present, and whether a complete task can be finished smoothly with the keyboard alone.

The site collects no personal data. The contact form validates its fields inside the browser and then prints a local simulation message; it opens no channel and sends nothing to any server. We therefore hold no data about its visitors or about the assistive technology they use.

8. Reporting an accessibility problem

The developer and operator of this demo is Exec Logic Company. Report any accessibility barrier to wael@execraai.com.

A useful report includes the page address, what you were trying to do, your browser and operating system, and the assistive technology and version if you were using one.

The site's own channels cannot be used for this: the address demo@almutairi.ai shown on the contact page is fictitious and is not monitored, and the contact form sends nothing to anyone.

No response time is committed to on this page, because this is a demonstration with no support operation behind it.