---
title: New Browser Run endpoint for accessibility trees
description: Browser Run now supports a standalone /accessibilityTree endpoint for capturing the semantic structure of rendered webpages.
image: https://edgetunnel-b2h.pages.dev/changelog-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://edgetunnel-b2h.pages.dev/changelog/) 

## New Browser Run endpoint for accessibility trees

Jul 07, 2026 

[ Browser Run ](https://edgetunnel-b2h.pages.dev/browser-run/) 

[Browser Run](https://edgetunnel-b2h.pages.dev/browser-run/) now supports a standalone `/accessibilityTree` endpoint, giving agent and automation workflows direct access to the browser's accessibility tree for a rendered webpage.

An accessibility tree is the browser's structured view of a rendered page: roles, names, states, values, and hierarchy. It is useful for accessibility tooling, but also for AI agents and automation workflows that need page structure without the noise of raw HTML or the cost of screenshots.

For AI agents, this means less inference from pixels and less parsing HTML. You can provide the page structure directly, helping agents identify available elements and determine which actions they can take.

With the new `/accessibilityTree` endpoint, you can request the accessibility tree directly when you only need the semantic structure of a page. If you need multiple page formats in a single API call, you can use the [/snapshot](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/snapshot/) endpoint, which also returns Markdown, HTML, and screenshots.

```bash
curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-run/accessibilityTree' \
  -H 'Authorization: Bearer <apiToken>' \
  -H 'Content-Type: application/json' \
  -d '{
    "url": "https://example.com/"
}'
```

```json
{
  "success": true,
  "result": {
    "accessibilityTree": {
      "role": "RootWebArea",
      "name": "Example Domain",
      "children": [
        {
          "role": "heading",
          "name": "Example Domain",
          "level": 1
        },
        {
          "role": "link",
          "name": "Learn more"
        }
      ]
    }
  }
}
```

Use `interestingOnly` to return only semantically meaningful nodes, or `root` to capture the accessibility tree for a specific subtree.

Refer to the [/accessibilityTree documentation](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/accessibility-tree-endpoint/) for usage examples and supported parameters.

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-07-browser-run-accessibility-tree-endpoint/#page","headline":"New Browser Run endpoint for accessibility trees · Changelog","description":"Browser Run now supports a standalone /accessibilityTree endpoint for capturing the semantic structure of rendered webpages.","url":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-07-browser-run-accessibility-tree-endpoint/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/changelog-preview.png","dateModified":"2026-07-07","datePublished":"2026-07-07","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```