What's in this article:
- All things CAPTCHA explained with troubleshooting
- Anyone frustrated by or curious about CAPTCHA
Why are you requiring CAPTCHA?
At JSTOR, we are constantly making modifications to the platform to enhance features, improve performance, and better understand our users’ behavior and needs. This intermittent use of CAPTCHA is a way that we address robotic activity and excessive downloading.
Is CAPTCHA accessible?
Our CAPTCHA provides an audio CAPTCHA for those who need it. You will be asked to listen to an audio file and type the numbers you hear into a form field. If all else fails, please contact us.
It's not working though:
Certain programs and settings on your computer can prevent reCAPTCHA from displaying or functioning properly. Below are some things to try when you need to troubleshoot.
Cache and cookies
A good first step is to clear your cache and delete your cookies, which will give your browser a new lease on life. This walk-through will show you how to do just that for the Chrome, Firefox, Internet Explorer, and Safari.
Ad-blockers can be another source of CAPTCHA frustration--most play nicely, but a few don't. Luckily, you can turn off ad-blocker for JSTOR without disabling your ad-blocker across the board. Since we don't show ads, this won't change your viewing experience. To do this in AdBlock:
- Go to the AdBlock icon in the top right corner of your browser. It should look like a little stop sign.
- Click on the icon and select "Don't run on pages in this domain" in order to disable AdBlock across all JSTOR pages.
Still not working?
Other culprits can include your firewall or proxy settings, which are typically set by your institution's library IT department. If you've tried the above and are still experiencing issues, we recommend that you contact them. We'll be happy to work with them to troubleshoot further.
In the meantime, you can submit your PDF request to firstname.lastname@example.org