[madeofpalk]

One thing I also notice when seeing issues like this is that this is also a problem with both the assistive tools themselves, and the accessibility APIs and methods available to build web pages.

I don't think there's anything inherently wrong with building content and feature rich websites, but when we do it is difficult to build them in a way, with or without javascript, that's also useful to browse through screen readers. We have to resort to hacks like skip link hacks and the rest.

I think not only do we have to get better at building accessible web pages, but the technology needs to get better to make building accessible web pages easier and more usable.

[extra88]

Skip links are mainly for people who don't use a screen reader but do solely operate the computer by keyboard (or keyboard emulator, like a switch). Screen reader users shouldn't need skip links because page content should be organized within landmarks (header, main, search, footer, etc.) and have headings identifying different parts of the page and their logical hierarchy, the screen reader gives them tools to list and move to those semantic structures.

[madeofpalk]

This is actually one of the exact 'features' I was thinking should be there. I guess this might be due to my inexperience with these tools (my problem!) but I've never experienced, or figure out how to, jump between the landmarks with VoiceOver.

[extra88]

In VoiceOver on a Mac, one way I know is to press VO-U to open the Web Rotor then use the left-right arrow keys to navigate through the options, one will list landmarks if they are present on the page.

I don't recall how to call up the Web Rotor on iOS devices.