I’m working on a project that requires generating Section 508-compliant PDFs, and I’m using Telerik Reporting to build the accessible reports. However, I’ve run into a problem with how screen readers—specifically NVDA—are interpreting table content.
As soon as I set an AccessibleDescription on a cell (especially the first cell in a row), NVDA stops reading the rest of the row. It seems like the table reading order is broken, and the screen reader exits the table structure or skips over the remaining cells to go to the next row.
This is obviously a problem for users relying on screen readers, and I’m not sure how to fix it. Has anyone else dealt with this in Telerik Reporting, or know a workaround to make screen readers read both the custom alt text and maintain proper row navigation?