429 Too Many Requests and client‑side pagination hinder accessible navigation in Cosmos DB SQL queries
0 reputation · 05 Apr 2024, 08:29 UTC
The Cosmos DB SQL API returns a 429 Too Many Requests response when request‑unit throttling occurs, and large query result sets are delivered via client‑side continuation tokens rather than server‑side paging.
Because continuation tokens must be managed by the client, screen‑reader users experience unpredictable navigation and potential data staleness, especially when the default consistency level is Session or Eventual, which can serve outdated information to assistive technologies.
Improving accessibility therefore requires true server‑side pagination for SQL queries, a mechanism that reduces client handling complexity and mitigates 429 throttling impact. How can Cosmos DB introduce server‑side pagination without breaking existing SDK behavior? What accessibility guidelines should govern continuation token handling for screen‑reader users? Is there a recommended approach to minimize request‑unit consumption while paging large result sets?
