HeinOnline Accessibility Evaluation
Evaluation date: November, 2026
Report date: November, 2026
Overview
The Center for User Experience (UX) evaluates digital content using the Web Content Accessibility Guidelines (WCAG) version 2.1, Levels A and AA as our technical standard, using both manual and automated testing methods.
Our manual testing methods include checking for:
- keyboard and screen reader support
- reflow at high levels of magnification
- accessible video and audio content
- sufficient color contrast
We may also identify usability barriers.
This evaluation is not comprehensive and should not be used as a replacement for internal quality assurance of a product. We find patterns of accessibility barriers and show examples of the types of barriers we find. If you have questions about this evaluation, please contact centerforux@wisc.edu.
For more about WCAG conformance, refer to W3C's Understanding Conformance Levels.
Test conditions
Device: Dell Pro 16 Plus PB16250
Operating system: Windows 11
Browser: Chrome and Edge
Screen reader: NVDA, JAWS
Summary
-
Overall
-
Areas found to be mostly accessible:
-
Tables in search results.
-
-
Areas that were identified as needing improvement:
-
Blocker: The site largely becomes unreadable at increased zoom.
-
Blocker: All documents tested lacked accessible markup (online, and downloadable pdf and plain text versions).
-
Many buttons do not have individually accessible names to distinguish between each other.
-
Keyboard focus frequently moves to the top of the page when it should stay on an element.
-
The focus indicator largely lacks sufficient contrast.
-
-
-
Reviewing a paper
-
Blocker: Screen-reader users will have difficulty navigating and reading all documents.
-
Blocker: The “next” and “previous” page buttons that appear at the bottom of the page when navigating with keyboard-only are not persistent, disappear due to unknown causes and lack a focus indicator.
-
-
LibGuide
-
Some images lack alt text.
-
Semantic markup is either missing or confusing for some elements such as headings and tab panels.
-
-
Search
-
Results are not alerted to screen-reader users.
-
Some form fields have confusing accessible names.
-
-
Databases
-
Some inline links and database buttons do not provide context for their destination and purpose.
-
Keyboard
Expected behavior: All actionable elements have a visible focus indicator and all actions can be completed using a keyboard alone.
Barriers:
-
Site wide
-
The gray focus indicator around elements such as search fields, search buttons, drop downs and blue buttons lacks sufficient contrast against the white background.
-
The “i” popups do not pull or confine keyboard or screen reader focus, and do not close with escape as expected.
-
After making some selections throughout the site, including alphabetical selections on the Database home page, or on individual databases such as Animal Studies: Law, Welfare, and Rights, keyboard focus moves to the top of the page. Expected behavior is for focus to return or stay at the button that was selected, or move to the top of the new content.
-
-
Reviewing a paper
-
Blocker: The “next” and “previous” page buttons that appear at the bottom of the page when navigating with keyboard-only are not persistent, disappear due to unknown causes and lack a focus indicator.
-
The easiest way to navigate between pages is by scrolling up or down. This may be confusing for many users as there is a long load time between pages. Additionally, due to the previous and next buttons that appear at the bottom of pages sometimes it is difficult to navigate between pages with keyboard and screen reader.
-
Modal dialogs such as “Display citation information for this page” do not pull or confine keyboard focus. This may cause users to get lost in the page behind it. Though it is the next item in the focus order, and when closed focus returns to the button that launched it, this is not true for all modals.
-
When the Pathfinder modal is launched the page reloads and focus moves to the top of the page instead of the modal
-
Non-actionable items, such as citations are in the keyboard focus order.
-
In the AI Summary modal there is an actionable tab stop that periodically does not correlate with any visual content.
-
-
LibGuide
-
On LibGuide pages such as Manz, William, some items that are non-actionable are in the keyboard focus order including the Summary tab and the text within the tab. Additionally, the Summary tab should not be a tab panel if there is only one item.
-
-
Search
-
Tab sections such as “Matching Text” and “Summary” in search results do not function as a semantic tab panel and can not be navigated to with arrow keys.
-
Screen reader
Expected behavior: All actions should be able to be completed with a screen reader and all information should be conveyed as well.
Barriers:
-
Site wide
-
Most pages do not have descriptive page titles, for example individual papers have a page title of their database.
-
When content will open a new tab or window it is best practice to indicate this to screen-reader users. This includes things such as the RSS button on pages such as Air and Space Lawyer, “More like this” button when viewing a paper and “More Information” buttons on database pages.
-
-
Reviewing a Paper
-
Blocker: Scanned documents lack semantic or accessible markup, making navigating and understanding them difficult for screen-reader users.
-
Blocker: Downloadable papers such as PDFs and plain text, do not include accessibility tags or semantic markup. The plain text is more accessible as screen-reader users can navigate through it piece by piece, but both will prevent users from being able to easily navigate
-
-
LibGuide
-
Expanding sections, such as the “i” buttons in the Lib Guide do not indicate their expanded/collapsed state. They also visually match items that have pop-ups, which may be confusing to users.
-
Some inline links do not indicate the destination of the link out of context, such as “here” in the h-index or LibGuide, and “Read More” in LibGuide. This also applies to content that loads for the “Create eTOC Alert” button.
-
-
Search
-
Screen-reader users are not alerted when content loads such as search results.
-
-
Database
-
On database pages such as American Law Institute Library have multiple buttons that all have accessible names of “More Information". This includes “MACR Record More Information” and “More Information”, these repetitive names do not provide context for what subject matter they correlate with, and it may be unclear if they are the same or different buttons to users.
-
Expanding sections on pages such as Acts of the Parliament of Canada (Annual Statutes) all have the accessible names of “Load table of contents” which does not provide context for what item they are related to.
-
Color Contrast and Visibility
Expected behavior: All elements should have sufficient color contrast and be readable by all users when active.
Barriers:
-
Site wide
-
Blocker: The site becomes unusable at high zoom with the top header blocking large sections of the top of the page or the whole page such as on article pages, overlapping a large amount of content, and creating horizontal scrolls on many pages. When able to scroll up users may have difficulty accessing content they just scrolled past. Additionally some text breaks containers and overlaps, becoming difficult to read.
-
-
Reviewing Document
-
The next and previous buttons that appear when navigating with keyboard on document pages lack a visual focus indicator.
-
-
LibGuide
-
When viewed at increased zoom size, the Summary tab creates a horizontal scroll.
-
Images
Expected behavior: All important images should have accurate alt text, and decorative images should be hidden from screen readers. Images of text should not be present if possible.
Barriers:
-
Reviewing Document
-
Blocker: Due to the lack of accessible markup, documents that contain many images such as 111 A.B.A. do not have accessible alternatives.
-
-
LibGuide
-
The “Findit@UW” images lack alt text.
-
Logos such as AEI on the American Enterprise Institute page are unlabeled.
-
-
Search Results
-
Although images such as Venn diagram search results do not give detailed descriptions of the image, there are appropriate text alternatives in table format.
-
Tables
Expected behavior: Tables should have semantic markup to be easily navigated and understood by screen-reader users. All filter options should be operable by keyboard and screen reader users.
Barriers:
-
Database
-
Stylistic tables are used for some databases such as Acts of the Parliament of Canada (Annual Statutes). Tables that are used this way should be hidden from screen readers with utilization of role=”presentation”.
-
Forms
Expected behavior: Forum fields should have accessible labels for screen reader users, be fully operable with keyboard only, and errors should be conveyed to screen reader users.
Barriers:
-
Chat with us
-
Fields with errors in the Chat with Us modal do not pull focus.
-
-
LibGuide
-
In the HeinOnline’s Path Finder modal, forms such as Email Address, Comments and Phone Number do not have accessible names.
-
There is a blue dot slider that is unclear to all users what its purpose is on the LibGuide.
-

-
-
Search
-
When searching a specific database, such as American Association of Law Libraries (AALL), search fiends and dropdown sections contain information such as “Search Term A” and "Operator for field B” instead of having an accurate accessible name such as “Title”. The Search Catalog section successfully uses dropdowns that correlate with their text fields.
-
Headings
Expected behavior: All pages should have an h1 at the top of the page that dictates the purpose of the page. All subsequent headings should be properly nested according to content relation. Additionally, headings should be semantic, not only visually indicated.
Barriers:
-
Site wide
-
Some pages such as the home page have improper nesting, including multiple h1’s, with the rest of the page consists of h2’s.
-
Some pages such as the Acts of the Parliament of Canada, lack an h1.
-
-
LibGuide
-
Pages such as AEI Publications lack heading markup.
-
Other
These are issues that otherwise do not fall into the above categories.
Barriers:
-
Site wide
-
All users are logged out without warning at an undetermined time. It is less than 20 hours.
-