Inclusive APIs: How to Extend OpenAPI for Accessibility
summary
Claims that adding a small set of API-level fields to OpenAPI lets backends drive accessibility so UIs and assistive tech behave consistently. Uses OpenAPI/JSON schema extensions to carry alt text, live-region mapping, aria-like labels, error-to-announcement mappings, focus hints, grouping and navigation links. Includes concrete examples: product-listing and shopping-cart flows where HTTP status codes map to screen-reader announcements and focus changes. Prototype examples show the UI can be automated from the API and improves screen-reader output without front-end guessing.
AI-written summary · about
chapters (12)
- 0:00Digital accessibility in APIs
- 2:00Who is Patrick and Amadeus context
- 3:06Consumer needs and assistive tech
- 6:13Server-level accessibility extensions
- 7:17OpenAPI and accessibility mind types
- 10:00HTTP status codes to live regions
- 12:21Accessible data table example
- 15:41UI focus and grouping concepts
- 17:53API navigation flows and states
- 20:50Product navigation in cart
- 21:11Accessibility in UI workflows
- 22:31Benefits for designers and standards
related talks
21mWhat if Your API Spoke Accessibility?
21mDesigning APIs with OpenAPI: Build the Right APIs the Right Way.
39mAPI Development in 2017
21mAPI Discovery done right: Engaging the right people with your APIs.
35mDocumenting APIs: new era, same craft
19mUnlocking API Opportunities: Best Practices for Corporations
31mUnifying OpenAPI & AsyncAPI : Designing JSON Schemas+Examples.
17mAPI Security Simplified: Practical Tips & Tools