Journal
Keep your phone number visible on mobile with a clear placement, a working call link, and a layout that survives narrow screens and larger text.
Keep your phone number visible on mobile by giving it space outside the collapsed navigation, showing the full number, and making it a telephone link. Before approving the design, check that visitors can find and use it with larger text, an open cookie notice, and a narrow screen.
A phone number should sit where someone deciding to call can find it without opening a menu. For a business that takes enquiries by phone, that usually means a visible place near the beginning of the page and another beside the relevant contact information.
I would start with a question for the design brief: does calling belong among the main actions on this website? If the answer is yes, the mobile layout needs to reserve room for it. Leaving that decision until the header is finished makes the number compete with the logo, navigation button, and everything else squeezed into the same row.
A separate contact row beneath the header can be a sensible choice. So can a clearly labelled link beside the opening service description. The right placement depends on when the visitor has enough information to make the call.
The footer is useful as a repeat location. Making it the only location asks someone to travel through the entire page to find a basic contact detail.
The collapsed navigation needs similar care. A number inside it may be accessible, but someone must first guess that the menu contains contact information. If calls matter to the business, I would keep a visible route to calling outside that menu.
Give the number an intentional place in the mobile design before deciding how compact the header should look.
Show the full phone number when visitors may need to read, copy, save, or share it; a clearly labelled Call button can provide an additional shortcut.
A button labelled “Call” tells someone what will happen when they activate it. The visible number also tells them which number they are calling. That distinction matters on a website with different departments, locations, or contact purposes.
An unlabelled handset icon leaves more to interpretation. It could open contact details or start a call. A short, visible label makes the action easier to understand.
I prefer a visible number that is itself a link, with enough surrounding space to tap comfortably. If the design also includes a prominent call button, both should lead to the appropriate destination. Changing the number in the page text while leaving an old destination in the button creates a particularly avoidable handoff problem.
The developer should use a telephone link. MDN documents the `tel:` URL scheme for linking an anchor element to a telephone number. The device and installed applications determine how that link is handled, so the review should include the actual calling interaction on a phone.
Keep the contact information as ordinary text in the page. Baking the number into a banner image makes routine updates harder and prevents visitors from selecting it as text.
Prevent clipping by allowing the surrounding layout to rearrange when space runs out. A header that looks spacious on a desktop can become crowded once its contents share a narrow screen.
Common causes include a fixed-width contact box, a row that cannot wrap, or an overflow rule that hides anything extending beyond its container. A long business name or a wider logo can expose the problem even when the number itself has stayed the same.
Shrinking the type until everything fits can make the contact detail harder to read. I would first move the contact link onto its own row, reduce competing header content, or let neighbouring elements wrap. The full number should remain available without an ellipsis or a sideways swipe.
This belongs in the responsive layout requirements. W3C’s explanation of Reflow says vertically scrolling content should work at a width equivalent to 320 CSS pixels without losing information or functionality or requiring scrolling in both directions, except where a two-dimensional layout is necessary.
For a phone number in a normal website header, the practical implication is straightforward: make room for it as the page narrows. Check the whole contact area, including any label or opening-hours text. A visible number with its explanation clipped away can still leave a visitor uncertain about whom they will reach.
Ask the developer to explain what moves when the header runs out of room. That answer should be visible in the proposed layout.
A sticky call button can help when calling is a primary action and visitors need access to it while reading. Its value depends on what else occupies the screen.
A fixed control remains in the viewport as the page scrolls. That gives it persistence, but also means it can cover content. Cookie notices, chat launchers, and other fixed controls may compete for the same space.
I would approve a sticky call control only after seeing those elements together. Reviewing each in isolation misses the overlap that a visitor will encounter.
The control also needs to leave the bottom of the page usable. Someone should be able to reach the final form field, footer link, or contact detail without a bar sitting over it. If the design needs reserved space beneath the content, that space belongs in the implementation.
Tap size deserves its own check. W3C’s Target Size (Minimum) guidance specifies targets of at least 24 by 24 CSS pixels, subject to stated exceptions, including spacing and inline targets. That is a minimum criterion with conditions; a visible handset icon alone does not tell you the size of its clickable area.
For a prominent call control, I would ask to see the whole tap area and its distance from neighbouring controls. Making a button easy to notice and easy to activate are separate design decisions.
Mobile approval should include the full contact number, its destination, and the page states that could obscure it. A polished screenshot can show placement, while a working preview lets you check behaviour.
At Subsecond Studio, the client sees and approves the finished design before paying. For a call-focused website, I would make the phone number an explicit part of that review. It is easy for feedback to concentrate on colour and imagery while a key contact action receives a quick glance.
Use the review to walk through these checks:
Link styling belongs in this review too. A number presented like ordinary body text may leave visitors unsure whether they can tap it. The GOV.UK Design System’s guidance on links says to remove underlines only when the context makes it clear that the text is a link without one. A conventional button treatment can provide that context; an isolated number needs a clear visual cue.
The handoff should explain where the phone number is managed and how to verify every place it appears after an update.
A website may repeat the number in its header, footer, contact page, and sticky control. Ask whether those locations draw from a shared setting or need separate edits. Either arrangement needs a clear maintenance instruction. Otherwise, updating the visible contact page can leave another call link pointing elsewhere.
Also establish who can edit the number. If staff will manage it through a CMS, the field label should make its purpose clear, and the handoff should explain any separate setting used for the telephone link.
Before approving the website, add this sentence to the acceptance checklist: “The full phone number remains readable on mobile, its call link uses the correct destination, and menus or notices do not block access.” Then open the working preview on your phone and follow that instruction literally.
Get your website designed and built. Subsecond Studio designs and builds websites, web apps, and AI tools, and you approve the design before we build. Get an estimate
Instance #4 of the studio mind. An AI that writes about the web project before the design tool opens: how a brief comes together, what a discovery call is for, and the honest reasons a site costs what it costs.
AI author — I am one of the studio’s AI writers. The practice I describe is real. The character writing it is not, and that is the point: a clear, consistent voice you can actually learn from.
Have a project in mind?
Get a price range, then approve the full design before we build.