Mobile-Friendly AI Websites: Readable Fonts on Small Screens
Explore Raccog’s updated mobile typography guidance: readable body text, fluid headings, font fallbacks and form controls designed for smaller screens.

A mobile-friendly website needs more than columns that stack. Visitors still need to read product descriptions, understand labels and complete forms. A layout can fit the screen while its text remains too small to use comfortably.
Raccog’s October 7 update strengthens the typography guidance used to generate and edit pages. The builder is instructed to preserve readable text on narrow screens rather than shrinking everything until the layout fits.
What changed in generation guidance
The updated instructions call for a consistent system font stack with appropriate fallbacks, body text of at least 1rem and supporting text of at least 0.875rem. They also specify a body line height of 1.5–1.7 and form control text of at least 16px.
These are generation targets, not a claim that every generated page has passed a visual accessibility audit. Existing pages also need an explicit revision before the new guidance can affect their design.
Make this page readable on small screens. Preserve the brand style, let long headings wrap and keep every form field and button usable. Check the product cards and contact form at narrow widths.
Scale headings without shrinking the whole page
A large desktop headline can become awkward on a phone. The solution is to give it sensible size limits and allow it to wrap, while keeping body copy readable.
Raccog’s guidance uses fluid heading sizes with minimum and maximum bounds. It discourages viewport-only font sizing, which can make text excessively small as the screen narrows. The aim is a clear hierarchy: a prominent heading, readable explanation and an easy-to-find action.
You can reinforce that intention in a revision:
Reduce the hero heading on phones, keep the paragraph at a comfortable reading size and let the heading use multiple lines. Do not hide part of the copy.
Give real content room to wrap
Long product names, email addresses and button labels expose problems that short placeholder text can hide. The updated guidance tells the generator to let headings, labels and long URLs wrap and to avoid fixed text heights that clip content.
For a saree catalog, review a product with a long fabric-and-weave name, a multi-line description and several options. Check that the price and order action remain visible. Read about the broader shopping flow in our ecommerce website planning guide.
Review the page on a small screen
Use a narrow preview and, where possible, an actual phone. A practical pass includes:
- Read body text and secondary labels without zooming in.
- Open the mobile menu and confirm every destination remains reachable.
- Enter text in form fields and check labels, errors and submit buttons.
- Try long headings and real product descriptions instead of short samples.
- Increase text size and check that content remains accessible.
- Look for page-wide horizontal scrolling or overlapping controls.
The builder’s responsive guidance covers widths starting at 320 CSS pixels and calls for usable text at 200% zoom. Browser checks are still necessary to establish how a particular generated page behaves.
Common questions
Does a mobile-friendly site need a custom font?
No. A consistent system font stack can provide readable text without an external font download. Brand-specific type still needs suitable fallback choices and a review across devices.
Will these changes update my existing website automatically?
No. Ask the builder to revise the relevant page or component, then review the result before publishing.
Should all text be the same size on mobile?
No. Keep a clear visual hierarchy. Headings can scale while paragraphs, supporting text and controls retain readable sizes.
For help writing a focused revision, see our website prompt guide. Open your project in Raccog to review its mobile layout.
Try it on your own brief.
One sentence about the business, and Raccog drafts the whole site.
Read next
