# Accessibility software and discourse **URL:** \ **Category:** Feature\ **Created:** [13 Março , 2014 22:14 UTC](https://meta.discourse.org/t/accessibility-software-and-discourse/13711 "2014-03-13T22:14:08Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![MarcoZehe](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@MarcoZehe](https://meta.discourse.org/u/MarcoZehe)\ **Post date:** [5 Maio , 2015 17:55 UTC](https://meta.discourse.org/t/accessibility-software-and-discourse/13711/24 "2015-05-05T17:55:39Z")
Hi folks! As @stevefaulkner said, using the title attribute is not desirable for many reasons for screen reader users. In the example of the notifications, putting a concise text bit in either an aria-label attribute on the href element or as a child of that in the form of a span with text that is positioned off-screen so only screen readers can read it, would be much much better. The same goes, for example, for all the buttons except the Reply button to any post. So the Like, Bookmark, etc. buttons below each post don’t get their function spoken by screen readers automatically, either. Only the title attribute conveys some information, but you usually have to press an extra key to read that. As the article linked by Steve points out: The title attribute has been abused so badly over the years that screen readers and browsers simply don’t rely too much on it any more when calculating what we call the Accessible Name of any element. So alt, aria-label or using hidden text are the preferred ways to name elements. To see how hidden text can be accomplished, see, for example, [here](http://unobfuscated.blogspot.de/2015/01/updated-offscreen-techniques.html). I would really like to see this improved in Discourse, since this is one of the major pain points I have myself. However, I do know nothing about Ruby and thus would have a very steep learning curve when trying to fix this bug. However, if someone else volunteers to fix the bug, I will be happy to review the proposed change before a PR is merged. I can see from looking at code if it does the right things (most of the time), I only cannot implement this myself. --- _[View the full topic](https://meta.discourse.org/t/accessibility-software-and-discourse/13711)._