UI & UXServer Driven Accessibility: Embedding UI Semantics Into Your GraphQL Schema
Server driven UI shouldn’t ship only layout and copy, it should ship accessibility semantics too. This talk shows how to embed a11y hints (labels, roles, states, live regions) directly in your GraphQL schema using directives, so clients render accessible components by default. We’ll design a small directive set, map it to Android Compose semantics and Web ARIA, and add lightweight contract tests that watch the schema for regressions (e.g., a required label removed). You’ll leave with a directive catalog, client side mapping patterns, and a rollout checklist that lets platform teams make a11y a server driven contract not an afterthought.
Takeaways:
- A copy ready @a11y directive set + examples
- Patterns to map schema semantics -> Compose/ARIA
- Contract test rules to catch regressions in CI
talkDetail.whenAndWhere
Takeaways:
- A copy ready @a11y directive set + examples
- Patterns to map schema semantics -> Compose/ARIA
- Contract test rules to catch regressions in CI
Vanessa Johnson
talkDetail.shareFeedback
talkDetail.feedbackNotYetAvailable
talkDetail.feedbackAvailableAfterStart
talkDetail.signInRequired
talkDetail.signInToFeedbackDescription
occupancy.title
occupancy.votingNotYetAvailable
occupancy.votingAvailableBeforeStart
talkDetail.signInRequired
occupancy.signInToVoteDescription
comments.speakerNotEnabledComments