Assistive technology guide, ZoomText for Windows testing steps

We’ll take you step by step through how to test a component or feature with ZoomText, screen magnifier software with speech, for Windows. Test with the latest version available.

How to turn ZoomText on / off

ZoomText is not installed on Windows devices by default.

1. To check if you have ZoomText already installed on your device, go to the taskbar and search for 'ZoomText', you should see the ZoomText app listed in the search results, here you can open ZoomText.
2. If you can't see ZoomText, request 'ZoomText Magnifier/Reader' from IT.
3. When ZoomText opens, you will hear an annoucement and everything on the screen will be magnified by default.
4. When using ZoomText, your activity will be announced by default, your point of interest will be in view, and as you move the pointer around the screen it will be followed.
5. If at any time you can't see the ZoomText window, to bring it into view press 'Caps lock + Ctrl + U'.
6. You can adjust the magnification level in the ZoomText window, in the 'Magnifier' toolbar, adjust 'Zoom level'. Alternatively at any time you can press 'Caps lock + up arrow' to increase the zoom level or press 'Caps lock + down arrow' to decrease the zoom level.
7. If at any time you would like to stop ZoomText while announcing something press 'Ctrl'.
8. There are many ZoomText commands and features that you can use, though only a few are needed to perform the testing steps, all of which are explained below.
9. To toggle ZoomText on or off press 'Caps lock + Ctrl + Enter'.
10. To exit and close ZoomText, open the ZoomText window in the taskbar or press 'Caps lock + Ctrl + U', in the 'ZoomText' menu select 'Exit'. Alternatively activate the close icon in the ZoomText window.

Back to page contents

It's speaking too fast

If you are new to ZoomText, you may find the rate in which announcements are made too quick to understand. To find a speaking rate that you are comfortable with:

1. If you can't see the ZoomText window, to bring it into view, press 'Caps lock + Ctrl + U'.
2. In the 'Reader' toolbar, select ‘Rate’ to make an adjustment.
3. Press the down arrow key to decrease the speaking rate.
4. Press the up arrow key to increase the speaking rate.
5. Alternatively, adjust the speaking rate with a keyboard shortcut. Press 'Caps lock + Alt + up arrow' to increase the rate, press 'Caps lock + Alt + down arrow' to decrease the rate.

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.

Some language support is available with different voices for ZoomText.

1. If you can't see the ZoomText window, to bring it into view, press 'Caps lock + Ctrl + U'.
2. In the 'Reader' toolbar, open the ‘Voice’ settings.
3. Select the foreign language required.
4. If you can't see the required foreign language, open 'Download more voices', select a language from the list of supported languages, then select and install a voice from that language.

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 ZoomText 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 - Turn ZoomText on

Go to the taskbar and search for 'ZoomText', you should see the ZoomText app listed in the search results, here you can open ZoomText.

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

Step 2 - Open Chrome

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

Note: ZoomText will work with other browsers, though always test in the most used browser.

Step 3 - Go to the testing url

Navigate to or type in the testing url.

Step 4 - Get in position to start testing

1. Move the pointer around the screen until you can see the start of the component you're going to test.
2. If using a trackpad, use one finger to move around the zoomed screen, and use two fingers to scroll the browser window.
3. Speech is usually on by default. If you have not heard anything announced while ZoomText has been open, turn speech on. To toggle speech on or off, press 'Caps lock + Alt + Enter', you will hear an annoucement. If you still can't hear anything, check your device volume level. If the volume is on and you still can't hear anything, restart ZoomText and Chrome, or your device.

Step 5 - View all the component

You are now ready to start testing, using an increased magnification level view all the component.

