wicg/aom — explained in plain English
Analysis updated 2026-08-08 · repo last pushed 2024-06-26
Build accessible drag-and-drop interfaces that screen readers can understand.
Create custom interactive widgets that announce state changes to assistive technologies.
Develop web-based games accessible to screen reader users.
Explore proposed APIs for programmatic accessibility control in Chrome demos.
| wicg/aom | sxyazi/free-hls | anthropics/launch-your-agent | |
|---|---|---|---|
| Stars | 601 | 612 | 678 |
| Language | HTML | HTML | HTML |
| Last pushed | 2024-06-26 | 2022-03-31 | 2026-07-02 |
| Maintenance | Dormant | Dormant | Maintained |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 3/5 | 3/5 |
| Audience | developer | developer | pm founder |
Figures from each repo's GitHub metadata at analysis time.
Demos are Chrome-specific and the spec is exploratory, so no production setup is needed to read the explainers and try the demos.
The Accessibility Object Model (AOM) is a proposed web standard that would let developers directly adjust how accessible a web page is using JavaScript code. Right now, making a website work well with screen readers and other assistive technologies relies on adding specific HTML attributes. This project wants to give developers a more powerful, programmatic way to control that experience from code. The project has two main parts. The first part is about letting developers modify the "accessibility tree," which is the behind-the-scenes structure that assistive technologies read to understand a page. Instead of only being able to set accessibility info through HTML, developers could use JavaScript to set or change it directly. The second part is a notification API, which would let web apps send confirmation messages to assistive technologies, for example, telling a screen reader to announce that a button was successfully clicked, even if the visual page doesn't immediately change. This would be useful for developers building complex, interactive web applications where the standard HTML approach falls short. Think of a drag-and-drop interface, a custom interactive widget, or a web-based game like the tic-tac-toe demo included in the project. In those cases, what the user sees and does doesn't always map cleanly to traditional HTML elements, so conveying the right information to someone using a screen reader becomes difficult. This API would bridge that gap. The project is a collaborative effort involving engineers from Google, Apple, Microsoft, and Mozilla, which signals broad industry interest in solving this problem. However, it is still an exploratory initiative, the spec is noted as not fully up to date, and the included demos are designed for Chrome specifically. Developers can read the explainer documents and try the interactive demos to understand the direction the proposal is heading, but it is not yet a finished standard they can rely on in production.
A proposed web standard that lets developers control web page accessibility programmatically through JavaScript, instead of relying only on HTML attributes, to better support screen readers and assistive technologies.
Mainly HTML. The stack also includes JavaScript, HTML, Chrome.
Dormant — no commits in 2+ years (last push 2024-06-26).
No license information is provided in the project materials, so usage terms are unclear.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.