Correct language and direction
Document language and direction change with Persian, English, German and Spanish so reading order and RTL/LTR layout remain predictable.
Document lang and dir
Accessibility at Mizi
Access belongs in the operating path—not at the end of the project.
This page makes the website’s target, implemented work, and current limitations explicit. We design toward WCAG 2.2 Level AA; that target is not yet a conformance claim or independent certification.
Design commitment
Four principles before any pattern or component.
We do not treat accessibility as a special mode. Structure, content, and interaction should begin usable across different ways of seeing, hearing, understanding, and operating.
- 01
Perceivable
Meaning does not rely on colour, imagery, or motion alone, and hierarchy and contrast should survive either theme.
- 02
Operable
Primary journeys should work with keyboard, touch, and pointer, without losing the current focus position.
- 03
Understandable
Labels, errors, and capability boundaries should be clear before action, without needlessly losing entered information.
- 04
Robust
Semantic HTML, accessible names, and announced state form the baseline for assistive-technology support.
What exists on this website today
Access should be visible in interface behaviour.
These foundations are implemented in the current website. They are not a guarantee of complete coverage until manual and assistive-technology testing is finished.
Keyboard and focus
Skip navigation, visible focus, Escape dismissal, and focus containment in mobile navigation are included.
A path without a mouse
Motion by preference
When reduced motion is requested, smooth scrolling and decorative transitions are effectively removed.
prefers-reduced-motion
Explainable forms
Inputs have labels, errors stay with their stage, and walkthrough data is preserved while editing.
Labels, errors, persistence
Semantic structure
Headings, navigation, main content, lists, and tables use semantic elements to support navigation.
Navigable structure
Two themes, one meaning
Light and dark colours share design tokens so meaning does not change when the theme does.
Light, dark, and contrast
Current review matrix
What we test should be possible to name.
This is the scope of internal review. “In progress” is not final approval or compatibility with every browser and assistive-technology combination.
JourneyReview methodState
Global navigation and mobile menu
Keyboard only, Escape, focus order, and skip navigation
In progress
Tailored walkthrough form
Labels, staged errors, data persistence, and result announcement
In progress
Persian, English, German and Spanish
Reading order, interface direction, numerals, and RTL/LTR alignment
In progress
Light and dark themes
Text, control, and focus contrast; meaning without colour alone
In progress
Zoom and narrow viewport
200% zoom, 320px viewport, and reflow without unintended horizontal scrolling
In progress
Reduced-motion preference
Non-essential movement removed without hiding state or content
In progress
Formal screen-reader testing and an independent audit are not yet recorded, so this page is not a conformance certificate.
Known limitations
We do not call unproven coverage complete.
This list changes with the product. Each item should close with evidence or remain visible until it is corrected.
Assistive-technology coverage
A formal VoiceOver, TalkBack, and desktop screen-reader matrix has not yet been completed and documented.
Product interface images
Some illustrative captures may contain small text; nearby copy must communicate the core point independently.
Public barrier-report destination
The owner and secure public destination are not yet approved. Pilot users should use the agreed channel for their project.
Independent audit
A third-party audit and formal conformance statement have not been completed and should not be inferred from this page.
Report a barrier
You do not need specialist language to make a useful report.
Tell us where you were, what you wanted to do, and what got in the way. Do not include unnecessary medical or personal information.
Current reporting route
If you are part of an active pilot, send the report through the support route agreed for that project so its owner and deployment context remain clear.
No public email or receiving form is published yet. Until an owner is approved, this website does not transmit your report or personal data.
What makes a barrier report actionable?
Keep this template locally and send it through your project’s trusted route.
- Page address or name
- What you were trying to do
- What happened instead
- Device and browser
- Assistive technology, if you choose
- Preferred contact route, only in a secure channel
Ownership and review
This statement is living work—not a permanent badge.
Material interface changes should include keyboard, language, theme, and motion review. A conformance claim will only be published after ownership is assigned, the test method is recorded, and high-severity barriers are resolved.
Content last reviewed: 1 September 2026Next review: after manual audit completion and approval of the public reporting route