Why? What does it add that accessibility features don't cover? And of there's a delta there, why have everyone build WebMCP into their sites rather than improve accessibility specs?
Because, thinking bigger picture, having an AI assistant acting on your behalf might be more effective than slow navigation via accessibility features?
I get the wider point that if accessibility features were good enough at describing the functionality and intent then you wouldn't need a separate WebMCP.
So what does WebMCP do that accessibility doesn't?
Seems to me, at cursory reading, it's around providing a direct js interface to the web site ( as oppose to DOM forms ).
Kind of mixing an API and a human UI into one single page.
Because, thinking bigger picture, having an AI assistant acting on your behalf might be more effective than slow navigation via accessibility features?
I get the wider point that if accessibility features were good enough at describing the functionality and intent then you wouldn't need a separate WebMCP.
So what does WebMCP do that accessibility doesn't?
Seems to me, at cursory reading, it's around providing a direct js interface to the web site ( as oppose to DOM forms ).
Kind of mixing an API and a human UI into one single page.