I just now realized why there are table of contents at the beginning of some blog posts. Sighted folk don’t have a way to jump to the first heading level 2 or 3 on the page, nor do they have the capability of bringing up a list of headings on the page and then jumping to a chosen heading the way we do. Gods, how do you all use such a limited form of navigation? I would think scrolling would get tiresome after a while.
If I sit here and think of all the ways that screen reader users can navigate easier around a web page than a sighted person, because the screen reader user can access more symantic things, it makes me actually want browsers that borrow how screen readers are able to extract and use symantic information. Like I think it would be cool to give you all the capability of jumping to a particular heading on the page, or the capability of extracting a list of links in the browser, things we have. The mouse just clicks and scrolls. How do you all handle such limited forms of navigation?#WebDev
If I sit here and think of all the ways that screen reader users can navigate easier around a web page than a sighted person, because the screen reader user can access more symantic things, it makes me actually want browsers that borrow how screen readers are able to extract and use symantic information. Like I think it would be cool to give you all the capability of jumping to a particular heading on the page, or the capability of extracting a list of links in the browser, things we have. The mouse just clicks and scrolls. How do you all handle such limited forms of navigation?#WebDev