1. Set the zoom level to 5. Press 'Caps lock + up arrow', this will increase the zoom level and announce it. Press 'Caps lock + down arrow' if you need to decrease the zoom level.
2. Following the reading order, move the pointer around to view all elements in the component.
3. Check that it's easy to find content that is related. For example, if there is a form field, check the label is nearby.
4. Check that it's easy to find all other elements. For example, check design patterns follow best practice, such as if there is a close icon, is it postioned at the top on the right?
5. Check that it's easy to see all elements. For example, if any content changes or disappears on hover, is it easy to see the default content with high magnification?
6. Check navigation tracking. For example, when activating a 'skip to content' link in the banner, you would expect the view to be scrolled upon interaction, to bring into view the start of the main content. Check the user experience is as expected for any in-page interactions.

Component bug examples

• There is a form field and the label is not nearby
• Design patterns don't follow best practice, such as there is a close icon, and is it postioned at the bottom on the left
• Default content that changes or disappears on hover can't be seen easily with high magnification
• The view isn't scrolled upon an in-page interaction and the start of the associated content is out of view (unless it is the next element on screen)

Step 6 - Focus on all actionable elements

All actionable elements, such as links, buttons and form elements, should be able to be focussed upon and be announced.

1. For efficency, set the zoom level to 1 or 2 (the default magnification level). Press 'Caps lock + down arrow', this will decrease the zoom level and announce it. Press 'Caps lock + up arrow' if you need to increase the zoom level.
2. If you can't see the ZoomText window, to bring it into view press 'Caps lock + Ctrl + U'.
3. In the 'Magnifier' toolbar, select a 'Focus' scheme of your choice, such as 'Red rectangle'.
4. Return to Chrome and move focus to an element in the component before the one you're testing. To move focus to an actionable element, press 'Tab' until you reach the element, or click and hold on the element, then move the pointer away before releasing. To move focus to a non actionable element, click on the element. Or if testing in isolation use the keyboard shortcut to move focus to the address bar, press 'Alt D'.
5. Press 'Tab' to read the first actionable element in the component you're testing. Check that the announced content matches the screen reader UX. If focus moves but nothing is announced, check speech is on.
6. If you need to hear what was announced again, press 'Shift + Tab' move to the previous actionable element, then press 'Tab' again.
7. Press 'Tab' to go through all actionable elements in the component, listening to what’s announced, until you reach the first actionable element in the component after the component you're testing, or the bottom of the page if testing in isolation (or there are no other actionable elements).

Focusing on an item in the component before the one you're testing, will ensure that you don’t miss out any elements that you can’t see at the beginning of the component, such as a visually hidden off screen element.

Navigating to the component after the one you're testing, will ensure that you don’t miss out any elements that you can’t see at the end, such as a visually hidden off screen element.

Focus bug examples

• You press 'Tab', focus moves but nothing is announced
• An actionable element was announced but you can't see the element displayed on screen
• An actionable element was announced that isn't defined in the screen reader UX
• An actionable element is announced twice
• What's announced doesn’t match the screen reader UX

Step 7 - Read all content aloud

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

1. Read by selection: In the 'Reader' toolbar, under the 'AppReader' menu, select 'Use SpeakIt tool'. Click to read aloud individual text elements, or click and drag to read aloud blocks of content. Read aloud all text content. To exit the AppReader press 'Esc'.
2. Read on echo: In the 'Reader' toolbar, under the 'Mouse' menu, select 'Instant' or 'Hover'. Read aloud text content instantly by pointing, or when hovering briefly. Read aloud all text content.

Reader bug examples

• Nothing is read aloud when I read by selection or read on echo.
• Link text is not read aloud when I read by selection or read on echo.
• 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, this maybe more noticeable with 'read by selection'. 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.

Step 8 - Accessibility acceptance criteria

Accessibility acceptance criteria can be used for additional manual testing steps specific to your component and documented UX, specific ZoomText commands maybe needed.

1. Read the accessibility acceptance criteria. If the accessibility acceptance criteria is missing, ask your team's business analyst for the criteria before continuing.
2. Check that any criteria that is specific to using screen magnifier software is met with ZoomText for Windows.

Step 9 - 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