Accessibility statement

clearrecharge aims for WCAG 2.1 AA on every public page. This statement lists what is done, what is known to be off, and how to write in about a barrier we did not think of.

What is in place

• Semantic HTML — header, main, nav, article, section, footer — with visible landmarks.
• Every interactive control reachable and operable from a keyboard, with a visible focus ring.
• Text contrast at 4.5:1 or higher on body copy; 3:1 or higher on large headings.
• Form labels are always visible; hints and errors are announced via aria-live.
• Motion respects prefers-reduced-motion: the mouse trail, hero pulses and confetti stop when the OS asks for less motion.
• Language attribute set on html; a full mirror in Arabic lives at /ar/ with dir="rtl".
• Zooming to 200% does not break the layout on any page.

Known gaps

• The OpenStreetMap iframe on About and Contact uses upstream markup we cannot rewrite; it may not narrate cleanly on every screen reader.
• The custom cursor-trail is decorative and can be visually distracting; it is disabled on touch devices and with reduced motion.

Write in about a barrier

If you hit something we missed, please tell us at [email protected]. Attach a screenshot or a short description of the browser and assistive tech you used. The workshop replies during Dubai working hours.