Rethinking Text Resizing on Web

Original Article ↗ Hacker News Discussion ↗

Overall sentiment about Airbnb and UX authority

  • Many criticize Airbnb’s product UX as dark-pattern heavy (irrelevant search results, forced phone numbers, unusable account constraints).
  • At the same time, several distinguish between disliking the product and respecting Airbnb’s frontend engineering and open‑source work.
  • Some point out their own site still has numerous accessibility issues, making their guidance feel somewhat ironic.

Text size, aging, and browser zoom behavior

  • Strong agreement that default font sizes are often too small; many users manually zoom to 150–160%.
  • Aging eyes and presbyopia are cited as universal drivers for larger text.
  • Complaints that some sites enforce very large text without an option to shrink it.
  • Several miss older “text‑only zoom” behaviors; Firefox’s option is praised, whole‑page zoom is seen as a regression.

200% text scaling and CSS choices

  • 200% text scaling (from WCAG) sounds simple but is described as technically hard: layouts encode many assumptions about fixed relationships and spacing.
  • Debate over use of rem vs px:
    • One camp argues for rem only for text and px for layout/spacing so text scaling doesn’t blow up grids and whitespace.
    • Others note common advice has been “everything in rem,” which effectively turns text scaling into full zoom.
  • Some share utilities and clamp() patterns to derive font scales from viewport size, while others criticize over‑engineered schemes (e.g., golden ratio everywhere).

Responsive design, mobile form factors, and accessibility gaps

  • Small phones (4–5.8") with larger accessibility fonts frequently break layouts; many major sites and apps fail basic scrollability and truncation handling.
  • Complaints that enterprises often ignore smaller devices and accessibility from the start; issues get deprioritized.
  • Container/media queries and “breakpoints” spark debate; some argue modern flex/grid should handle most cases, others insist breakpoints are still needed for complex UIs.

Broader critique of modern web/frontend culture

  • Nostalgia for simpler, CSS‑light, semantic HTML sites where user settings control typography.
  • Frustration with CSS‑in‑JS trends, framework‑driven breakpoints, and design obsessed with branding over usability.
  • Some argue much of today’s web design is self‑inflicted complexity; others defend serious interface design as necessary, distinct from mere “prettiness.”