[caesar] Considering NVDA ignores most symbols but JAWS doesn't, what's everyone's recommendation for how to code a piece of text like "250+" or "* indicates a mandatory field" without having to resort to converting it into text (due to space constraints)?
[caesar] E.g. "Fields marked with an asterisk (*) are mandatory" would result in asterisk being duplicated in JAWS
[caesar] And for 250+ putting "plus" offscreen will make JAWS read 250 plus plus.
[caesar] Not to mention I wouldn't be able to convince anyone that 250-plus would actually be preferable to "250+"
[caesar] Figured out my NVDA problem at least. The voice settings had Symbols set to "none" although that's weird since I've never modified the default settings...
[callumacrae] Hello :) I've been googling this for a while but have only managed to find articles complaining about this and not people actually suggesting solutions - how do you make sure a single page web app works well for a user with a screen reader?
[herin] I'm not very skilled with the technology itself. But, from some of the speakers from various applications I understand that as long as the Page structure, Titles, navigation mechanism, Focus, if there are any live upating regions proper use of ARIA would help to meet the accessibility
[crazycatlena] Hi everyone, I may have to work on a project with Bootstrap 2.3 (with Liferay) and we need to be WCAG AA compliant. Do you know some articles or resources where I can find examples of accessibility issues on it?
[crazycatlena] I just found some issues about contrast and using the <i> to use icons
[conley] hey @crazycatlena check out #a11y-devtools
We have a skip link to a main element. The main element has a tabindex="-1" because I thought that was an issue with Chrome and IE. For some reason it seems to be getting focus on click. Is this a known bug that I just can't find in Google?
[marcysutton] Nope it's entirely the tabindex. Are you worried about the outline? I just addressed this problem by using the What Input library, it allows you to style focus more deliberately https://github.com/ten1seven/what-input
...Until we have :focusring in the standards track
[marcysutton] You can also do this: [tabindex="-1"]:focus { outline: none } but I'd argue the outline is useful for focus management. Hence the library usage
[ianmcburnie] you could set a ‘temporary' tabindex of -1 on the main element using javascript when the skipto link is activated. then remove the tabindex on blur event of main element. this way, clicking the main element with mouse will not set focus to it.