# Discourse with a screen reader **URL:** https://meta.discourse.org/t/discourse-with-a-screen-reader/178105 **Category:** UX **Tags:** accessibility, screen-reader **Created:** [February 2, 2021, 1:17pm UTC](https://meta.discourse.org/t/discourse-with-a-screen-reader/178105 "2021-02-02T13:17:53Z") **Posts on this page:** 1 **Showing post:** 59
### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam) #### Post date: [May 27, 2021, 10:40pm UTC](https://meta.discourse.org/t/discourse-with-a-screen-reader/178105/59 "2021-05-27T22:40:31Z")
> [@nolan](#): > > I concur about the topic list headings being a bit odd. I think I’d prefer it if the headings just bracketted the absolute essential details, since if I want the rest, I know where to get it. At the moment we have the ARIA heading role on the entire row. I will move it so it is only on the essential information, the first column of the big table. (status, title, category, unread count and so on). Should I go a step further and just put the role on the topic title only? I guess this does make stuff a big faster as long as you remember to navigate left and right for information about topic status, category and so on. @celtichawk thanks! @j.jaffeux is option for a solution for dropdowns that should be compatible across JAWS, orca and NVDA. As I mentioned, it may take a bit of time, but we are working on it right now and hope to have something to show you in the next few weeks. @ethindp I think I have an idea for the header situation in topics. We can put the header role on a single element like “username” and then give it an aria description of “Sam posted 3 hours ago”, then I guess it would say: “Post #3 region Sam posted 3 hours ago” as you h through stuff. Should we try this? --- _[View the full topic](https://meta.discourse.org/t/discourse-with-a-screen-reader/178105)._