Checklists for testing with NVDA

Testing the document title

These tests check whether each page has a document title that NVDA can announce, and whether that title helps users know where they are.

Test 2: Does the document title describe the topic or purpose of the page?

How to check: Press NVDA+T and compare what you hear with the main content of the page.

Related WCAG criteria:

Test 3: Does the document title distinguish this page from other pages on the site?

How to check: Visit two or three different pages, press NVDA+T on each page, and compare the titles.

Related WCAG criteria:

Test 4: When the main content changes without a full page load, does the document title update?

How to check: Trigger a change that displays a different page or view (for example, navigate within a single-page application), then press NVDA+T .

Related WCAG criteria:

Testing headings

These tests check whether NVDA announces the headings on a page, and whether those headings provide a useful outline of the content.

Test 1: Does the page contain at least one heading?

How to check: Press H to navigate through headings. Check that NVDA identifies at least one heading on the page. If the page has no headings, NVDA announces "no next heading".

Related WCAG criteria:

Test 2: Does NVDA announce every visible heading as a heading?

How to check: Press H to move through the headings and compare what NVDA announces with the headings you can see on screen.

Related WCAG criteria:

Test 3: Is everything NVDA announces as a heading actually a heading?

How to check: Press H to move through the headings and check that each one identifies a section or subsection of content.

Related WCAG criteria:

Test 4: Does every heading contain text?

How to check: Press H to move through the headings and listen for any that announce only a heading level, such as "heading level 2", without a name.

Related WCAG criteria:

Test 5: Do the heading levels reflect the structure of the page?

How to check: Open the Elements List ( NVDA+F7 ), select Headings, and check that the heading levels reflect the relationships between sections and subsections.

Related WCAG criteria:

Test 6: Does each heading describe the content that follows it?

How to check: Open the Elements List ( NVDA+F7 ), select Headings, and review whether the headings provide a useful outline of the page. Where necessary, navigate to a heading and read the content that follows.

Related WCAG criteria:

These tests check whether NVDA announces each link with a name that helps users understand its purpose.

Test 1: Does NVDA announce every visible link as a link?

How to check: Press K to move through the links and compare what NVDA announces with the links you can see on screen.

Related WCAG criteria:

Test 3: Does NVDA announce the visible link text as part of each link's name?

How to check: Press K to move through the links and compare the announced names with the visible link text. The visible text should be included, although additional words may be announced.

Related WCAG criteria:

Test 4: Can the purpose of each link be determined from its name or surrounding content?

How to check: Press K to move through the links. Where a link is unclear on its own (such as "Read more"), use the arrow keys to read the surrounding sentence, paragraph, list item or table cell.

Related WCAG criteria:

Test 5: Are users informed when links have unusual behaviour? Best practice

How to check: Press K to navigate through links and listen for information about actions such as downloading a file, opening a new window or starting an email.

Related WCAG criteria: None (best practice)

Testing landmarks

These tests check whether the page has landmarks that help NVDA users move between its main sections. All landmark tests are best practice rather than WCAG requirements.

Test 1: Does the page have landmarks that identify its main sections? Best practice

How to check: Press D to move through the landmarks, or open the Elements List ( NVDA+F7 ) and select Landmarks. Listen for landmarks such as banner, navigation, main and content info (footer).

Related WCAG criteria: None (best practice)

Test 2: When multiple landmarks of the same type are present, can they be distinguished by their names? Best practice

How to check: Press D to move through the landmarks. Where multiple landmarks of the same type are present, check that NVDA announces names that distinguish them, such as "Primary navigation landmark" and "Footer navigation landmark".

Related WCAG criteria: None (best practice)

Test 3: Does the page have one main landmark? Best practice

How to check: Open the Elements List ( NVDA+F7 ), select Landmarks, and check that there is exactly one main landmark.

Related WCAG criteria: None (best practice)

Testing images

These tests check whether NVDA provides users with the information and functionality conveyed by images. Before you start, decide which images on the page are informative, functional or complex.

Test 1: Does NVDA announce every image without reading a file name or path?

How to check: Press G to move through the images and listen for any announced as a file name or path, or as just "graphic".

Related WCAG criteria:

Test 2: Does NVDA announce every informative image?

How to check: Press G to move through the images and compare what NVDA announces with the images you can see on screen. Any informative image NVDA skips is a fail.

Related WCAG criteria:

Test 3: Does NVDA announce a text alternative that conveys the meaning of each informative image?

