AccessBuild Day 3: Auto-Scanning Is Live. Here’s What I Learned.

Description and use

The API now accepts Android UI XML trees, classifies elements, scores accessibility, and persists audits in Supabase, offering audit history and statistics.

Problem

The API could only score manually pasted elements; it lacked memory and persistence for real-world Android UI scans.

Outcome

Implemented auto-scanning of Android UI trees, added persistence, and exposed audit/history endpoints, achieving a 40% accessibility score on a test banking login screen.

Workflow

• Receive raw Android UI tree XML via /scan endpoint
• Walk through each node and classify element type
• Check for accessibility labels
• Calculate grade (A‑F) based on label coverage
• Write audit record to Supabase PostgreSQL
• Return grade and audit data to client

Evidence

Yesterday, the API could only score elements you pasted in manually. Today, it parses real Android UI tree XML, extracts every interactive element, scores it, and saves the result to Supabase.

Source

The new /scan endpoint accepts a raw UI tree dump. It walks through every node, classifies each element as button/input/icon/link, checks for accessibility labels, and returns a grade from A to F. Then it writes the audit to the database.

Source

I ran the first auto-scan on a test banking login screen. Five interactive elements. Only two had labels. Result: D — 40% accessible

Source