World Web Certified aims to support reading across different screens, navigation methods and assistive technologies. This page describes measures already in place without claiming conformity that has not been independently audited.
A text alternative depends on what the image contributes. Appearance alone is insufficient when it acts as a button or conveys data.
| Situation | What changes | Useful check |
|---|---|---|
| Informative image | Convey the essential information in context. | Do not unnecessarily repeat a nearby caption. |
| Functional image | Name the action or destination. | A button should announce its purpose, not just its icon’s shape. |
| Complex chart | Provide a complete equivalent of useful data or relationships. | Supply a description and, where appropriate, a readable table. |
An empty alt attribute avoids announcing a purely decorative image. Read the page without images: essential actions and information should remain identifiable.
Documentation : W3C WAI — Images Tutorial ↗ · · Read the reference record →
A useful statement explains measures actually present, known limitations, the assessment approach and a simple way to request help. It does not turn self-evaluation into certification.
Editorial review
Publication director: Vincent Ferrer. Webmaster / Domain name owner: Alexis RZG.
Accessibility applies to the main portal, navigation, insights and selection records. Visitors should be able to understand content, reach important links and report a barrier without depending solely on visual presentation.
External websites reached through the directory have their own structures and responsibilities. Inclusion in the selection does not mean World Web Certified has validated the accessibility of all their pages.
The portal uses a heading structure, a skip link to the main content, labelled navigation, visible focus states and keyboard-operable controls. Layouts adapt to narrow screens, and essential information does not rely solely on colour or imagery.
Selection screenshots are accompanied by the project name, a description and a text link. They support the record but are not required to understand the destination.
Pages rely on HTML, CSS and a limited amount of JavaScript for the menu and selection search. Primary editorial content remains in the HTML document and does not require dynamic loading to be read.
A recent browser improves presentation, while core information should remain available when motion is reduced, images do not load or JavaScript is unavailable.
This statement currently rests on technical and editorial self-evaluation, not a complete audit involving several assistive technologies and user profiles. We therefore make no formal WCAG conformance claim.
Long selection pages and some screenshots may require additional navigation. The integrated search reduces that length, while insights provide a contents section for direct access to individual topics.
If an element is difficult to read, reach, understand or operate, include the exact page address, the intended action and the problem encountered. Mentioning the browser or assistive technology can help, but no sensitive data is needed.
Write to contact@worldwebcertified.com or use the contact page. A response may involve a correction, an explanation or an accessible alternative.
Links, buttons, search fields and disclosure summaries should receive focus in a coherent order. A visible outline identifies the active element, while Escape closes the mobile menu or clears a search containing text.
Insight contents use internal links to identified headings. Back-to-top and skip links reduce repeated navigation.
Future changes should preserve these landmarks instead of requiring hover or touch gestures alone.
Text uses distinct contrast, adaptable widths and sizes that respond to the screen. Important links have textual labels, and decorative elements are hidden from assistive technologies when they convey no information.
The system preference for reduced motion disables smooth scrolling and shortens transitions. A simplified print mode removes navigation so the useful content remains.
Browser zoom should enlarge the page without causing horizontal scrolling on a narrow screen.
Current checks cover HTML structure, heading order, labels, identifiers, keyboard navigation, responsive behaviour and horizontal overflow at common viewport sizes.
Technical checks do not reproduce every lived situation. User feedback, assistive-technology testing and a future specialist audit may expose barriers that automated review cannot see.
Each reproducible issue should feed maintenance of the underlying component so the correction benefits every page that uses it.
Provide the page, task, steps and observed outcome. Mention browser, zoom or assistive technology when relevant to reproduction. A screenshot supports a text description; remove personal details.
Read our guide to reporting an accessibility barrier and its checklist. For a time-sensitive task, also ask for an alternative way to proceed.
Accessibility improves when technical decisions remain assessable and visitors have a human contact for describing a specific barrier. World Web Certified would rather document and correct a limitation than publish an absolute claim it cannot guarantee.
Report a correction ↗