Live region markup is a complex area which is somewhat open to interpretation. Mozilla guide talks about striking a balance. Users will have their favorites, which is another reason that developers shouldn’t test their content in a single computing environment. Someone who’s adept at Apple’s VoiceOver may encounter a learning curve when switching to Android’s TalkBack. Not all screen readers are compatible (or as compatible) with every operating system, browser, and app, and user interfaces can differ considerably. Myth 4: All screen readers are exactly the same The result was that they had different rules. When I started making my sites accessible, I downloaded a few addons (to simulate a reader) and a few readers. Would love to get some insight on this, thank you. I also tried switching places between and, to get a similar result and it also messed up the design.įollow-up: Could it be that their reader is just not working well? I had that suspicion How can that be? there is only one element. Surprisingly, the screen reader still has the same problem. With css handling the break lines with the property 'white-space: pre-line ' applied to element.

'link - some headline', and then 'link - info1' and so on.Īfter reading some about accessibility, I decided to not use the element, since it causes problems in screen reading. I'm happy with the design itself (visually) and want to stick with it. There are 7 links, each of them in their own hoverable box, and in each box there is text,Ī headline and about 3-4 lines of more details. I have sent the site i'm working on to someone who checks whether its accessable or not, and the test came back with a reject regarding some links in the site.

Accessibility screen reader for android