Read&Write is text to speech literacy software which makes the web more accessible for users with dyslexia, reading and other learning difficulties, or anyone whose first language isn’t English.

It is primarily used for reading long form content e.g. paragraphs of text, for example article page body copy.

Read&Write MUST be tested with Internet Explorer 11. If the component/feature is used on a wide range of pages and services, to meet the Definition of Done Chrome SHOULD also be used for testing (as rendering engines differ greatly between browsers, which may effect how content is read), in order to be considered acceptable for a live release. Test using an actual device if possible.

Not sure how to Read with Read&Write? Watch Introduction to the Read&Write Gold for PC Reading Toolbar from 4 minutes 6 seconds to 5 minutes 30 seconds.

Typical user behaviour

When reading long form content, such as an article on the web, typical user behaviour might be:

  • Less likely to select/highlight content above the first image or video such as the headline or date
  • More likely to select/highlight paragraphs of text to read after the first image or video in the article
  • Would probably have ‘automatically read next block’ or ’continuous reading’ selected
  • User sometimes might select all the content on a long form content page (by pressing ‘CTRL + A’) then click ‘Play’ to read out the entire page, even if that means reading out all the page furniture and navigation

What should I test?

  1. Test the feature by reading highlighted text elements.
  2. Test the feature by reading elements that are hovered over by the mouse.

Testing steps

The accessibility acceptance criteria can be used for additional manual testing steps on device, this is written by the Business Analyst and part of their checklist.

  1. Open Read&Write.
  2. In the toolbar, under the ‘TextHelp’ dropdown menu, under ‘Current Toolbar’ select ‘Reading Features’.
  3. In the toolbar, under the ‘Play’ dropdown menu, make sure only ‘Read by sentence’ is checked. (Ensure ‘Automatically read next block of text’ and ‘Read the web’ are not checked).
  4. Use the mouse to highlight the 1st text element in the feature, then use the ‘Play’ button in the toolbar, to read the text out. Do this for all the text elements in the feature one by one. Note highlighting maybe difficult if the feature uses ‘faux block link’. This is because the ‘faux block link’ sits on top of the text which makes highlighting/selecting text difficult.
  5. If you are testing long form content such as an article page, select all the content by pressing ‘CTRL + A’, then use the ‘Play’ button in the toolbar, to read all the content out.
  6. In the toolbar, under the ‘Play’ dropdown menu, check ‘Read the web’, then use the mouse to hover over the different text elements one by one in the feature, the text should be read out.
  7. If the feature uses ‘faux block link’, you may still have difficulty reading many of the text elements. Try hovering over a text elements you can read out, after reading this out, try using the ‘Forward’ and ‘Rewind’ buttons in the toolbar, to get to difficult text elements.
  8. If the feature uses ‘faux block link’, and you are still having difficulty reading many of the text elements. Try checking ‘Automatically read next block of text’ in the ‘Play’ dropdown menu, then use your mouse to hover over the 1st text element in the feature and let it read until the end of the feature, is everything now read out? If not, in the feature before the feature which is being tested, hover over an item which you can read by hovering, then let it read from this element and through the feature which is being tested.
  9. Hover over each of the images in the feature, the alt text should be read out. Note if the feature uses ‘faux block link’ you may have difficulty.

Known bugs

When testing with IE, you may experience text that is hidden being read out as well as code in script tags, this maybe more noticable when ‘Read the web’ and ‘Automatically read next block of text’ are selected. If so, verify if the same bugs you experienced with IE are also present in Chrome on PC (ensure Chrome has the Read&Write support for Google Chrome extension installed - you do not need to do anything with the extension itself, this enables Read&Write to work). If the bugs do not exist in Chrome then these are bugs with IE and can be ignored.

Test using other supported assistive technology

Other pages

Edit this page