WebMCP is a proposed browser-native standard that lets AI agents interact directly with web pages via predefined tools, removing the guesswork current AI automation relies on. While it promises efficiency gains — like context-aware filtering on e-commerce sites — it must not become a substitute for accessible web design. All parts of the loop (the webpage, the AI agent interface, and the WebMCP layer) must be accessible so users can take manual control at any time. The post warns against treating WebMCP as a 'conforming alternate version' that lets underlying pages remain inaccessible, and calls for disability advocates and accessibility specialists to be included in the standardization process. Practical barriers to testing the proposal — inaccessible demos and costly AI API tiers — are also flagged as issues that could exclude the very users whose feedback matters most.
Table of contents
Future beyond auto-fillHuman in the loop needs accessibility of the whole loopStandards in making need co-design or they may excludeTo conclude – WebMCP is not a replacement for accessible webpagesAuthor: Bogdan Cerovac1 Comment
Sort: