The latest in web accessibility and digital regulations
Guides on WCAG, e-commerce, WordPress, WooCommerce and European legal compliance.
Accessibility ≠ Overlay: when a pop-up blocks access
ACCESIBILIDAD ≠ OVERLAY · 26Accessibility ≠ Overlay: when a pop-up blocks access📅 October 2026 · ⏱ 7 min readA pop-up can be useful, but when it interrupts a task or cannot be dismissed, it becomes a barrier.01. The problemA pop-up can be useful, but...
Accessibility ≠ Overlay: when a modal dialog blocks keyboard navigation
Accessibility ≠ Overlay: when a modal dialog blocks keyboard navigation📅 October 2026 ⏱ 6 min readA pop-up dialog can help someone confirm a purchase, sign in or read important information. But poor focus and keyboard handling can stop them completing...
Accessibility ≠ Overlay: when a cookie banner becomes a barrier
Accessibility ≠ Overlay: when a cookie banner becomes a barrier📅 October 2026 ⏱ 5 min readA cookie notice should allow everyone to make an informed choice. If keyboard or screen-reader users cannot operate it, a privacy decision becomes an...
Accessibility ≠ Overlay: When a form cannot be completed with a screen reader
Accessibility ≠ Overlay: when a form cannot be completed with a screen reader📅 October 2026 ⏱ 7 min readAn accessible form is more than a collection of fields. Everyone should be able to understand it, fill it in, review their answers and submit it...
Accessibility ≠ Overlay: When a CAPTCHA prevents access to a website
Accessibility ≠ Overlay: when a CAPTCHA blocks access to a website📅 October 2026 ⏱ 7 min readA CAPTCHA may protect a form against abuse, but it can also become a locked door. Security should work without forcing people to pass tests they cannot...
Accessibility ≠ Overlay: Blind Reader, an intelligent assistant that improves web accessibility
Accessibility ≠ Overlay: Blind Reader, an intelligent assistant that improves web accessibility📅 October 2026 ⏱ 10 min readBlind Reader improves web accessibility through contextual guidance, assisted navigation, voice commands and automatic fixes for...
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....









