how to do a screenshot on a Google sheet
Betsy Grenevitch
I have been asked to do a screenshot on a google form to show the person the headings are missing. What are the steps?
Thanks.
Betsy Grenevitch 678-862-3876
Sarah Alawami
you can use the snipping tool.
get to the form.
press the print screen key. if the snip tool comes up tab to new screenshot or press control plus N
choose the window option in the combo box
now tab to the button where your document is and press space. The screen cap should be saved where ever you screen caps are saved. Access that folder via the game > screenshot and video section under settings. I changed mine so I forgot where the default is.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/d5a2a664-a86a-4e35-82b2-63a43585346c%40gmail.com.
Snehashish Mahato.
Alternatively, another substitute way could be pressing Alt+Printscreen while in Sheets. After that, if NVDA+C is pressed and an announcement like, ‘There is no text on the clipboard, but the clipboard is not empty,’ is heard, then it confirms that the screenshot has been copied to the clipboard. Then, ‘Paint’ can be opened to save that to the desired location.
I have always been doing it this way. So, Sarah, do you have any idea about what other differences exist between taking a screenshot via the snipping tool and directly copying that to the clipboard to paste manually, aside from the difference in time consumption?
Snehashish.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/85a6bc6d-0b73-4221-a198-c58f362672fb%40gmail.com.
Sean Randall
Betsy Grenevitch
thank both of you for such clear directions. I have written them down and will try to do this in the next couple of days.
I am always afraid to try something new. I have learned that the only way to learn new things on my laptop is to try them and realize I may fail the first couple of times but it is a learning process so much like a toddler learning to walk. It takes determination.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CALm5GvkwehYrz%3DrnjJy5BXiQpnEBMp18NczBQusRy9aAebnE3A%40mail.gmail.com.
Betsy Grenevitch 678-862-3876
Mister Kayne
Hi Betsy,
While the technical methods for capturing screenshots shared by Sarah and Snehashish are helpful for general documentation, I would like to offer a different perspective regarding the goal of your request.
Respectfully, I believe asking for a screenshot to "prove" that a Google Form lacks headings is an ineffective way to address the issue. A screenshot only shows the visual layout; it does not reveal the underlying semantic markup. A form might look perfectly structured to a sighted user while lacking the necessary heading tags for screen reader accessibility.
As a best practice for inclusive design, the burden of verification should remain with the developer or the person maintaining the form. They can easily verify the heading structure by:
1. Using Accessibility Audit Tools: Running an automated scan (like Axe or Lighthouse) on the page.
2. Inspecting the Source Code: Directly checking the HTML to see if the relevant text elements are wrapped in <h1> through <h6> tags.
3. Conducting a Screen Reader Walkthrough: Using a screen reader to confirm if the expected navigation structure is present.
If you are communicating this to a developer, it may be more effective to simply inform them that, "The form currently does not have a recognizable heading structure when navigated via a screen reader, which hinders efficient navigation for Persons with Disabilities." They should have the tools to verify and fix that on their end without needing a visual capture.
Warm regards,
Mister Kayne
Author: The Somebody, Nobody, Anybody & Everybody Blog!
Mail: writ...@mister-kayne.com
Betsy Grenevitch
Thank you. This make more sense to me.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/02f101dcff3b%2407a305f0%2416e911d0%24%40mister-kayne.com.
Betsy Grenevitch 678-862-3876