ACCESIBILIDAD ≠ OVERLAY · 26

Accessibility ≠ Overlay: when a pop-up blocks access

📅 October 2026   ·   ⏱ 7 min read

A pop-up can be useful, but when it interrupts a task or cannot be dismissed, it becomes a barrier.

01. The problem

A pop-up can be useful, but when it interrupts a task or cannot be dismissed, it becomes a barrier.

02. Not all dialogs are alike

Not every dialog is the same. A truly modal dialog prevents interaction with the background while open, so focus management matters. A non-modal notice should not unnecessarily block the page.

03. Common barriers

Common failures include unexpected openings, unlabelled close buttons, lost focus, an Escape key that does nothing, and forms obscured by the dialog.

04. Managing focus

When a modal opens, focus should move inside it. Tab and Shift+Tab should remain within the active dialog, and focus should normally return to its trigger when it closes. Assistive technologies need accurate modal semantics.

05. Must they be optional?

Not every pop-up must be optional: an essential confirmation may require attention. The interruption should be justified, understandable and compatible with completing the task.

06. Why an overlay is not enough

An accessibility overlay does not automatically fix broken dialog code. Changing colours or font sizes cannot create a working close control or repair focus order.

07. How to test

Test with a keyboard: open the dialog, identify its title, navigate its controls, close it and check where focus lands. Repeat with a screen reader, zoom and mobile.

08. Conclusion

Real accessibility means building components that people can understand and operate without being blocked.

♿ Accesibilidad ≠ Overlay · 26

Adapta tu Web