By Jennie Delisi, Accessibility Analyst

If you don’t want a web browser to remember your activity, you can browse the web privately. Google Chrome calls this Incognito mode. Many browsers have this capability, but they call it different names:

• Edge: InPrivate browsing. 
• Firefox: Private window/Private browsing. 
• Safari: Private browsing.

Some people only think about this when they don’t want the websites they visit stored in their browsing history. Accessibility testers can use incognito and private browsing modes to save time. That way you don’t have to clear your cookies and cache each time you start a test session. Before you start using extensions in private browsing modes you must think through how this impacts information security. 

Think About the Data

“A private browsing window can’t erase the records of your visit from a website’s servers, or from any networks you went through to get to a site,” writes Nicholas Deleon. This also applies to any accessibility testing extensions you want to use. Each extension or app shares information about how they store data regardless of whether you use private browsing. 

If your accessibility testing extension stores data in any way do not use protected information without permission from your project team. In short, while your browser may be in incognito mode, your app or extension may not. What is protected information? This depends on the definition used by your agency or company. It could include: 

• Sensitive information about people (like birth dates or social security numbers).
• Information available only to a small number of people within an organization.
• Information not publicly available.

Talk to Your Project Team

Work with your project manager, digital security professional, and others on the team. Determine if your test plan can use extensions and private browsing.

Only Use It Temporarily

If you decide to use private browsing and extensions, make a plan. Turn off  “Allow in Incognito” or “Allow in private browsing mode”  when you finish each test session. Set a reminder so you don’t forget.

Other Options

The security of data must be part of the test plan. If your project team does not approve private browsing and extensions because of data security, there are other options. Your project team and requirements may prefer to use more manual testing methods. The project team can work together to determine options for quality accessibility testing. It’s easier to include these considerations at the beginning of a project plan.

Talk to Your Digital Accessibility Coordinator

When you need to use testing tools, your accessibility coordinator can help! State of Minnesota employees can reach out to their coordinators. They can let you know: 

• Options for your test plan.
• Training available on specific testing tools.
• The contact at your organization who can help.

Enabling Extensions for Incognito/Private Browsing Use

Turning on private browsing mode usually disables extension access. To use an extension in private browsing mode you must enable it for that extension.

Chrome

Open your Chrome extensions.

Find the extension you want to use in Incognito Mode. Select the Details button. 

Review the warning in the “Allow in Incognito” section. If this meets your requirements, enable it using the toggle for that section.

Open a new Incognito Window (Ctrl + Shift + N). Your extension should now be available. Don’t forget to return to the permissions page and turn off the toggle when finished. 

Other Browsers

Other browsers use similar methods for private browsing settings. 

• Go to the extension settings. 
• Open the details for the specific extension.
• Find the option to turn on Private Browsing mode.
• Open a private browser window and use the specific extension while testing.
• Return to the extension settings – details and turn off the “allow in private browsing” option.