Design for Everyone, Starting with Mobile

Desktop layouts can hide indecision behind extra space. A phone cannot. When the screen is narrow, the hierarchy has to answer three questions quickly: what is this, why should I care and what can I do next?

Small screens reveal weak priorities

W3C treats mobile accessibility as part of the same accessibility standards that apply across the web. Touch targets, readable type, clear focus states and sensible motion are not optional polish. They are part of whether a person can use the experience.

"Responsive design is not a smaller desktop. It is a clearer decision path."

Design around the task

Start with the most important task on the page and give it the most reliable path. If the page is a service page, that might be understanding the offer and requesting a conversation. If it is a portfolio page, that might be opening a project without losing the surrounding context.

• Keep the primary action visible without making it compete with five secondary links.
• Use headings and spacing to make scanning work before reading begins.
• Give images meaningful alt text when they carry information.
• Make focus states visible for keyboard users and people navigating with assistive technology.

Make touch, type and motion predictable

People use phones in bright rooms, one hand and interrupted attention. Controls need enough space to tap, text needs enough contrast to read and animations should never hide the action a person came to complete.

Test the page with a slow connection and a larger text setting. If the layout remains understandable, the design is doing its job instead of depending on perfect conditions.

Check the real journey

A mobile review should follow a complete journey, not just inspect the first screen. Open the menu, jump to the relevant section, fill a form, close a dialog and return to the previous context. The small moments between those steps are where trust is either built or lost.