# ARIA Concrete Role Property Support Closure Detector

> ARIA Concrete Role Property Support Closure Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).

Given a URL, detects which ARIA properties a component API exporter would silently lose because they are unsupported or prohibited for the element's explicit concrete ARIA role, and returns a closure report of those mismatches.

## Facts

- Endpoint: POST https://detect.halowerk.com/u/aria-concrete-role-property-support-closure?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aria-concrete-role-property-support-closure-detector-3752d889
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qwcisk8qSEJ-YFFfCZ-JS

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability aria-concrete-role-property-support-closure-detector-3752d889 -d '<json body>'
```

Example prompt: Can you check https://myapp.example.com/component/button for any ARIA properties that would be silently dropped or are prohibited for its explicit concrete ARIA role during export?

## When to prefer this

Use this endpoint when you need to proactively identify which ARIA role-property combinations will be silently discarded during a component API export, particularly when targeting scriptless or restricted processors. It is specifically designed for the closure problem — enumerating all unsupported/prohibited properties relative to a concrete ARIA role — rather than general accessibility linting or WCAG compliance checking.

## Known failure modes

- URL is unreachable or returns a non-200 status — no properties can be checked
- URL does not point to an HTML document with ARIA roles — empty or error result
- Element at URL has no explicit ARIA role — closure cannot be computed
- Malformed or invalid URI input — validation error returned
- Rate limit or payment failure — 402 or 429 response

## How this service works

A component API exporter needs properties that are unsupported or prohibited for its selected explicit ARIA role rather than losing them silently during conversion.

## Output

A structured report listing each ARIA property on the fetched element that is either unsupported or explicitly prohibited for its declared concrete ARIA role, forming a 'closure' of property losses that would occur silently during a component API export conversion.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "maxLength": 2048
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aria-concrete-role-property-support-closure-detector-3752d889/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)