The latest in web accessibility and digital regulations
Guides on WCAG, e-commerce, WordPress, WooCommerce and European legal compliance.
Accessibility ≠ Overlay: accessibility is designed and developed from the start
Accessibility ≠ Overlay: accessibility is designed and developed from the start📅 Octubre 2026 ⏱ 10 minW3C recomienda integrar la accesibilidad durante todo el proceso de producción web, no tratarla como una reparación que se añade cuando el producto...
Accessibility ≠ Overlay: accessibility is designed and developed from the start
Accessibility ≠ Overlay: accessibility is designed and developed from the start📅 Octubre 2026 ⏱ 10 minW3C recomienda integrar la accesibilidad durante todo el proceso de producción web, no tratarla como una reparación que se añade cuando el producto...
Accessibility ≠ Overlay: an automated 100/100 does not mean WCAG conformance
Accessibility ≠ Overlay: an automated 100/100 does not mean WCAG conformance📅 October 2026 ⏱ 9 minA perfect score can be a useful signal, but it describes the checks run by that tool and how they are weighted. In Lighthouse, the accessibility score is...
Accessibility ≠ Overlay: an automated tool does not replace a real audit
Accessibility ≠ Overlay: an automated tool does not replace a real audit📅 September 2026 ⏱ 9 min readAutomated tools can find certain accessibility issues quickly, repeatedly and at scale. W3C says they can save time and effort, but is also explicit:...
Accessibility ≠ Overlay: ARIA does not magically fix poorly built HTML
Accessibility ≠ Overlay: ARIA does not magically fix poorly built HTML📅 September 2026 ⏱ 9 min readAfter semantic HTML comes a common misconception: adding ARIA attributes does not automatically turn a poorly built component into an accessible one....
Accessibility ≠ Overlay: semantic HTML, the foundation an overlay cannot replace
Accessibility ≠ Overlay: semantic HTML, the foundation an overlay cannot replace📅 September 2026 ⏱ 9 min readA site can look perfectly organised and still be confusing to someone using a screen reader, keyboard or other assistive technology. The...
Accessibility ≠ Overlay: “My website has an accessibility button. Is it accessible?”
Accessibility ≠ Overlay: “My website has an accessibility button. Is it accessible?”📅 September 2026 ⏱ 8 min readA common question is: “I installed an accessibility button or widget. Is my website accessible now?” The answer cannot be determined by...
Accessibility ≠ Overlay: an accessibility menu does not make a website accessible
Accessibility ≠ Overlay: an accessibility menu does not make a website accessible📅 September 2026 ⏱ 8 min readA website does not become accessible because an icon appears in a corner. Larger text, colour changes or text-to-speech can be useful, but...
Accessibility ≠ Overlay: privacy, data and third-party layers
Accessibility ≠ Overlay: privacy, data and third-party layers📅 September 2026 ⏱ 8 min readAdding a third-party service is not only an accessibility decision; it can also be a data decision. An overlay may load external code, store preferences or...
Accessibility ≠ Overlay: Respecting User Preferences
Accessibility ≠ Overlay: respecting user preferences📅 September 2026 ⏱ 8 min readA person may already have configured their computer, browser, or assistive technology to use a particular text size, reduce motion, use specific colors, or navigate in a...









