On a Mac, all screen reader commands require the user to hold down a special key combination (usually command + option), leaving all other keystrokes free for the OS and web browser. If a Windows user wants to pass keystrokes on to the browser, they must indicate this by placing the screen reader into a specific mode. Only if the keystroke is not a screen reader command, will it be passed on to a website. By default, Windows screen readers will intercept every keystroke a user makes, and attempt to interpret it as a command. Mac and Windows screen readers are also slightly different. For example, swiping left or right with a single finger, always moves to the next or previous element on the screen. On mobile, screen readers define special touchscreen gestures instead of keyboard commands. On desktop, a screen reader user may navigate by using the tab key, arrows, or other shortcut keys on the keyboard.
Mobile screen readers are quite different from desktop screen readers. Things that change from platform to platform If you have not provided this semantic information, screen reader users will become confused. For example, all screen readers allow users to skip directly to the next and previous heading or the next and previous link/button. They provide shortcut keys to make navigating easier: Shortcuts help users to quickly navigate using the semantic structure of a website.Making sure focus is managed correctly, and tab order is set up properly, helps give the screen reader a linear pathway to navigate your website. While a sighted person can glance at a screen and understand content as a whole, someone listening to a screen reader cannot. They read content in a linear fashion: Screen readers generally read out the contents of the screen using text to speech.For this reason, alt-text on images, and labels on icons, are crucial.
0 kommentar(er)
