# Getting off the Modernization Treadmill: Build accessible, resilient websites with web standards

DevFeed: [Getting off the Modernization Treadmill: Build accessible, resilient websites with web standards](<https://devfeed.tech/articles/getting-off-the-modernization-treadmill-77117.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/talk-notes-modernization-treadmill/>)

Author: Jim Nielsen

Published: 2026-10-08T17:45:46.520742Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Website](<https://devfeed.tech/topics/website.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [css](<https://devfeed.tech/tags/css.md>), [develop](<https://devfeed.tech/tags/develop.md>), [html-css](<https://devfeed.tech/tags/html-css.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [performance](<https://devfeed.tech/tags/performance.md>), [software](<https://devfeed.tech/tags/software.md>), [talk](<https://devfeed.tech/tags/talk.md>), [technologies](<https://devfeed.tech/tags/technologies.md>), [the-web](<https://devfeed.tech/tags/the-web.md>)

## AI overview

Notes from Alexander Petros's Big Sky DevCon 2026 talk argue that public service websites should use HTML, CSS and JavaScript according to the web platform's strengths. Semantic HTML and core functionality that works without JavaScript can improve performance, accessibility and usability, especially for people using slower connections or devices. The talk also connects technology choices to values, contrasting user-focused public services with ad-driven engagement priorities.

## Source excerpt

My notes from this talk by Alexander Petros at Big Sky DevCon 2026. Alex starts by noting how "modernize" used to mean something along the lines of "update this thing that was made before I was born". But now "modernize" means something more like "update this thing from 5-10 years ago" (hence the framing of the talk, the "modernization treadmill"). Using a real-world example of an incredibly slow website that was required to access state-sponsored programs for welfare, Alex points out the disparity in conditions between those of us who make software and those who have to use them: The people who develop these websites are usually doing so on high-powered internet connections and high-powered devices, but they're not using them in the conditions that the people who most need those benefits are going to be. Then he shows a Reddit thread where somebody essentially posted, "I'm having problems with this website. I've been waiting for months for my application to go through. Any suggestions?" And one Reddit user responded, "The best thing you can do is go into the physical office, get a case worker, and your problems will be solved within the hour." The irony. I guess we've come full circle now. It used to be: "Don't talk to anybody. It's faster and more convenient to use the website!" But now it's: "Don't use the website. It's faster and more convenient to talk to somebody!" Have we failed at making websites? And is our failure, at least in part, rooted in the fact that we don't leverage the basic tools for making websites: HTML, CSS, and (in a distant third) JavaScript? Alex goes on to argue that the technologies of the web have an ideological bent and, if used as designed, can solve so many of the performance, accessibility, and usability issues that plague so many websites. The grain of the web's technologies are rooted in these values: User-friendly Backwards- and forwards-compatibility Long-term viability Universal accessibility Which means if you use them as inten