How to check: Press G to move through the images. For each one, compare what NVDA announces with what the image shows.

Related WCAG criteria:

Test 4: Does NVDA announce a name for each image link or button that conveys its purpose?

How to check: Press K to move through links and B to move through buttons. For any that contain an image, check that what NVDA announces describes what the link or button does, not what the image looks like.

Related WCAG criteria:

Test 5: Does each complex image have a longer description available?

How to check: Press G to move to the complex image, such as a chart or diagram, then use the arrow keys to read the content around it. Check for a description on the page, or a link to one.

Related WCAG criteria:

Testing lists

These tests check whether NVDA announces lists as lists, along with the correct number of items.

Test 1: Does NVDA announce every visible list as a list?

How to check: Press L to move through the lists and compare what NVDA announces with the lists you can see on screen.

Related WCAG criteria:

Test 2: Does NVDA announce the correct number of items for each list?

How to check: Press L to move to each list and listen for the item count, such as "list with 5 items". Compare it with the number of items you can see on screen.

Related WCAG criteria:

Testing tables

These tests check whether NVDA announces data tables, their size, and their headers as you move through them. They apply to data tables only, not tables used for layout.

Test 1: Does NVDA announce every visible data table as a table?

How to check: Press T to move through the tables and compare what NVDA announces with the data tables you can see on screen.

Related WCAG criteria:

Test 2: Does NVDA announce the correct number of rows and columns for each table?

How to check: Press T to move to each table and listen for the size, such as "table with 5 rows and 4 columns". Compare it with the rows and columns you can see on screen.

Related WCAG criteria:

Test 3: Does NVDA announce the column header when moving across a row?

How to check: Move into a table, then press Ctrl+Alt+Right Arrow to move across a row. As you move into each new column, NVDA should announce that column's header before the cell content.

Related WCAG criteria:

Test 4: Does NVDA announce the row header when moving down a column?

How to check: Move into a table, then press Ctrl+Alt+Down Arrow to move down a column. As you move into each new row, NVDA should announce that row's header before the cell content. This only applies to tables with row headers.

Related WCAG criteria:

Test 5: Does NVDA announce a name for each table? Best practice

How to check: Press T to move to each table and listen for a name that describes the table's content, announced along with "table".

Related WCAG criteria: None (best practice)

Testing labels for form fields

These tests check whether NVDA announces each form field with a name that matches its visible label and describes what users need to enter or select.

Test 1: Does NVDA announce every visible form field as a form field?

How to check: Press F to move through the form fields and compare what NVDA announces with the fields you can see on screen. Listen for the field type, such as "edit", "check box" or "combo box", and check it matches what you see.

Related WCAG criteria:

Test 3: Does NVDA announce the visible label as part of each form field's name?

How to check: Press F to move through the form fields and compare the announced names with the visible labels. The visible label should be included, although additional words may be announced.

Related WCAG criteria:

Test 4: Does each form field's name describe the information required?

How to check: Press F to move through the form fields and check that each name makes clear what to enter or select, without needing to see the screen.

Related WCAG criteria:

Testing form field instructions

These tests check whether NVDA announces a field's instructions, such as a date format or password rules, when you move to that field.

Test 2: Does NVDA announce each set of instructions with the correct form field?

How to check: Press Tab to move through the form fields and check that the instructions NVDA announces match the instructions shown next to that field on screen.

Related WCAG criteria:

Test 3: Does NVDA announce the instructions in full?

How to check: Press Tab to move through the form fields and compare the announced instructions with the visible instructions. Listen for any that are cut short or missing part of the text.

Related WCAG criteria:

Testing overall labels for radio and checkbox groups

These tests check whether NVDA announces the question or label for each group of radio buttons or checkboxes, not just the individual options.

Test 1: Does NVDA announce every visible radio and checkbox group as a group?

How to check: Press Tab or F to move into the first option of each group. Listen for "grouping" or similar, and compare with the groups you can see on screen.

Related WCAG criteria:

Test 2: Does NVDA announce a name for every radio and checkbox group?

How to check: Press Tab or F to move into each group and listen for a group name before the first option, such as "Delivery method, grouping".

Related WCAG criteria:

Test 3: Does NVDA announce the visible group label as part of each group's name?

How to check: Compare the announced group name with the question or label shown above the group on screen.

Related WCAG criteria:

Test 4: Does each group's name describe the question being asked?

How to check: Listen to the group name on its own and check that it makes clear what you're choosing, such as "Delivery method" rather than "Options".

Related WCAG criteria:

Testing instructions for radio and checkbox groups

These tests check whether NVDA announces instructions for a group of radio buttons or checkboxes, such as "Select all that apply", when you move into the group.

Test 1: Does NVDA announce the instructions for each radio and checkbox group when moving into the group?

How to check: Press Tab or F to move into the first option of each group. For each group with visible instructions, such as "Select all that apply", listen for the instructions in the announcement.

Related WCAG criteria:

Test 2: Does NVDA announce each set of instructions with the correct group?

How to check: Press Tab or F to move into each group and check that the instructions NVDA announces match the instructions shown with that group on screen.

Related WCAG criteria:

Test 3: Does NVDA announce the group instructions in full?

How to check: Press Tab or F to move into each group and compare the announced instructions with the visible instructions. Listen for any that are cut short or missing part of the text.

Related WCAG criteria:

Testing required fields

These tests check whether NVDA users can identify which form fields are required, and whether optional fields are incorrectly announced as required.

Test 2: Is every form field NVDA announces as required actually required?

How to check: Press F to move through the form fields. For each field NVDA announces as "required", check that it's shown as required on screen.

Related WCAG criteria:

Test 3: Does NVDA announce "required" as a state for every required form field? Best practice

How to check: Press F to move through the form fields and listen for "required" after the field type, such as "First name, edit, required". If "required" only comes before the type, it's part of the label text rather than a state.

Related WCAG criteria: None (best practice)

Testing form field errors

These tests check whether NVDA announces each error message with its field, and whether the message helps users fix the problem.

Test 1: Does NVDA announce the error message for each form field with an error, when moving to that field?

How to check: Submit the form with errors, then press Tab to move through the form fields. For each field showing an error on screen, listen for the error message in the announcement.

Related WCAG criteria:

Test 2: Does NVDA announce each error message with the correct form field?

How to check: Press Tab to move through the form fields and check that the error NVDA announces matches the error shown next to that field on screen.

Related WCAG criteria:

Test 3: Does NVDA announce each error message in full?

How to check: Press Tab to move through the form fields and compare the announced error with the visible error. Listen for any that are cut short or missing part of the text.

Related WCAG criteria:

Test 4: Does each error message describe how to fix the problem?

How to check: Press Tab to move through the form fields and listen to each error. Check that it tells you what to do, such as " Enter a date in DD/MM/YYYY format", rather than just "Invalid date".

Related WCAG criteria:

Test 5: Does NVDA stop announcing the error once the field has been corrected?

How to check: Correct the field, resubmit the form or move away from the field, then Tab back to it. Check that NVDA no longer announces the error.

Related WCAG criteria:

Test 6: Does NVDA announce "invalid entry" for each form field with an error? Best practice

How to check: Press Tab to move through the form fields with errors and listen for "invalid entry" in the announcement.

Related WCAG criteria: None (best practice)

Test 7: Does NVDA avoid announcing errors before the user has finished with the field? Best practice

How to check: Reload the form, then move to a form field for the first time and listen for any error message or "invalid entry". Then type part of a value, such as the first few letters of an email address, and listen for any error announced while you're still typing. Errors announced after leaving the field or after submitting the form are fine.

Related WCAG criteria: None (best practice)

Testing on-submit errors

These tests check how NVDA handles errors when a form is submitted, including where focus moves and how users can navigate to fields with errors. Tests 1, 2 and 4 are based on Intopia's recommendations rather than WCAG requirements.

Test 1: For forms with two fields or fewer, does focus move to the first field with an error when the form is submitted?

How to check: Submit the form with errors. Listen for NVDA to announce the first field with an error, including its name and error message.

Related WCAG criteria:

  • None (Intopia recommendation)

Test 2: For forms with more than two fields, does focus move to an error summary above the form when the form is submitted?

How to check: Submit the form with errors. Listen for NVDA to announce the error summary, rather than staying silent or announcing the submit button again.

Related WCAG criteria:

  • None (Intopia recommendation)

Test 3: Does the error summary list every error in the form?

How to check: After submitting, use the arrow keys to read through the error summary. Compare the errors announced with the errors shown next to the fields on screen.

Related WCAG criteria:

Test 4: Does each error in the summary take you to the field it describes?

How to check: Use the arrow keys to move to each error in the summary and press Enter to activate it. Listen for NVDA to announce the matching form field.

Related WCAG criteria:

  • None (Intopia recommendation)