On the large monitor the new Wohnwissen article looks balanced. The text is on the left, a sample calculation on the right; beneath lies a wide comparison table. When reading in a narrow view the lines now continue sideways while a fixed notice area obscures the final paragraph. The problem cannot be solved by a smaller photo alone.
This workshop recommends that real-estate companies in Austria and Germany commission a dedicated process for designing their knowledge pages. It does not address any specific product surface and does not change a website. An expert technical review remains a separate step; no complete conformity confirmation follows from the reading sample below.
Small display and enlarged display are two approaches
People can read on a small device or enlarge content on a larger device. The commission should take both needs into account. A suitably reduced overall image may fit on one screen, but the text can still remain difficult to read.
The W3C describes reflow as layout without loss of information or function and without requiring scrolling in two directions under the specified conditions. For vertically read content the criterion specifies a width corresponding to 320 CSS pixels; exceptions exist for parts that truly require two-dimensional presentation. [REFLOW]
This reference is not a general quality judgement about every screenshot. The subsequent technical review must establish suitable conditions and examine the actual content. The simple editorial contribution is initially to prepare a complete reading path rather than only an attractive initial view.
Choose a real reader task for the sample page
Our fictional article explains the difference between a listing price and a personal cost plan. The reader should understand the explanation, find an example item and then recognise which details remain open for their case.
For this task headline, explanation, calculation, limitation and the next reference are required together. It is not sufficient on narrow width to show only the image and the first sentences. Include longer terms, a multi-line notice and the place with the wide content in the design review.
This selection is its own editorial method. It is not a statistically representative user test. It merely makes concrete design issues visible before the same structure is applied to a large knowledge library.
Reorder content without losing context
A lateral infobox can appear in a different place in a narrow view. What matters is that its statement can still be associated with the correct paragraph. If a necessary limitation only appears long after the related promise, the content relationship should be checked in the draft.
Therefore do not plan only positions such as “to the right”. Describe the relationship: this explanation belongs to that sample calculation. The design can then develop an appropriate order for different views. A reader need not know where an element stood on the large screen.
With a fixed bar the practical question is whether the content and its operation remain accessible in the intended state. The W3C explanation also points to possible problems from fixed overlapping elements when enlarging. [REFLOW] A specific technical solution is not prescribed here.
A table may keep its structure
Not every wide content can be sensibly broken down into individual independent rows. A table can become understandable precisely through the relationship of its columns and rows. Plans and maps can also require a two-dimensional presentation for their sense. The reflow explanation addresses such limited exceptions. [REFLOW]
What matters is their extent: a necessary wide table does not explain why the entire subsequent body text must run sideways out of the reading area. Ask the support team how the wide part remains understandably accessible and how the remaining text stays readable. A statement “tables are simply wide” would not yet be a complete test justification.
In the sample the calculation table is planned to remain a coherent comparison. Additionally its central message is explained in a separate comprehensible paragraph. This editorial addition does not automatically replace a technically correct table structure. It does, however, help to describe the intended content unambiguously before implementation.
Formulate findings as tasks
A useful piece of feedback might be: “In the indicated view the note on the invoice cannot be read in full.” It specifies the passage of text, the condition and the effect. “Mobile: poor” is less actionable because support cannot tell from that which task is affected or what exactly is lost.
Record whether it concerns font size, truncated text, an unfortunate order or missing accessibility. These observations may occur together, but are not automatically the same error. The technical classification will be made with the appropriate specialist.
A later review should examine the actually generated version. The design file and the published presentation can be different stages of work. This article does not review either of the two states and does not assume any live function to be present.
The result is a comprehensible reading path
After their own sample check the team knows which contents absolutely belong together, which parts require a wide presentation and which observations need professional clarification. From this arises a precise assignment with limited acceptance criteria.
A small screen is therefore not merely a reason to shrink everything together. Good preparation asks whether a person can read the whole train of thought including limits and the next step. This is a concrete quality requirement of the knowledge side, without presupposing a complete accessibility audit.