I use voice over because I like apple and use it. The voice over software comes with every apple product. I like how easy it is to work and it is built in.



Some but not many more are accessible.

Also I would say in general it’s not a make it or break it thing but more heading navigations or other things that are markers. I find I like headings. Label buttons and describe images. I don’t like meems that much say on reddit.

I feel this is yet another post that should be in the pinned topic of this redit

The absolute worst thing that anybody has ever put into websites, which there will be a horrible punishment for the developer of in the afterlife etc are date pickers that forgo the usual method of 'just type in the date' in exchange for a lovely all-singing all-dancing inaccessible calendar. I use jaws (and have nvda installed on my computer in case there's something that fails with jaws but works with nvda) and it's very rare I can get one of these things to work. Don't use them, advise everyone else not to use them and find a creative punishment that preferably involves fire for those who insist on using them.

Yes. WebAim found almost all of the top million home pages have accessibility issues, and I would guess that some pages of a website are likely to contain more serious issues. While they're not all problematic for screen reader users, some most definitely are.

I use JAWS because it has many features I require and better support for the applications I use.

>Web developers should consider accessibility from before they write their firstline of code for a website because it is much easier to create an accessible website than to shoehorn accessibility in retroacdtively. Web developers should become^ very familiar with WCAG 2.1, especially if no-one else is overseeing accessibility. I think that they should never offer accessibility features on their website that assistive technology and user agents can't provide; this would be things like magnification and color inversion.

To an extent. I only code individual HTML pages, not entire websites, and these pages are never shared beyond a small group of people who often convert them into other formats to read them. When I'm making accessible Word documents, the number of accessibility features I use depends on my audience.

I think that ARIA roles should be used when the standard HTML5 elements like <nav>, <main> and <footer> don't suffice, but when there is overlap between them, I think that the HTML5 one should be used.

So I used to use JAWS Job Access With Speech when I was first learning the Internet and computers. However, during university, I switched to VoiceOver and Apple. I believe I prefer the VoiceOver.

When I was first learning the Net, I would use it to research to find articles and E-books, one of the best websites for that was Project Gutenberg.

I found it difficult sometimes to search articles, because sometimes they were just scanned in images and so the screenreaders would not be able to read them and I would have to use further steps to convert the articles into a more legible format.

I hate images and memes, although some website administrators are getting better at putting in image tags, I find the Facebook image tags funny because all they can say is "three women and two men outside" which would not be enough information for me to know who was in the picture or where the picture was supposed to be.

[deleted]

Commenting here to remind myself to give you an answer later today.