if you are doing proper testing, you'll test with Jaws, NVDA, and VoiceOver since they all handle custom web controls differently. If you use HTML 5 correctly, stick with native form controls, proper data tables with headers, proper heading structure, use landmarks, put alt text in informative images and hide decorative images, don't use emojis everywhere, and stay away from custom JavaScript controls and widgets, you'll be fine. If you have to have JS all over the place, make sure it's all programmatically labeled, associated, and use ARIA where necessary.

Use aria-live for any dynamic text that appears on your site when users click or control something, don't use color as a sole means of identifying things, follow WCAG color contrast rules for text and graphics, and ensure your site also works on mobile using iOS VoiceOver and Google TalkBack. Make sure your site ,is responsive and can be zoomed without making users have to scroll left and right to read content. Keep things simple, concise, and in a good logical order, understanding that we screen reader users experience the web linearly through how the DOM is ordered. Just some basics for you. :) To answer your question, I'm a VoiceOver user.

JAWS, with a refreshable Braille display. No voice synthesizer.

I use jaws. A lot of people use NVDA because it's free but luckily I don't need to and I find jaws works a lot better for most things.

I would avoid modal windows, date pickers (just let people enter the date it's so much simpler) and if there's going to be a captcha then make sure there's a good audio test that actually works.

Strictly voice over here. Apple is great and I don’t use windows much. Honestly. Hoping to find a good ocr on mac and I’ll never use stupid windowsbox again.

Some valuable info here for sure but for a better over all look, try WebAIM.

https://webaim.org/projects/screenreadersurvey8/

I would also urge those responding here not to forget about Talkback since, you know, the 75% of the world who can't afford Iphone's has blind people in it too...

That said, it's totally understandable that a smaller company can't be expected to test on all the less commonly used screen readers and browsers, especially if the majority of their VI users don't fall into the category of those who might be using that certain combination.


https://jaketracey.com/a-developers-perspective-the-problem-with-screen-reader-testing/

I technically have access to all the 7 main screen readers, that being talkback, commentary, voiceover on both mac and iOS, narrator, JAWS, and NVDA.

My main screen readers, however, are voiceover on iPhone, and NVDA on windows. Despite having a legal JAWS license, despite it being a citizenship key, meaning it will never expire, NVDA works way better for most things for me.

UK does still heavily rely on JAWS and supernova, (don't have experience with the latter), don't really know why.

Something I hate? No headings, having to scroll forever, or do screen find to find the start of the article.\`

I use JAWS on my laptop, but I use VoiceOver for my phone.

One thing I really hate on websites is when they aren't separated into regions or they don't have a "main region." Like, at least put a "skip to main content" link!

Also, having alt text or image descriptions for graphics and images would be great.

NVDA and VoiceOver, on my PC and iPhone respectively.

Thanks for all the answers, it's disturbing to see people listing issues I would class as the bare minimum for projects like skip-to links and alt tags.

UK resident here. I know someone who uses $1, as does $1. Voiceover on iOS and ChromeVox also get used.

To find out more about the UK use of screen readers you might get some help from the RNIB https://www.rnib.org.uk/about-rnib/contact-us

A common problem with websites is that important parts of the page become invisible when viewed in a Windows High Contrast colour scheme, I think because of the fewer colours available.

Something to really hate?
- Lack of image descriptions.
- icons without alt-text
- Why have people started using emojis in email subject lines?