gitwtfhub

wtf is aom?

wicg/aom — explained in plain English

Analysis updated 2026-08-08 · repo last pushed 2024-06-26

601HTMLAudience · developerComplexity · 2/5DormantSetup · easy

TL;DR

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.

Mindmap

mindmap
  root((repo))
    What it does
      Modify accessibility tree
      Send screen reader alerts
      Programmatic accessibility control
    Use cases
      Drag and drop interfaces
      Custom interactive widgets
      Web-based games
    Tech stack
      JavaScript
      HTML
      Chrome demos
    Audience
      Web developers
      Browser engineers
      Accessibility advocates
    Status
      Exploratory proposal
      Not production ready
      Industry collaboration

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Build accessible drag-and-drop interfaces that screen readers can understand.

REASON 2

Create custom interactive widgets that announce state changes to assistive technologies.

REASON 3

Develop web-based games accessible to screen reader users.

REASON 4

Explore proposed APIs for programmatic accessibility control in Chrome demos.

What's in the stack?

JavaScriptHTMLChrome

How it stacks up

wicg/aomsxyazi/free-hlsanthropics/launch-your-agent
Stars601612678
LanguageHTMLHTMLHTML
Last pushed2024-06-262022-03-312026-07-02
MaintenanceDormantDormantMaintained
Setup difficultyeasymoderatemoderate
Complexity2/53/53/5
Audiencedeveloperdeveloperpm founder

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Demos are Chrome-specific and the spec is exploratory, so no production setup is needed to read the explainers and try the demos.

No license information is provided in the project materials, so usage terms are unclear.

Wtf does this do

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.

Yoink these prompts

Prompt 1
Show me how to use the Accessibility Object Model notification API to announce a button click to a screen reader in JavaScript.
Prompt 2
Write a drag-and-drop interface demo that uses AOM to update the accessibility tree when an item is moved between lists.
Prompt 3
Create a tic-tac-toe game that uses the Accessibility Object Model to tell screen readers about each move and game state changes.
Prompt 4
Explain how modifying the accessibility tree via JavaScript differs from using ARIA attributes, with a code example based on the AOM proposal.
Prompt 5
Build a custom interactive widget that uses AOM to set accessibility properties programmatically instead of HTML attributes.

Frequently asked questions

wtf is aom?

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.

What language is aom written in?

Mainly HTML. The stack also includes JavaScript, HTML, Chrome.

Is aom actively maintained?

Dormant — no commits in 2+ years (last push 2024-06-26).

What license does aom use?

No license information is provided in the project materials, so usage terms are unclear.

How hard is aom to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is aom for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.