Websites Should Be Printable
This post argues that websites should prioritize printability, showcasing a simple CSS solution. It ignited a fiery debate on HN, polarizing opinions between those who champion accessibility and archival needs, and those who see printing as an antiquated, wasteful practice.
The Lowdown
The author, a graduating Computer Science student, champions the often-overlooked practice of making websites printable. Driven by their personal preference for marking up physical documents, they discovered that modern web pages often print poorly and set out to rectify this on their own site.
Here's a summary of the author's approach and rationale:
- Initial Discovery: A simple
Ctrl-Pon their website revealed unacceptable print quality, with oversized text, distorted headers, and grayed-out links. - CSS for Print: They implemented
@media printCSS rules to address these issues, allowing elements to be shown or hidden specifically for print, adjusting font sizes to standard 12pt for body text, and ensuring links print in black. - Codeblock Challenge: Noted that codeblocks remain a challenge, often failing to break across pages gracefully.
- Motivation: Acknowledges the effort involved and the likely small audience for printed web content, but frames it as an act of kindness to users, enabling them to engage with content in their preferred medium.
Ultimately, the author believes that for text-heavy sites, considering print styling is a small but meaningful gesture that enhances user experience and embraces the flexibility of the digital medium.
The Gossip
Philosophical Print Prerogatives
The discussion often pivoted to fundamental questions about the web's purpose. Some argued that Tim Berners-Lee's original vision was for navigable, not printable, documents, and that modern web complexity (JS-heavy sites, animations, ad-driven design) fundamentally conflicts with printability. Others countered that the web has evolved, and imposing strict historical definitions is unhelpful. They suggest that accommodating print is about user choice and flexibility, not a reversion to old paradigms.
Technical Troubles & CSS Challenges
Many commenters recounted their battles with print CSS. Common grievances included inconsistent browser rendering, the difficulty of managing page breaks for complex elements (like code or structured resume sections), and issues with background colors and images disappearing by default. Developers highlighted that debugging print CSS can be a 'pain in the ass' due to browser specificities and less scrutiny from browser makers. However, some argued that basic printability isn't that hard if integrated from the start, often preventing later demands for PDF generation.
Accessibility & Archival Advantages
A strong current of support for printability emerged from practical use cases and accessibility concerns. Users cited the need for physical copies for marking up documents, official records (invoices, receipts, legal filings), offline reading (especially on e-ink devices or for travel), and accommodating users with accessibility needs like dyslexia or limited motor control who benefit from consistent, physical layouts. Real-world examples, such as car shopping sites or internal documentation, highlighted tangible business and user needs that are often overlooked.
Environmental Echoes & Digital Defaults
The environmental impact of printing sparked a debate, with some forcefully advocating against paper use as wasteful, suggesting e-ink devices or PDF exports as superior alternatives. Counter-arguments emphasized the unique value of physical print for durability, security (unhackable records), and cognitive engagement (reading away from screens). Browser-native 'Reader View' features were also presented as a modern solution for clean content consumption, reducing the perceived need for websites to implement their own print styles.