I'm doing some accessibility testing on my company's website. I have been doing the majority of the screen reader testing using Mac's VoiceOver tool, paired with Chrome. For the most part, it has worked, however, today I added some ARIA labels and roles to a custom element (built mostly with divs), and it only seems to work in Safari...
Has anybody else ran into this issue? Any ideas on if there's a fix or workaround so it works on any browser?
If my scenario isn't clear enough, please let me know and I will provide more information/details. Thanks!
Firefox for Windows, Linux, Android, and iOS all work with the popular and included screen readers on those platforms, but macOS screen reader support has been absent. For over a year the Firefox accessibility team has worked to bring high quality VoiceOver support to Firefox on macOS.
Turn your screen reader on or offVoiceOver: Use Command + F5. Chromevox: Use Ctrl + Alt + z.
VoiceOver can also be enabled by going to System Preferences > Accessibility > VoiceOver and selecting Enable VoiceOver. The VoiceOver Activation keys (called VO keys) are control + option . These keys are used to access special VoiceOver commands and functions and will be referenced simply as VO .
VoiceOver—Use Command + F5. Chromevox—Use Ctrl + Alt + z.
The answer is more likely to be the opposite of how you phrased the question.
Does Mac VoiceOver limit its functionality on Chrome / Firefox?
Generally, no. Web developers often assume the screen reader is the problem, but it's often the web browser's implementation that is lacking. When HTML and ARIA semantics are conveyed as expected with one browser, but not with another browser, using the same operating system and screen reader, this usually points to a difference in the browser's implementation.
Screen readers don't read web pages directly. Instead screen readers (and other assistive tech) communicate with web browsers (and other native applications) via an accessibility API provided by the operating system. The screen reader can only report what it has been told by the web browser. Web browsers need to pass the accessibility metadata to the operating system, which in turn is available to the screen reader. Firefox in particular is does not work well with the macOS accessibility APIs.
WCAG uses the term "accessibility supported" to describe this. Basically, these ducks must all be in a row:
That said, some screen readers like JAWS can hook directly into the browser process, because historically that was the best way to do things, before the accessibity APIs were developed. I've heard that some assistive tech may engage custom behaviours as workarounds for browser bugs, but I can't provide a citation for a good example. Looking to the future, the proper way is the use of OS-level accessibility APIs, which OS vendors may enforce at some point. Screen readers do have user-script capabilities, and some vendors distribute scripts (hacks) to enhance particular websites.
Further information:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With