Review headings, columns, spacing and photographs against reading tasks: a testing method for wide screens, smartphones and every language.
Updated :
AI-generated illustration
Where does the layout prevent reading or acting?
The absence of overflow does not guarantee a balanced composition. Huge headings, three cards squeezed into four columns or an overwhelming photograph may obscure useful information. Link each defect to its responsible CSS rule, correct the component and retest every page sharing it. Suggested widths form a working matrix, not a universal standard.
Build the matrix
Include home, section, long profile, results, form and tool. Try 320, 390, 768, 1024, 1440 and 1920 CSS pixels, then resize gradually between them. Add the longest headings and every script: a defect between breakpoints may escape familiar device screenshots.
Inspect the cascade
Record computed font size, line height, width, padding, margins and minimum height in browser tools. Identify the winning rule and specificity. A global h2 correction may leave a more specific selector unchanged. Review the affected component’s variants.
Restore reading hierarchy
Compare heading, introduction, subheadings and card text. Check wrapping and placement of the action. Bound sizes and adapt line height to the writing system. Remove fixed heights that leave empty space with short text or clip a longer translation.
Test columns
Inspect sets of three, four and five cards with real content. Switch to one column before paragraphs become cramped. Test long URLs and fields. Keep explicit local scrolling for tables requiring two dimensions.
Check photographs
Measure the box and aspect ratio, then currentSrc and transferred bytes. sizes should describe the occupied slot: half a page is not the full viewport. Check cropping of the subject, reserved dimensions and lazy loading below the fold.
Retest zoom and interactions
Test reading at 200% and reflow at 400% zoom on a suitable screen. Navigate menus, FAQs and fields by keyboard. Inspect visible focus and logical order. In Arabic, examine alignment, directional icons and Latin strings. Record results by URL, language and width. With a sticky header or banner, check that at least part of the control receiving focus remains visible.
Define which region may scroll
Where meaning requires a two-dimensional table, contain its scrolling while surrounding text fits the available width. Check keyboard access to every column. This must not make every card or the whole document a horizontal surface; record the precise region and reason for the exception.
IN PRACTICE
Check a journey, not just a screenshot
A readable screen can still block an action. Test a complete goal: find the right section, use the control, understand the result and go back. Record the first obstacle and its practical effect.
Which check comes first?
Choose the situation you observed. Each path gives a first check, useful evidence and the limit of that check.
The task works with a mouse but not a keyboard
First check
Repeat a task using Tab, Shift+Tab, Enter and the component’s expected keys. Track focus: where does it enter, which control receives it and can you leave a menu or dialog?
Evidence to retain
Step, key, focused control, open or closed state and the exact point where the task blocks or becomes unclear.
Limit to remember
Logical focus order does not certify overall accessibility. Also examine control names, announced states and content reading.
Trigger one field error and review its label, expected format and associated message. Check that it can be corrected without losing other useful values.
Evidence to retain
Field, non-sensitive test value, message, error-to-field association, focus behaviour and result after correction.
Limit to remember
A visible message may not be associated with its field or announced at the right time. Also test submission, confirmation and unavailability.
Narrow the window, enlarge text and repeat the task. Identify the component forcing the whole page to scroll horizontally; distinguish it from a table needing two-dimensional layout.
Evidence to retain
Viewport width, zoom level, language, component, hidden text and genuine need for two-direction scrolling.
Limit to remember
One mobile screenshot does not cover every zoom, language and state. A table exception does not justify whole-page overflow.
Keep a visible label and connect the error to its field.
Dynamic result
Changing a number without context.
Provide the result, unit and what changed.
01
Locate
Does the heading describe the right task?
02
Act
Is the control accessible and understandable?
03
Understand
Are the result and next action explicit?
Final check
Repeat the journey with Tab, Shift+Tab and Enter, then at 200% zoom. While scrolling, check that the fixed header does not completely hide the focused control. Open and close the menu using the keyboard, trigger a form error and check that you can correct it. Record the page, action and obstacle observed; these targeted checks are not WCAG certification.
A 720 px minimum height creates an almost full-screen scene. Bound the container and compare a two-column photograph/text layout. Review sizes and mobile cropping: file compression alone does not fix composition.
Three cards in four columns
The fourth track remains empty and paragraphs are narrow. Fit the grid to content, then retest three, four and five items with the longest Russian and Finnish headings.
A visually correct form
A fixed banner can hide focus, or an error may appear far from its field. Test failure and recovery by keyboard. Good alignment does not establish that the action can be completed.
A label disappears instead of wrapping
Illustrative case: a short action label becomes a longer translated phrase. A fixed height cuts its ending when text is enlarged. Check the complete label and focus, then allow wrapping or adjust the component. Shortening a translation until meaning is lost does not fix readability.
An anchor lands behind a fixed header
Example journey: a result opens a heading whose beginning is hidden by the header. Test direct links, keyboard navigation and return from another page. Adapt scroll positioning to the actual header; no horizontal overflow does not establish a visible destination.
Worked exercise
A readable table with an unreachable action
Fictional example: the values and documents teach the method and do not describe a real organisation.
On mobile, the table fits inside its container. The task is to reach confirmation while retaining access to the values being compared.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
Starting information
Item
Observed information
Table columns
9
Mobile container
Horizontally scrollable region
Confirmation button
In the last column
Scroll hint
Absent
Your checks
Reach the button by keyboard and touch.
Check region scrolling, not only page scrolling.
Test enlarged text and long labels.
Read the answer
Answer and decision
No page overflow does not establish usability. Make the region identifiable and the action reachable; consider moving the action outside the table or adapting presentation. Then check headings and preservation of compared values.
If the case changes
If the task compares nine attributes together, stacked cards may make comparison harder: test the task before choosing.
Record to retain
Keep width, zoom, input method, focus path and task outcome.
Do a filtered card, a long translated heading and an invalid form preserve consistent columns and spacing?
Does the photo file actually selected by the browser suit its displayed width without needlessly loading the largest variant?
Can users read and act using zoom and keyboard navigation without text hidden beneath a fixed element?
Does the component remain readable with a long translation and a direct section link?
Frequently asked questions
A breakpoint for every phone?
Choose points when the content stops working. Device models extend the matrix without justifying arbitrary rule proliferation.
Is 16 px always enough?
No. Typeface, contrast, line height, line length and zoom matter together. Test actual text and its readers.
Can a block be hidden on mobile?
Only if necessary information remains available. Reorganising a comparison or form is often preferable to removing explanations.
Why every language?
Lengths, scripts, wrapping and direction differ. A French template may break with a Finnish heading or a Latin address inside Arabic text.
Should one only test the home page on mobile?
Not to. Forms, tables, maps and long texts have other constraints. Choosing representative pages of components and content allows you to cover more useful situations.
A correct page on a large screen shows a cut or a horizontal scroll on the phone. The diagnosis must identify the responsible component and the conditions where the defect occurs.
Updated on .
Priority checks
Examine multiple widths, long texts, tables, menus and images. Check fixed width items, spaces and the possibility of returning to actions after opening a panel.
Interpretation pitfalls
Hidden the overall overflow can hide information or a order. A single phone width does not represent all situations, especially after zoom or language change.
Working record to retain
The report combines width, page, component and effect on the action. The correction is validated on the neighboring widths and with the longest content.