
Accessibility with google docs
I've been trying to use the "Accessibility" -> "verbalize screen reader" on Google Docs, but it won't let me use the verbal functions. I have tried to download reader extensions in hopes that it would read the Google Doc, but it's not working. I have restarted my computer, the Accessibility is on, and tried to contact Google to see if it's an issue on their end but most of the information is only applicable for Chrome. I also tried to use "verbalize screen reader" on Chrome, and it is also not working there. If anyone knows how to use the Accessibility with Firefox and not Chrome, please help me navigate this. I have tried several Firefox extensions and none of the Text-to-Speech are working with google docs. I don't know why there aren't any, but suggestions would be appreciated.
All Replies (4)
Using accessibility features like screen readers and text-to-speech in Google Docs can sometimes be challenging, especially when trying to use them in different browsers. Here are some steps and suggestions to help you navigate this issue in Firefox and provide alternatives if needed: 1. Use Built-in Screen Reader Support
If you are using a screen reader (like NVDA or JAWS), ensure that it is properly configured to work with Firefox. Most screen readers should work with Google Docs, but you may need to adjust settings or ensure that the screen reader is running before you open Firefox. 2. Check Firefox Accessibility Settings
Make sure that accessibility features are enabled in Firefox:
Open Firefox and type about:preferences#general in the address bar. Scroll down to the "Accessibility" section and ensure that the relevant options are checked.
3. Use Firefox Reader Mode
Firefox has a Reader Mode that simplifies web pages and can make them easier to read. While it may not work directly with Google Docs, you can try copying the text from your Google Doc and pasting it into a new tab in Reader Mode:
Open your Google Doc. Select the text you want to read and copy it (Ctrl + C or Cmd + C). Open a new tab in Firefox and paste the text (Ctrl + V or Cmd + V). Click on the Reader Mode icon (it looks like an open book) in the address bar to enable Reader Mode.
4. Use Third-Party Text-to-Speech Extensions
If you want to use a text-to-speech extension, here are a few popular options that may work better with Google Docs:
Read Aloud: This is a popular text-to-speech extension that can read text from web pages, including Google Docs. You can install it from the Firefox Add-ons site. Natural Reader: Another text-to-speech tool that can read text from various sources.
After installing an extension, make sure to follow the instructions provided by the extension to use it effectively. 5. Use Google Docs with Chrome
If you continue to have issues with Firefox, consider using Google Docs in Chrome, as it is optimized for Google services. If you have accessibility needs, Chrome has built-in support for screen readers and other accessibility features that may work more seamlessly with Google Docs. 6. Use Operating System Accessibility Features
Both Windows and macOS have built-in text-to-speech features that can read text aloud:
Windows: Use the Narrator feature. You can enable it by pressing Windows + Ctrl + Enter. macOS: Use the VoiceOver feature. You can enable it by pressing Command + F5.
7. Contact Support
If you continue to experience issues, consider reaching out to the support team for the specific screen reader you are using or the Firefox support community for more tailored assistance.
1. NVDA wasn't able to provide me with the accessibility that I needed and rather hindered my work. JAWS won't allow me to use it in my firefox for some reason as it stays grey-toned and unable to be clicked on. 2. I went to the about:preferences#general in firefox and there is no "Accessibility" on the page. Perhaps things have changed but if you could please double check. I even checked in the search bar and it says that there is Accessibility anywere in the firefox settings. 3. I'm trying to edit as I listen and using the Firefox Reader Mode makes that impossible. The suggestion you offer is feasible I was hoping that firefox would at least be a little more kind to users that need special accessibility without having to take extra time that could be going back into my work. 4. Again these extensions do not provide the usage that I need. Read Aloud pops up in a different page and doesn't let me edit. And Natural Reader also requires that I pop into a new page which is equally as unhelpful. 5. I don't use Chrome. I use Firefox. Also the Accessibility isn't working in Chrome for me either so the point is mute. 6. The Operating System Accessibility doesn't work on google docs as far as I was aware. I tried and it never read my works. 7. Can you tell me how to contact support. I have been going around in circles trying to get an answer.
1. Accessibility Settings in Firefox
As of my last update, Firefox does not have a dedicated "Accessibility" section in the preferences. However, you can enable certain accessibility features through the following steps:
Keyboard Shortcuts: Firefox has built-in keyboard shortcuts that can help with navigation. You can find a list of these shortcuts in the Firefox support page. Reader Mode: While you mentioned that Reader Mode isn't suitable for your needs, you can toggle it on and off using the F9 key. This might help you access content in a more readable format without distractions.
2. JAWS Compatibility
If JAWS is not functioning correctly with Firefox, ensure that you have the latest version of both JAWS and Firefox. Sometimes, compatibility issues arise with updates. You can also check the JAWS documentation or support for specific settings that may need to be adjusted for Firefox. 3. Contacting Firefox Support
To get direct support from Mozilla, you can use the following methods:
Mozilla Support Forum: You can post your question on the Mozilla Support Forum. This is a community-driven platform where you can get help from other users and Mozilla staff.
Bugzilla: If you believe you have encountered a bug or an issue with accessibility, you can report it on Bugzilla. You will need to create an account to file a bug report.
Twitter: You can reach out to Mozilla on their official Twitter account @Mozilla for quick questions or support.
Email Support: While Mozilla does not provide direct email support, you can use the support forum or Bugzilla for more detailed inquiries.
4. Alternative Accessibility Tools
If the built-in tools and extensions are not meeting your needs, consider exploring other third-party accessibility tools that may work better with Firefox. Some users have found success with tools like:
Speech Central: This is a text-to-speech app that can read web pages and documents aloud. It may offer better integration with your workflow.
VoiceOver (macOS): If you are using a Mac, the built-in VoiceOver feature can provide robust accessibility options.
5. Operating System Accessibility
If you are using Google Docs and the operating system's accessibility features are not working as expected, ensure that you have enabled the necessary permissions for the screen reader or accessibility tool you are using. Sometimes, specific settings need to be adjusted for compatibility.
1. Thank you for the suggestion, but yes this does not help me at the moment. 2. I update my firefox and it is still not working. Are you talking about the "JAWSInspect"? I have emailed their contact support to see if anyone can answer me there but I'm not too hopeful. 3. Isn't this the Forfox support forum? I have now tried to email Bugzilla and see if they offer any insights. I am also tweeted @Mozilla for any advice though I doubt I shall get a response either. The last suggestion you have is to email Bugzilla which I have stated that I have tried and shall wait for a response. 4. Speech Central does look promising, however it is requiring payment which I cannot spare at the moment. I am not using mac, I have a windows so I can't use VoiceOver. 5. My permission are allowed for accessibility. I checked my tools in google docs and everything so I don't know what else could be mishandling it. If you have any suggestions where I can look, that would be appreciated.