A website for more people.
How WahabDev approaches accessible content and interfaces, known limits and the best way to report an accessibility problem.
Ask a question →What we aim for
We aim to create a website that supports readable content, keyboard navigation, useful alternative text, sensible heading structure, responsive pages and reduced-motion preferences. We use the WCAG 2.2 AA guidelines as a design goal, not a certification of conformance.
Things already supported
The site has a skip-to-content link, descriptive links, page headings, visible focus treatments, and viewport-responsive layouts. Navigation menus and interactive galleries should remain usable with a keyboard.
Known limitations
Some client-project screenshots and third-party embedded websites contain content outside WahabDev’s control. Legacy sliders and interactive sections may still require additional assistive-technology testing. We have not completed a formal independent accessibility audit.
Report an issue
If an interface is difficult to use, email a description of the page, browser, device and issue. We will review accessibility feedback and seek a practical solution; no guaranteed response time is advertised.
Ongoing improvement
Accessibility is ongoing. Changes to templates, plugins and content should be checked again, especially after deployment.
Questions deserve clear answers.
If you need further details about these policies, your project or the plugins, get in touch.