Assistive technology guide, ClaroRead for Windows testing steps

We’ll take you step by step through how to test a component or feature with ClaroRead reading solution for Windows. Test with the latest version available.

How to turn ClaroRead on / off

To test with ClaroRead on Windows, use the 'ClaroRead Chrome' web extension. This is not installed by default.

  1. To check if you have the 'ClaroRead Chrome' extension already installed on your device, in Chrome go to 'Settings', then under 'Extensions', look for 'ClaroRead Chrome', you should see the extension, make sure it's turned on.
  2. If you can't see the extension, download 'ClaroRead Chrome' from the Chrome Web Store. After download, check the extension is turned on, in Chrome go to 'Settings', then 'Extensions'.
  3. To start using ClaroRead, in the extensions toolbar (to the right of the address bar in Chrome), click the 'ClaroRead Chrome' icon (speech bubble with a star in it). When ClaroRead is open, the ClaroRead toolbar will be displayed on screen. Note the ClaroRead toolbar will not be displayed when viewing the Chrome extensions page.
  4. To exit and close ClaroRead, in the ClaroRead toolbar, click 'Close'.
Back to page contents

Testing in a foreign language

When testing with assistive technology it's important to test with content in a language that you can understand and with a language that is supported by the assistive technology. For further information see the assistive technology testing in a foreign language guide.

ClaroRead supports 30 languages, to select a foreign language voice:

Back to page contents

Testing steps

We’ll take you step by step through how to test a component or feature. Following the same steps every time, ensures that everyone is testing using the same methods and using the most common techniques. The steps also enable anyone, in any role, to use ClaroRead for the first time.

To become more familiar and proficient using assistive technology, resist the temptation to cheat, always try to navigate like a user would.

As you go, make notes of any bugs you find.

Step 1 - Open Chrome

Open Chrome, this is the most used browser by ClaroRead users.

Note: ClaroRead will work with other browsers, such as Firefox, though always test in the most used browser.

Back to steps

Step 2 - Go to the testing url

Navigate to or type in the testing url, then scroll the page until you can see the component you're going to test.

Back to steps

Step 3 - Turn ClaroRead on

  1. In the extensions toolbar (to the right of the address bar in Chrome), click the 'ClaroRead Chrome' icon (speech bubble with a star in it).
  2. The ClaroRead toolbar will be displayed on screen.
  3. If testing in a foreign language, select a foreign language voice.

See how to turn ClaroRead on / off for more detailed instructions.

Back to steps

Step 4 - Promo components

Promo's usually have a large clickable area, this can sometimes make selecting or clicking content to read aloud difficult. For promo components, check the content can be read aloud using the following method:

Hover to read: In the toolbar, go to 'Settings', then under 'Speech', check 'Speak under mouse' is selected. Now hover the mouse cursor over the promo content and hear it read aloud. Check all content is read aloud, such as links, text and images. Note, if the promo is comprised of more elements than a text link, such as an image or timestamp, if the link text is the only content to be read aloud, this is likely due to the way that the code that is used to create the large clickable area works. This is acceptable when hovering to read, for this type of content, as this tool is primarily used for reading long form content e.g. paragraphs of text.

Promo components bug examples
  • When I hover to read, link content is not read aloud.
  • When I hover to read, nothing is read aloud.
  • Content I can't see is read aloud. This tool will read content that is hidden, such as visually hidden text for screen reader users. If this happens, verify if hidden content is being read by inspecting the code and looking at the component's HTML. If you can see the hidden content that was read aloud, this is acceptable.
  • Non text content, such as an icon, is not read aloud. Use your judgement to decide if it's acceptable if non text content isn't read aloud. Images with alt text are expected to be read, though note this tool is primarily used for reading long form content e.g. paragraphs of text.
Back to steps

Step 5 - Other components

Check the content can be read aloud using the following methods:

  1. Hover to read: In the toolbar, go to 'Settings', then under 'Speech', check 'Speak under mouse' is selected. Now hover the mouse cursor over content and you will hear it read aloud. Check all content is read aloud, such as links, text and images.
  2. Select to read: In the toolbar, go to 'Settings', then under 'Speech', check 'Speak when mouse selects' is selected (this is usually selected by default). Now select links, text or other types of content such as images, when the mouse is released you will hear the content read aloud. Check all content is read aloud, such as links, text and images.
  3. Click to read: In the toolbar, go to 'Settings', then under 'Speech', check 'Click and play' is selected (this is usually selected by default). Now click text or other types of content such as images, when the mouse is released you will hear the content read aloud. Check all content is read aloud, such as text and images. Note, actionable elements, such as links and buttons, maybe difficult to read aloud with this method.
Other components bug examples
  • When I hover to read; link, text or image content is not read aloud.
  • When I hover to read, nothing is read aloud.
  • When I select to read; link, text or image content is not read aloud.
  • When I select to read, nothing is read aloud.
  • When I click to read; text or image content is not read aloud.
  • When I click to read, nothing is read aloud.
  • Content I can't see is read aloud. This tool will read content that is hidden, such as visually hidden text for screen reader users. If this happens, verify if hidden content is being read by inspecting the code and looking at the component's HTML. If you can see the hidden content that was read aloud, this is acceptable.
  • Non text content, such as an icon, is not read aloud. Use your judgement to decide if it's acceptable if non text content isn't read aloud. Images with alt text are expected to be read, though note this tool is primarily used for reading long form content e.g. paragraphs of text.
Back to steps

Step 6 - Document any bugs

Document any accessibility bugs found, include as much information as you can, including information on how to replicate the issue and the bug priority level.

Note, this guide takes one approach, there are other ways you could do this. Back to top