Auto-Generate Playwright Tests from Your GraphQL Schema [Testμ 2026]

At Testμ Conf 2026, New York Times Android engineer Vanessa Johnson presented a contract-driven accessibility approach that places accessible names, roles, descriptions, and spoken-content templates in a GraphQL schema through optional, additive custom directives. The approach is intended to reduce inconsistent client-side accessibility strings across web, Android, and iOS by making the schema a shared source of semantic intent while leaving each client responsible for implementing native accessibility behavior. A generator combines schema annotations with sample data to create JSON expectations and Playwright tests that validate the browser’s computed accessibility tree, alongside axe-core audits for broader automated checks. Johnson emphasized that this does not replace UI accessibility work or manual screen-reader testing, but helps detect drift between intended and rendered semantics in CI. She recommended beginning with a small number of high-traffic screens and reusable components, establishing shared terminology, and assigning cross-functional ownership across product, backend, and UI teams.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.