When should we use custom website controls?

Choosing a custom control means taking responsibility for behaviour that a native browser element would otherwise provide. A native element, for example, lets users access its list with a keyboard. Replacing it to achieve a particular visual design makes keyboard operation and screen-reader recognition part of the development task, not simply a styling consideration.

Before choosing a custom approach, establish whether the native element meets the interaction need and whether the replacement can preserve accessible operation. Smashing Magazine explained in 2025 that native HTML elements are preferable when they fit the interaction because ARIA changes announced semantics but does not supply keyboard behaviour or other functionality. WebAIM reported in 2026 that 22% of detected ARIA menus on leading website home pages globally introduced accessibility barriers through missing required menu markup or interactions.

Treat the intended appearance and the control's accessible behaviour as a single design decision.

Sources: Designing and developing web experiences for everyone

How The Frameworks helps

Developing accessible website interactions

You need website controls that people can use reliably without compromising the intended design. The Frameworks brings digital design and development together, treating the visible interface and its underlying behaviour as connected decisions. For interactions where the design calls for something beyond standard controls, its approach keeps accessibility within the development brief rather than leaving it as a finishing task. It works with you on how those interactions fit the design, technical constraints and requirements of your website.

The Frameworks offers website redesign and redevelopment to improve accessibility and responsiveness, alongside ongoing maintenance for the resulting experience. These services connect changes to the interface with the development work needed to support them, rather than treating controls as isolated visual elements. You get a website whose intended interactions are supported by its implementation, with maintenance available to address accessibility and responsiveness as the site evolves.

Let’s talk about your website control choices ^↗

Related

• How can we balance website design and accessibility?
• Which access needs should a website design account for?
• What keeps interactive websites usable across browsing conditions?
• How do accessibility overlays compare with fixing underlying website barriers?
• How do we structure our website around buyer needs?
• What should an innovation centre website show?

Got a challenge?
Let’s talk ^↗

Curious?
Sign up to our newsletter ^↗

Cookie consent

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyse site usage, and assist in our marketing efforts. View our Privacy policy for more information.

Deny

Accept

Privacy preferences

Essential cookies

Required

Marketing cookies