A visitor arrives at a website to do something. Read an article. Find a service. The interface should help that intent move forward. Instead, the first few seconds can become a negotiation with the interface itself. A cookie notice appears. A chatbot opens in the corner. A newsletter offer slides over the content. An accessibility control sits nearby. A location prompt asks for permission. A promotional banner takes over the top of the page. On mobile, several of those elements may compete for the same few inches of screen.
None of these elements is necessarily the problem on its own. The problem is accumulation.
The website has acquired a second interface
For years, digital teams have worked to simplify navigation, reduce friction, clarify hierarchy, and make websites easier to use. At the same time, a growing collection of notices, tools, prompts, and conversion mechanisms has been layered on top of the experience.
Some support privacy choices. Some are intended to improve access or provide assistance. Others come from marketing, analytics, customer service, or sales. Each may have a legitimate business purpose. But visitors do not experience them as separate departmental decisions. They experience one website.
A privacy team may see a consent mechanism. Marketing may see a lead-generation prompt. Customer service may see a chatbot. The visitor sees four things asking for attention before the page has had a chance to answer the reason they came.
Good intentions can still create poor hierarchy
Interface hierarchy is fundamentally about priority.
- What needs attention now?
- What can wait?
- What belongs in the background until a person asks for it?
When several systems are implemented independently, they often behave as though each one has first priority. A modal centers itself. A chat bubble animates. A banner stays fixed. A promotional message interrupts. The page underneath may be carefully designed, but its hierarchy is being rewritten by components that were never designed together.
This is where the issue becomes a UX problem rather than a debate about any individual tool. The question is not whether a particular feature should exist. The design question is how all of those features coexist without obscuring the primary experience.
Accessibility belongs in the experience, not beside it
Accessibility makes the same point particularly well. An accessible experience is strongest when accessibility is considered throughout structure, content, interaction, visual design, and development. A visible control or third-party tool may serve a specific function, but the presence of an interface element should not be confused with the accessibility of the underlying experience.
The more useful design question is whether the website itself works well across different ways of seeing, navigating, understanding, and interacting with content. That shifts attention from the presence of a badge or control to the quality of the system underneath it.
Privacy can be designed with the same care as the rest of the site
Privacy choices also deserve thoughtful interface design. Requirements and implementation choices vary by organization, technology, audience, and jurisdiction, so legal and privacy teams should determine what a particular site needs. The design team still has an important role: making the resulting experience understandable, proportionate, and consistent with the rest of the interface.
A notice does not have to visually dominate the page simply because it is important. Clear language, sensible timing, appropriate emphasis, and well-considered controls can help people make choices without turning every arrival into an obstacle course.
Design the stack, not just the page
The practical problem is that many teams still review these elements one at a time. The web design is approved first. Then analytics is added. Then consent. Then chat. Then a campaign pop-up. Then another service introduces its own launcher. Months later, nobody can quite explain why three floating controls occupy the lower-right corner.
A better approach is to treat the entire interface stack as part of the design system. Inventory every persistent, conditional, and interruptive element. Decide which one has priority. Define where each can appear, when it can open, how it behaves on small screens, and what happens when two systems want the same space.
Most importantly, test the assembled experience rather than evaluating each component in isolation. A component can work exactly as intended and still make the overall website harder to use.
The next UX problem is attention governance
Modern websites are no longer composed only of pages and navigation. They are collections of systems competing for a limited resource: human attention.
That makes attention governance an increasingly important part of digital design. Someone has to decide what gets to interrupt, what remains available without demanding attention, and what should disappear entirely. Those decisions cannot be left to whichever platform was installed most recently.
The goal is not to strip useful functionality out of websites. It is to make the whole experience feel intentional again. Privacy, accessibility, support, analytics, marketing, and conversion can coexist. But they should behave like parts of one interface, not six interfaces fighting over the same visitor.