Reaxys Accessibility Statement

Last updated on July 31, 2026

Commitment to accessibility

At Reaxys, we are committed to creating an inclusive and accessible platform that empowers all users, by enabling access and optimizing the experience for individuals with disabilities and impairments, including auditory, cognitive, physical, speech, and visual disabilities.

In alignment with the broader accessibility policies set forth by Elsevier RELX, we strive to meet the established standards for web accessibility, adhering to the World Wide Web Consortium's Web Content Accessibility Guidelines 2.1 Level A and AA as well as similar standards enacted by countries around the globe.

For more information on how Reaxys aligns with accessibility standards, we invite you to explore our Accessibility Conformance Report (ACR) document. This Accessibility Conformance Report was last updated July 14, 2026. To see the latest improvements, please refer to our Accessibility Roadmap.

Organizational measures and initiatives

Our commitment encompasses ongoing evaluation and enhancement of our platform to address the specific accessibility needs of our users.

We understand that fostering an inclusive platform is an ongoing journey that requires vigilance, education, and engagement.

Accessibility is a foundational aspect of our design and product development process. From the initial concept stage through to testing and deployment, we ensure that accessibility is a core consideration. Therefore, we have designated at least one accessibility champion in every main role—Product, Development, Quality Engineering, and User Experience. Each accessibility champion has completed Deque University’s Web Accessibility course.

Accessibility features

  • Pages feature skip links to main blocks of content as the first focusable items on the page
  • Pages are descriptively titled
  • Heading elements are generally well used to label blocks of content and landmark elements demarcate notable sections in the UI
  • Images, graphics and icons have text alternatives which describe their purpose
  • Text generally has a high level of color contrast except for a small number of areas
  • Content is typically presented in a logical programmatic reading order
  • Standard interactive controls can be reached and operated by keyboard alone
  • The product does not contain any keyboard traps
  • Interactive elements have a high contrast focus indicator
  • The default language of the page is programmatically determinable
  • There are many ways to navigate the site content including consistent main navigation, breadcrumb navigation, comprehensively indexed global search functionality, and a sitemap

Known issues

During the Reaxys development and testing cycles we care about accessibility and continuously working to improve any limitations:

  • Where mixed language records might not be marked with a language so that screen readers might not be able to detect the language of the part of the record correctly.
  • Reaxys does not yet fully support Reflow on every page which will be addressed via scheduled re-branding and further UI improvements.

Accessibility limitations in third-party components

We acknowledge that certain third-party components integrated into our platform, such as structure editors and the Resource Center, may currently have accessibility limitations. These can include issues with keyboard navigation, focus management, 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. As you might see in our accessibility roadmap, we are actively investigating how to improve these experiences, including collaborating with vendors and exploring alternative solutions where necessary.

Support and feedback

  • To report any accessibility issue or for accessibility support, please contact [email protected].
  • For general Customer Service support for Reaxys, please via the email option below.

Update overview: The Reaxy accessibility roadmap focuses on resolving key WCAG A and AA issues across search, search results, and core navigation. As of April 2026, we have made significant progress, with improvements to contrast, text spacing, keyboard navigation, and error identification. Remaining issues will be addressed primarily between 2026 and 2027, with major enhancements tied to reflow handling.

Did we answer your question?

Related answers

Recently viewed answers

Functionality disabled due to your cookie preferences

For further assistance: