Accessibility in Elsevier Open Access Platform

Last updated on March 05, 2026

Our platform is built to help librarians and institutional OA administrators manage Elsevier agreements with ease, including users who rely on assistive technologies.

We are committed to embedding accessibility in our platform, from navigation and forms to data presentation and workflows, focusing on keyboard operability and screen reader compatibility. The product team is committed to a continuous accessibility learning programme and to embedding accessibility from the outset of design and development. 

We align with the broader Elsevier and RELX accessibility policies and are working to meet WCAG 2.1 AA, continually testing and improving based on user feedback. We welcome input from our users to help us refine accessibility as the product evolves.

Accessibility measures

We have –so far– put in place the following measures:

  • Keyboard navigation: most of the site can be used via keyboard alone
  • A “Skip to main content” link, to bypass repeated navigational items
  • Responsive design allowing for browser zoom to 400% and text scaling to 200%
  • Interactive elements have high-contrast visible focus indicators
  • Interactive elements have appropriate accessible names and programmatic roles set
  • Page markup is structured with a logical heading order and include appropriate landmark elements
  • Form text labels for inputs are clearly identified and programmatically linked
  • Modals windows, where present, are programmatically communicated to assistive technologies
  • Pages have a logical focus order which follows the visual layout of information
  • Icons have appropriate text alternatives, where necessary
  • Tables adapt when browser is zoomed in, with scrollbars where necessary to preserve logical relationships of the data
  • Status messages and dynamic changes to the interface are automatically communicated to assistive technologies

Known accessibility limitations

Sections of the platform, such as the Analytics section, report pages, and in-product widgets are provided and maintained by third-party vendors (Tableau, Salesforce, Pendo). We acknowledge that these areas may currently have accessibility limitations and present a confusing experience to some users. These can include issues with keyboard navigation, focus management, ARIA menu roles, and insufficient color contrast. While we aim to provide an inclusive experience across all areas of the platform, these elements may not yet meet our internal accessibility standards.

We are actively working to remediate this and continue to collaborate with vendors and explore alternative solutions where necessary.

Improvements planned for the next two years

Over the next few years, we plan to phase out third-party components and bring all data analytics under the control of our development team. This will enable us to schedule and drive accessibility improvements in those areas on our own timeline.

We also aim to improve readability and accessibility of our data tables, to improve the experience when zoomed in.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: Ben Saunders at [email protected]

For accessibility support or feedback (e.g., on assistive technology or usability) related to Elsevier's products or services, contact the Elsevier Digital Accessibility Team: [email protected].

The Americans with Disabilities Act (ADA)

Our platform is designed and developed with accessibility in mind and aims to meet the requirements of the Americans with Disabilities Act (ADA) and other relevant standards.

Read more about Elsevier’s approach to the ADA.

Preparation of this accessibility statement

This statement was prepared by the EOAP product team.

It was last reviewed in March 2026.

Did we answer your question?

Recently viewed answers

Functionality disabled due to your cookie preferences

For further assistance: