lulzx

which ones do you want it to run? I can test out

Every few months someone proposes a new standard so AI agents can interact with websites. WebMCP, llms.txt, agent metadata layers.

The accessibility tree already solves this. Labels, roles, states, actions, input formats, validation feedback, it's all there. A screen reader user and an AI agent need the exact same information. If your site works for one, it works for the other.

If you find something an agent can't do through the accessibility layer, you've found something a disabled person's assistive technology can't do either. So fix accessibility. Don't build a parallel system.

I filed an issue on the W3C WebMCP repo asking for a concrete use case that (1) can't be handled by the accessibility tree, (2) isn't better served by a backend API, and (3) wouldn't also benefit assistive technology if added to the accessibility layer.

Curious if anyone can produce one.

tools are tools.

hasn't world moved on from these things already?

Fair point. I won't submit here again until I've put in the work to make something that respects people's time to evaluate it. Lesson learned. :)

this is more like a quick test for python bindings, the zig files have tests within them for broad range of things.

thanks! :)

works now!

ΑΛΕΞΑΝΔΡΟΣ ΤΡΙΑΝΤΑΦΥΛΛΙΔΗΣ Καθηγητής Τμήματος Βιολογίας, ΑΠΘ

     ΝΙΚΟΛΕΤΑ ΚΑΡΑΪΣΚΟΥ
     Επίκουρη Καθηγήτρια Τμήματος Βιολογίας, ΑΠΘ

     ΚΩΝΣΤΑΝΤΙΝΟΣ ΓΚΑΓΚΑΒΟΥΖΗΣ
     Μεταδιδάκτορας Τμήματος Βιολογίας, ΑΠΘ





     Γονιδιώματα
     Δομή, Λειτουργία και Εφαρμογές