Enabling people with disabilities to access Scopus content quickly and easily

Scopus features, content and functions are designed to be accessible by all users and devices. We strive to adhere to the U.S. Section 508 Standards of the Federal Rehabilitation Act, as well as meet the World Wide Web Consortium's Web Content Accessibility Guidelines 2.0.

Our Scopus team consists of developers and user-centered designers who conduct usability testing and accessibility assessments of navigation, flow, labels and consistency. We test Scopus on a variety of devices and with assistive technology including JAWS screen reader, NVDA, keyboard only and a variety of browser testing tools.

Some of the accessibility features of Scopus include:

  • The user interface is well-structured HTML, CSS and JavaScript.
  • All primary functions in Scopus are operable using keyboard only, with logical tab order.
  • Search result pages show obvious highlighting of the row in focus to provide orientation for keyboard-only sighted users.
  • Scopus uses properly structured headings, allowing users of screen readers to navigate pages more quickly.
  • JavaScript functionality is operable using keyboard friendly event handlers.
  • Graphical elements such as images and icons are supplemented by HTML text attributes.
  • User interface panes and page sections are identified by headings.
  • Color coding is minimal and is supplemented by meaningful text.
  • Animated tutorials are also available as HTML text files.
  • Scopus uses separate CSS files and is also usable with CSS turned off.
  • Required fields are marked using asterisks
  • Form elements are tagged with <label>.
  • Scopus uses primarily standard HTML form elements such as checkboxes and radio buttons, which offer state information to assistive technology such as JAWS.
  • Pages have unique and descriptive page titles to help orient users of screen readers.
  • All content and controls are compatible with screen enlargement software in addition to compatibility with built-in browser zoom functionality.
  • Scopus does not have features that interfere with standard API features of the OS including MSAA (Microsoft Active Accessibility).
  • A skip navigation link is available for screen reader users.

Download the Scopus Web Content Accessibility Guidelines (WCAG) 2.0 Statement (pdf 367 kb).

Our commitment to testing & improving accessbility

Scopus takes a continuous improvement approach to web accessibility, testing new and existing pages for accessibility with each product release. We train our developers and create tools in house to improve accessibility compliance. And we partner with leading experts such as Michigan State University's Usability and Accessibility Research Center to test our product directly with users.

Elsevier & Accessibility


  • For immediate support, users can use the Live Chat feature of Scopus
  • To report an accessibility issue with Scopus or for questions about Scopus accessibility, please contact Elsevier's accessibility support group at
  • If you require electronic files for a student or staff member with a disability, you may use the Access Text Network or the Elsevier Disability Request Form to request a file.
  • For general Customer Service support for Scopus, please complete the HTML Contact Us Form.