So far, we’ve focused on making the browser an effective platform for developing web applications. But ultimately, the browser is a user agent. That means it should assist the user in whatever way it can to access and use web applications. Browsers therefore offer a range of accessibility features that take advantage of declarative UI and the flexibility of HTML and CSS to make it possible to interact with web pages by touch, keyboard, or voice.
Embedding The Web
We need to talk more The web is much more than browsers. What works great in browser development is missing in related spaces like embedding. Can we get together to collectively describe security and compatibility properties of user agents that are not browsers? Can we develop things that don’t ...
brief history of browser accessibility support
Author: steve faulkner The Paciello Group contact: [email protected]
Group Note Draft: Web User Agents
Web user agents include both web browsers and other intermediaries between end-users and the web.
Supporting Embedded Content | Web Browser Engineering
While our browser can render complex styles, visual effects, and animations, all of those apply basically just to text. Yet web pages contain a variety of non-text embedded content, from images to other web pages. Support for embedded content has powerful implications for browser architecture, performance, security, and open information access, and has played a key role throughout the web’s history.
Wasm-agents: AI agents running in your browser
One of the main barriers to a wider adoption of open-source agents is the dependency on extra tools and frameworks that need to be installed before the agents can be run. In this post, we show how to write agents as HTML files, which can just be opened and run in a browser.
Running Interactive Scripts | Web Browser Engineering
The first web applications were like the previous chapter’s guest book, with the server generating new web pages for every user action. But in the early 2000s, JavaScript-enhanced web applications, which can update pages dynamically and respond immediately to user actions, took their place. Let’s add support for this key web technology to our browser.
A Deep Dive into Accessibility APIs, Part 1 — Knowbility
In this first Deep Dive into Accessibility APIs installment, we'll start from absolute scratch and recount the widely available basic story. It's written for beginners, but the fact that I describe web accessibility in the broader context of software accessibility might offer a different twist for current practitioners as well. Parts 2 and 3, on the other hand, are more technical. Although those discussions may largely be of interest only to "inquiring minds that want to know", understanding the history and variety of the specialized protocols at the heart of this process sheds light on why screen readers sometimes perform differently in the same application or on the same web site while also providing a glimpse of a likely future.
WebAIM: Web Accessibility In Mind
Expanding the potential of the web for people with disabilities by empowering individuals and organizations to create accessible content.
Your Browser May Be Having a Secret Relationship with a Screen Reader: A Deep Dive into Accessibility APIs, Part 3 — Knowbility
The final installment of the three-part saga on the technical details of how screen readers communicate with other software.
WebAIM: The WebAIM Million - The 2026 report on the accessibility of the top 1,000,000 home pages
For the eighth consecutive year, WebAIM conducted an accessibility evaluation of the home pages for the top 1,000,000 web sites. The evaluation was conducted using the WAVE stand-alone API (with additional tools to collect site technology and category data). The results provide an overview of and insight into the current state of web accessibility for individuals with disabilities as well as trends over time.
A threat model for accessibility on the web - Alice
A explanation of the primary threat to accessibility on the web, and a call to action for the web standards community
Handling Buttons and Links | Web Browser Engineering
Our browser is still missing the key insight of hypertext: documents linked together by hyperlinks. It lets us watch the waves, but not surf the web. So in this chapter, we’ll implement hyperlinks, an address bar, and the rest of the browser interface—the part of the browser that decides which page we are looking at.
AI Browsers & the Web User Agent: What Might Need to Change?
AI browsers may fit the Web User Agent definition, but their autonomy raises questions for web architecture, standards, and user protection.
Launch HN: Browser Use (YC W25) – open-source web agents | Hacker News
Check out this video to see it in action: https://preview.screen.studio/share/r1h4DuAk. There are lots more demos at https://github.com/browser-use/browser-use on how we control the web with prompts.
Sending Information to Servers | Web Browser Engineering
So far, our browser has seen the web as read-only—but when you post on Facebook, fill out a survey, or search Google, you’re sending information to servers as well as receiving information from them. In this chapter, we’ll start to transform our browser into a platform for web applications by building out support for HTML forms, the simplest way for a browser to send information to a server.