Accessibility Statement

Last reviewed May 2026.

The Intermenu platform — including the blog you’re reading — targets WCAG 2.2 Level AA. This statement explains where we stand, what we test, and how to reach us if you encounter a barrier.

What we’ve done

Semantic HTML across every blog page: <article>, <header>, <main>, <nav>, <aside>, <footer>. A skip-to-content link is the first focusable element on every page.
Alt text required at the editor level — admins cannot save an image without one.
Keyboard accessible interactive elements with visible focus rings.
Colour contrast meets WCAG AA: 4.5:1 for body text, 3:1 for large text.
Reduced motion respected via prefers-reduced-motion on every animation we ship.
RTL layout for Arabic and Hebrew, mirrored and tested visually for tables, blockquotes, and list rhythm.
Reading aids: an in-page table of contents and the browser's native zoom + reader-mode are honoured (no overrides on font-size or line-height).

What we test

Our deploy pipeline runs automated accessibility checks (axe-core / pa11y) against the post template, the blog home, and the search page. New violations block the deploy. We supplement this with manual screen-reader testing on representative posts each month and a quarterly audit by a third party.

Reach us

Encountered a barrier? Email info@ibramdawwa-gmbh.de. Tell us the URL, the assistive technology you’re using, and what failed. We aim to respond within five business days and to fix the issue or document a workaround within ten.