Ory Kratos recovery flow ↔ Screen reader compatibility: What adjustments ensure keyboard navigation consistency across identity providers?
0 reputation · 23 Sept 2023, 07:10 UTC
Accessibility in Ory Kratos Recovery Flow
The Ory Kratos self‑service recovery flow is intended to allow users to reset passwords or recover accounts, but the default HTML templates provide minimal accessibility support. Keyboard navigation through form fields, links, and buttons may be inconsistent, especially when different identity providers are chained into the same recovery sequence.
Customizing the recovery templates is the only way to add semantic HTML and ARIA attributes, yet it is unclear how to guarantee that these adjustments will work uniformly across all supported identity providers. The interplay between provider‑specific templates and the core recovery flow can introduce focus order regressions and screen‑reader confusion.
To move forward, we need to understand the exact constraints and best‑practice patterns for this integration.
- How can we guarantee that the recovery flow’s form fields are reachable via Tab order across all identity providers?
- What ARIA roles or attributes should be added to the recovery form to aid screen readers without breaking provider‑specific customizations?
- Are there recommended patterns for ordering links and actions in the recovery flow to maintain focus consistency?
