Are descriptions for fields and boxes easy to understand?
Answer: Always
Score: 2
Notes: All form fields contain straightforward and intuitive descriptions. Labels such as “Author,” “Title,” “Publication,” and “Full Text” are commonly used and clearly convey the purpose of each field. Instructions are concise and use plain language, making the interface easy to understand for all users, including those with cognitive or language-related challenges.
Are labels placed above the user input fields and clearly associated with each field?
Answer: Always
Score: 2
Notes: All user input fields—particularly in the basic and advanced search interfaces—feature labels placed above or adjacent to the corresponding input field. These labels are visually aligned and programmatically associated with their fields, ensuring compatibility with assistive technologies. No accessibility issues were flagged by WAVE in this area.
Are text cues for coloured form control labels available?
Answer: Sometimes
Score: 1
Notes: In some forms, red text or bold styling is used to indicate required fields (such as in the account creation or citation tools). However, not all fields include an accompanying text cue like "(required)", which could cause issues for users who cannot perceive colour differences. Adding explicit text cues would improve clarity and accessibility.
Are other visual indicators provided consistently, such as an asterisk for required form fields?
Answer: Sometimes
Score: 1
Notes: Some forms, such as citation tools or account creation pages, use red text or bold labels to indicate required fields. However, the use of asterisks (*) or other standardized indicators is inconsistent across the platform. This may reduce clarity for some users, particularly those who rely on visual consistency or cannot perceive colour alone.
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: When a form is submitted with missing or incorrect input (e.g., leaving an email field empty), EBSCOhost provides clear error messages that appear near the field in question. These messages are concise (e.g., “Please enter a valid email address”), are visually distinct, and work well with screen readers. The user remains on the form page, can correct the issue, and resubmit successfully with confirmation. The error messages are also keyboard navigable and do not interfere with reading or tab order.
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 on EBSCOhost forms (e.g., email citation, login, or account creation) appear directly adjacent to the problematic field, providing specific guidance such as “Please enter a valid email address.” The error descriptions are concise, easy to understand, and allow users to quickly identify the issue, make corrections, and resubmit the form. These alerts are also recognized by screen readers and follow proper tab order.
Is the user able to easily access the user input field to correct the error?
Answer: Always
Score: 2
Notes: When an error is triggered (e.g., by submitting a form without required information), the EBSCOhost platform keeps the user on the same page, highlights the error next to the affected field, and allows the user to immediately click or tab into the field to correct it. The process is smooth with both mouse and keyboard, and the form can be resubmitted after the correction. The interface supports both visual and assistive technology users.
Is the user able to resubmit the form and re-validate their submission?
Answer: Always
Score: 2
Notes: After correcting input errors (e.g., adding a missing email address), the user can easily resubmit the form without needing to refresh or restart the page. Once submitted successfully, the user receives a clear confirmation message, indicating that the action (e.g., sending an email or creating an account) has been completed. The process is smooth and accessible.
Do error reports follow a logical reading and navigation order?
Answer: Always
Score: 2
Notes: Error messages appear in a top-down logical order, either inline with the problematic field or grouped near the top of the form, maintaining the standard tab and reading flow. Keyboard users can move through errors in sequence, and screen readers announce the alerts in the correct order. This ensures that users don’t miss important feedback and can respond effectively.
When a user spells a word incorrectly, does the search function offer spelling suggestions or synonyms?
Answer: Always
Score: 2
Notes: The search function in EBSCOhost (Canadian Literary Centre) includes a built-in spell-check feature. When a misspelled term is entered (e.g., “cornavirus”), the system automatically displays a spelling suggestion such as “coronavirus and COVID-19.” This supports users in refining searches and improves accessibility, especially for users with cognitive or language processing difficulties.
Are icons such as to save, download, or print consistent across the site?
Answer: Always
Score: 2
Notes: Functional icons like “Save”, “Email”, “Print”, and “Cite” are consistently used and styled across article result pages and detail views. Users can reliably identify their functions by visual design alone, and placement is consistent throughout the interface.
Is alternative text clear and consistent for each icon type?
Answer: Always
Score: 2
Notes: Alt text for functional icons is both clear and consistent across the platform. For example, the “Cite” icon always includes descriptive text like “Cite” or “Citation Tool”, and similar consistency applies to other icons such as “Print”, “Download”, or “Email”. WAVE did not flag inconsistencies in icon labeling.
Are actions consistently labelled across the site? For example, the “search” button is always labeled “search”.
Answer: Always
Score: 2
Notes: All interactive actions (such as the "Search" button, "Add to folder", and "Email") are labeled consistently across the interface. The search button always uses the word “Search”, maintaining uniformity for user expectations and screen reader announcements.
Are icons that have adjacent links consistent?
Answer: Always
Score: 2
Notes: Icons with adjacent links (such as citation tools or export functions) are consistently used. If both icon and text are clickable, they lead to the same destination and convey the same function, reducing ambiguity for all users.
Can the purpose of each link be determined from the link text alone?
Answer: Always
Score: 2
Notes: Link text across the platform is descriptive and independent. Phrases like “PDF Full Text”, “Cite”, and “Email this article” clearly convey their function without requiring additional context. This benefits screen reader users and improves overall clarity.
Does the eresource have a consistent layout and navigation across all pages?
Answer: Always
Score: 2
Notes: The EBSCOhost platform uses a consistent layout across all pages, including the homepage, search results, advanced search, and record details. Navigation menus, search bars, and utility links (e.g., Sign In, Folder, Help) appear in the same locations throughout the experience, reducing cognitive load and improving usability.
Are search fields located in the same places throughout the website?
Answer: Always
Score: 2
Notes: The search bar appears consistently at the top of every page, whether on the homepage, results page, or article detail view. Users do not need to reorient themselves when conducting a new search.
Do other features occur in the same place throughout the website?
Answer: Always
Score: 2
Notes: Page numbers, result filters, citation/export tools, and help/contact links maintain consistent placement. The location of features like "Help," "Folder," and "My EBSCOhost" remains fixed in the top navigation, ensuring predictability.
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: Pop-up windows are not triggered automatically. When users click on features like “Cite,” “Email,” or “Export,” content opens in modal-style overlays or same-tab interfaces — not separate tabs or browser windows unless explicitly requested (e.g., “Open in new tab” actions).
Does the database avoid launching pop-up windows automatically when the database is loaded?
Answer: Always
Score: 2
Notes: No pop-ups are triggered automatically upon launching the database. The homepage loads without interruptions or overlays, allowing users to begin navigation or searching without unexpected prompts or windows.
Where pop-ups occur, are users able to postpone or suppress any pop-ups?
Answer: Always
Score: 2
Notes: When pop-up modals appear (e.g., saving to folder, email form), they can be closed or canceled easily using mouse or keyboard (Esc, Tab + Enter). These interactions are under user control and do not auto-trigger without action.
Does the database avoid launching pages in a new browser window with the usual browser controls missing?
Answer: Always
Score: 2
Notes: No instances were found where pages launched in new browser windows without browser chrome (address bar, controls). Even when external links or documents open in new tabs, they do so within standard browser environments with full navigation available.
Is page content subdivided hierarchically into appropriate headings and tagged appropriately?
Answer: Always
Score: 2
Notes: WAVE’s heading outline confirms that EBSCOhost pages use properly nested heading tags (e.g., <h1> for main titles, <h2> for major sections, <h3> for subsections). Heading levels are not skipped, and the visual hierarchy matches the semantic structure. This allows screen reader users to navigate the page effectively.
Are headings concise and clear, and accurately reflect the content under that heading?
Answer: Always
Score: 2
Notes: Headings such as “Refine Results,” “Search Results,” “Tools,” and “Detailed Record” are brief, descriptive, and match the content that follows. This clarity supports both assistive technology users and visual users in understanding and navigating the interface efficiently.
Does the main navigation and drop-downs contain a reasonable number of menu items?
Answer: Always
Score: 2
Notes: The number of menu items is kept to a minimum, and dropdowns (such as for citation export tools or filter controls) typically contain fewer than 6 options, making them manageable even for screen reader users. No deep nesting or overwhelming submenu structures were observed.
Can all menus and submenus be accessed with screen readers and via keyboard navigation?
Answer: Always
Score: 2
Notes: Menus and dropdowns are fully accessible using the keyboard (via Tab, Enter, and arrow keys). Each menu item receives visible focus, and dropdowns expand on keyboard interaction. Additionally, screen readers can detect and announce menu items appropriately, and there are redundant text links (e.g., “Tools” section below article titles) for critical actions, ensuring accessibility.
Does the “results” page or item record view avoid opening in a new tab without a warning?
Answer: Always
Score: 2
Notes: Search results and article views open in the same tab unless the user manually chooses to open links in a new tab. There is no automatic tab launching, and user control is preserved throughout the search experience.
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 sort options (e.g., date range, subject, full text) in the result list require users to click "Update" to apply changes. Content does not refresh automatically on focus or selection, which supports accessibility.
Does the database avoid automatic redirection?
Answer: Always
Score: 2
Notes: No auto-redirection was observed. Users are always aware of page transitions, and changes occur only after a button is clicked or a link is activated. There is no silent redirect behavior.
Does the database avoid launching new windows when a component receives focus?
Answer: Always
Score: 2
Notes: Tabbing through the interface or placing focus on a component does not open any new windows or dialogs automatically. The user remains in the same visual context throughout keyboard navigation.
Does the database avoid change of focus when a component receives focus?
Answer: Always
Score: 2
Notes: Focus remains on the selected component when navigating with the keyboard. No elements shift the focus away unexpectedly (e.g., no help pop-ups or modals triggered on focus alone). This behavior supports screen reader users and individuals with motor or cognitive disabilities.
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: Keyboard navigation is smooth and sequential. Tab and Shift+Tab work logically, and focus indicators are visible. Focus does not jump or disappear while navigating, and interactive elements retain proper focus.