Five role-specific accessibility agents (front-end, back-end, mobile, design, PM) backed by the Stark Continuous Accessibility platform.
Each skill knows what its role owns — HTML/ARIA fixes, SSR markup, native mobile accessibility APIs, design tokens, or compliance posture — and can read live violations or set up new scans in your authenticated Stark workspace.
MCP connector Server URL https://mcp.getstark.ai/mcpCopy Login OAuth Tools Reads data6 get- get- get- get- list- list-
Changes data7 create- create- create- create- create- create- create-
Skills 5 in the Claude listing
Stark backend This skill should be used for server-side accessibility work — whenever the user is dealing with accessibility concerns that originate on the back end: missing or wrong `lang` / document metadata, ser Stark design This skill should be used for design-stage accessibility work in Figma or Sketch — whenever the user mentions "contrast", "color contrast", "color blindness", "design accessibility", "Figma accessibil Stark frontend This skill should be used for web front-end accessibility work — whenever the user mentions "accessibility", "a11y", "WCAG", "ARIA", "screen reader", "keyboard navigation", "focus management", or "sem Stark mobile This skill should be used for native mobile accessibility work — iOS (UIKit/SwiftUI), Android (Views/Compose), and cross-platform frameworks (React Native, Flutter). Stark pm This skill should be used for accessibility program and project management — whenever the user asks where they stand on accessibility, about compliance status against WCAG / Section 508 / EAA, how to 
