Check the profile at narrow widths and enlarged text settings using real reading tasks. Preserve a sensible order, readable content and operable navigation. Adapt comparisons, images and forms so their meaning survives stacking, and fix clipping or hidden information rather than assuming a responsive template has handled every page.
Begin with the content sequence
Choose tasks a visitor actually needs to complete: understand the offer, inspect a sample and find the contact route. Read each page in a narrow window without relying on the desktop arrangement. Side-by-side content often becomes a long stack, which can separate a claim from its qualification or place a next step before the relevant explanation. Check that headings and paragraphs still form a coherent sequence when there is only one column and less visible context at a time.
Pay particular attention to repeated elements. A tall header, oversized portrait or long introductory animation can consume most of the available space before useful content appears. Reduce their footprint when they obstruct the task rather than simply shrinking every element. Let text wrap and grow. Important descriptions should not be clipped to preserve a card height, and status labels such as independent practice should remain visible instead of disappearing from the smaller version of a project card.
Inspect content types that often break
Check comparison tables, screenshots, long links and downloadable material. A table may need a different presentation to preserve the relationship between headings and values; making the whole page scroll sideways creates a difficult reading experience. A before-and-after image pair needs labels and explanatory text when the images stack. Screenshots should not be the only place essential instructions appear, because their embedded text may become unreadable when scaled to fit a narrow screen.
Try navigation and form controls with the interaction methods available, including keyboard use where appropriate. Ensure that menu labels remain understandable and that opening a menu does not hide the page without a clear way to continue or close it. Check field labels, error messages and confirmations in the same layout. Do not assume a small icon communicates the same meaning as its desktop text label. Keep important actions identifiable without requiring precise tapping or a hover state.
Check enlarged text and complete routes
Increase text size or zoom and inspect wrapping, spacing and overlap. A layout that fits a standard phone screenshot may still fail for someone who needs larger text. Look for content hidden behind fixed headers, buttons that overlap paragraphs and lines cut off inside fixed-height containers. Record the actual problem and the conditions in which it occurs. A small-screen review is most useful when it identifies a specific obstacle rather than assigning a general impression of responsiveness.
Finish the full visitor route, including the case page, contact form and confirmation. Check more than the homepage because page-specific content often introduces the problem. Repeat targeted checks after the affected layout changes, and keep unresolved issues visible in your maintenance notes. These checks provide evidence about the tasks and conditions examined; they do not establish comprehensive accessibility. Use fuller evaluation when needed, particularly for interactions or content whose behaviour cannot be understood from a screenshot alone.
Fictional example: a comparison that loses its labels
A fictional advisor, Mei, reviews an invented two-service profile on a narrow screen. The desktop comparison uses headings at the top of two columns, but the mobile stack separates each price assumption from its service name. Mei restructures the comparison into labelled sections that retain the task, handover and conditions together. She keeps the detailed text available instead of replacing it with unexplained icons.
Mei then checks enlarged text and the path to the contact form, where one button overlaps a required-field instruction. The example records these specific issues and their corrections. It does not claim that the profile is fully accessible or that one viewport proves it works on every device, browser and assistive technology.
A checklist for your next step
- Test real tasks at narrow widths.
- Keep claims and conditions together.
- Inspect comparisons and screenshots.
- Check navigation and form states.
- Review enlarged text and full routes.
Common questions
Is checking a phone screenshot enough?
No. Inspect interaction, reading order, enlarged text and page-specific content. A static image cannot demonstrate the whole route.
Should all desktop content remain on mobile?
Preserve information needed for the task. Adapt presentation rather than hiding material conditions or essential evidence to make the layout shorter.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.