Are descriptions for fields and boxes easy to understand?
Answer: Always
Score: 2
Notes: Descriptions were written in plain language and clearly indicated what data was expected in each form field. Terminology was accessible and consistent across the interface.
Are labels placed above the user input fields and clearly associated with each field?
Answer: Always
Score: 2
Notes: Labels were consistently positioned above the corresponding fields, reducing cognitive load and ensuring a linear, logical tabbing sequence. This supports screen reader navigation and improves usability for all users.
Are text cues for coloured form control labels available?
Answer: Always
Score: 2
Notes: Labels were consistently positioned above the corresponding fields, reducing cognitive load and ensuring a linear, logical tabbing sequence. This supports screen reader navigation and improves usability for all users.
Are other visual indicators provided consistently, such as an asterisk for required form fields?
Answer: Always
Score: 2
Notes: When colour was used to indicate required fields (e.g., red text), a text-based explanation was also present (e.g., “Fields marked with * are required”), ensuring users relying on screen readers or without colour vision could understand the meaning.
Are alert messages clearly visible to the user, either at the top of the form field, inline, or through a dialog box?
Answer: Always
Score: 2
Notes: Error messages appear inline next to the affected fields or at the top of the form, with distinguishable text and sometimes icon indicators. These messages are clearly visible and persist until the issue is corrected.
Do alert messages clearly indicate the field in which the error has occurred and a description of the error and the fix?
Answer: Always
Score: 2
Notes: Alert messages specifically mention what went wrong (e.g., “Invalid email address format”) and suggest corrections. Each message is placed logically next to or within the field needing attention.
Is the user able to easily access the user input field to correct the error?
Answer: Always
Score: 2
Notes: After an error occurs, users can return to the form and edit the incorrect entry without needing to restart the process. Focus is retained or returned to the affected field during navigation.
Is the user able to resubmit the form and re-validate their submission?
Answer: Always
Score: 2
Notes: Users can correct the issue and resubmit the form. The submission is revalidated and, if successful, users are shown a confirmation or success message.
Do error reports follow a logical reading and navigation order?
Answer: Always
Score: 2
Notes: Using keyboard and screen reader testing (e.g., NVDA), the reading and navigation order of error messages followed a logical and expected sequence. Focus moved correctly to the first error, and messages were announced clearly.
When a user spells a word incorrectly, does the search function offer spelling suggestions or synonyms?
Answer: Always
Score: 2
Notes: When intentionally entering a misspelled word in the search bar, the interface offered spelling suggestions either via drop-down autofill or suggestions on the results page (e.g., “Did you mean...”). This improves the search experience and supports users with dyslexia or other cognitive challenges.
Are icons such as to save, download, or print consistent across the site?
Answer: Always
Score: 2
Notes: Functional icons such as “save,” “download,” and “print” maintain a consistent appearance and behavior throughout the interface. There is no visual or functional discrepancy between similar actions on different pages.
Is alternative text clear and consistent for each icon type?
Answer: Always
Score: 2
Notes: Each icon has descriptive alt text that matches its function (e.g., “Download PDF” or “Save to folder”). No ambiguous or missing alt text was observed during the WAVE and manual inspection.
Are actions consistently labelled across the site? For example, the “search” button is always labeled “search”.
Answer: Always
Score: 2
Notes: Interactive elements like search, save, and email are consistently labelled across all sections. The term “Search” is used uniformly on buttons and forms without variation.
Are icons that have adjacent links consistent?
Answer: Always
Score: 2
Notes: Where an icon is accompanied by a text link (e.g., a printer icon next to “Print”), the icon and link are contextually consistent and lead to the same action, providing clarity and reinforcement.
Can the purpose of each link be determined from the link text alone?
Answer: Always
Score: 2
Notes: Links use meaningful text like “Download Full Text” or “Email this Record.” There are no vague or non-descriptive links such as “Click here,” ensuring clarity for screen reader users and keyboard navigation.
Does the eresource have a consistent layout and navigation across all pages?
Answer: Always
Score: 2
Notes: The layout across all pages—homepage, results, advanced search, help, and account pages—was consistent in terms of structure, headings, sidebar navigation (if any), and footer links. Users can predictably find tools and features without needing to re-orient on each page.
Are search fields located in the same places throughout the website?
Answer: Always
Score: 2
Notes: Search bars are consistently located in the top central or right-hand area across all pages, including homepage, results, and advanced search. This consistency improves usability and accessibility for screen reader and keyboard users.
Do other features occur in the same place throughout the website?
Answer: Always
Score: 2
Notes: Help links, page navigation (e.g., pagination), contact info, and settings are located consistently throughout the platform. Their placement and labels remain unchanged across different sections of the site.
Does the electronic resource avoid the use of pop-up windows which open automatically in a new tab if a user clicks on a button?
Answer: Always
Score: 2
Notes: Clicking buttons or links (e.g., to view full text, citations, or export functions) opens content in the same tab or a clearly indicated new tab, without disruptive or automatic popups.
Does the database avoid launching pop-up windows automatically when the database is loaded?
Answer: Always
Score: 2
Notes: No pop-ups launched automatically upon entry into the resource or after a period of inactivity. Interface behavior remained predictable and controlled.
Where pop-ups occur, are users able to postpone or suppress any pop-ups?
Answer: Not Applicable
Score: -1
Notes: No pop-ups occurred during testing that required suppression or postponement. The interface remained free of intrusive or time-triggered popups.
Does the database avoid launching pages in a new browser window with the usual browser controls missing?
Answer: Always
Score: 2
Notes: All pages opened in standard browser tabs with full controls (back, forward, refresh, and URL bar). No content was launched in a restricted or control-stripped window.
Is page content subdivided hierarchically into appropriate headings and tagged appropriately?
Answer: Always
Score: 2
Notes: WAVE’s “Outline” tool showed a clear and logical heading structure across the site. <h1> was used for
Are headings concise and clear, and accurately reflect the content under that heading?
Answer: Always
Score: 2
Notes: Headings are short, meaningful, and clearly describe the content they precede. They guide users—both sighted and those using screen readers—efficiently through the page’s content without confusion or ambiguity.
Does the main navigation and drop-downs contain a reasonable number of menu items?
Answer: Always
Score: 2
Notes: Navigation menus remain consistent and uncluttered. Each drop-down includes a manageable number of options, organized logically under main categories without excessive submenus.
Can all menus and submenus be accessed with screen readers and via keyboard navigation?
Answer: Always
Score: 2
Notes: Using keyboard navigation and screen reader (NVDA) testing, all menus and submenus were accessible via the Tab, Arrow, and Enter keys. Focus was clearly indicated, and items were announced appropriately. No inaccessible or hidden links were found.
Does the “results” page or item record view avoid opening in a new tab without a warning?
Answer: Always
Score: 2
Notes: Clicking on item titles or result links opened content in the same tab or, if in a new tab, a clear visual cue or tooltip (e.g., "opens in a new window") was provided to notify the user in advance.
Is there an "update now" button that requests a refresh of content rather than automatically updating the content?
Answer: Always
Score: 2
Notes: Filters and sorting options required the user to manually click an “Apply” or “Update” button. No content updated automatically upon simply selecting a filter, which prevents unintentional changes in context for keyboard users.
Does the database avoid automatic redirection?
Answer: Always
Score: 2
Notes: There were no instances of automatic redirection without user initiation. All page changes occurred after a deliberate user action (e.g., link click or button press).
Does the database avoid launching new windows when a component receives focus?
Answer: Always
Score: 2
Notes: Focus events did not trigger any automatic window launches. Content remained within the current browsing context unless explicitly clicked.
Does the database avoid change of focus when a component receives focus?
Answer: Always
Score: 2
Notes: Keyboard focus remained stable when tabbing through the page. No unexpected pop-ups or focus jumps were observed during interaction.
Are you able to tab through a page using keyboard navigation without the keyboard focus moving away from the control?
Answer: Always
Score: 2
Notes: Tabbing followed a logical sequence, and focus indicators were clearly visible. Focus stayed on each interactive element until moved deliberately by the user using the keyboard.