How Can We Help?
Pure Portal Accessibility Statement (UK)Pure Portal Accessibility Statement (UK)
Accessibility statement for Pure Portal
This accessibility statement applies to Pure Portal, as provided by Elsevier to the customer organisation.
This website is run by [name of organisation]. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change contrast levels and text size browser or device settings
- navigate most of the website using a keyboard or speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible:
- UN Sustainable Development Goals and PlumX colours do not have enough contrast with the backgrounds
- On profile details and article details: the canvas graphs have tooltips that appear on mouse hover that cannot be hovered without disappearing.
- The popups for the Plum and Altmetric images cannot be reached and read by screen readers.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: Irina Bischof at i.bischof@elsevier.com.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email i.bischof@elsevier.com
We’ll consider your request and get back to you in 14 days.
If you cannot view the map on our ‘contact us’ page, call or email us here for directions.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
Elsevier is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.
This website is partially compliant with the [Web Content Accessibility Guidelines version 2.1 AA standard, due to the exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Disproportionate burden
Navigation and accessing information
Visuals | ||
WCAG 2.1 Checkpoint |
Supporting Features |
Remarks |
1.4.3: Color Contrast (Minimum) (AA) |
Partially supports |
Most text has enough contrast with its corresponding background.
Note: University Branding will change the link colors which can cause color contrast violations.
Exceptions: Homepage: Many of the UN Sustainable Development Goals white text does not have enough contrast with the yellow/green/light blue/orange backgrounds, usually under 3.0:1 ratio required for text within images.
Profile Details, Research Unit Details, Article Details: The PlumX orange, green, and purple text does not have enough contrast.
Profile Details: The page can contain the UN Sustainable Development Goals, some of which do not have enough contrast for text within images. |
1.4.5: Images of Text (AA) |
Partially supports |
No images of text are used other than for Logos or essential presentation in most areas.
Exceptions: Homepage: The UN Sustainable Development Goals all use images of text for the menu buttons.
Profile Details: The UN Sustainable Development Goals all use images of text. |
1.4.13 Content on Hover or Focus (AA) (2.1) Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissable Hoverable Persistent |
Partially supports |
There are tooltips that appear on hover and focus that are not hoverable.
Exceptions: Profile Details, Article Details: The canvas graphs have tooltips that appear on mouse hover that cannot be hovered without disappearing.
Advanced Search: The information tooltips are not dismissable. |
Keyboard | ||
WCAG 2.1 Checkpoint |
Supporting Features |
Remarks |
1.3.2: Meaningful Sequence (A) The correct reading sequence can be programmatically determined |
Partially supports |
The correct reading sequence is logical with the DOM order matching the visual order. A few irregularities occur with how screen readers read out text.
Exceptions: Profile Details, Research Unit Details, Article Details: The popups for the Plum and Altmetric images cannot be reached and read by screen readers. |
2.1.1: Keyboard (A) All functionality is available from a keyboard, except for tasks such as drawing |
Partially supports |
Most content is keyboard operable.
Exceptions: Profile Details, Research Unit Details, Article Details: The interactive portions of the canvas graphs cannot be reached by keyboard. The popups for the Plum and Altmetric images cannot be activated by keyboard.
Profile Details: The email link cannot be reached by keyboard. |
Users can tab through the elements of a page in a logical order |
Partially supports |
Tab order and focus management is logical on the site in most areas.
Exceptions: |
Headers and Structure | ||
WCAG 2.1 Checkpoint |
Supporting Features |
Remarks |
Specify the language of text passages that are in a different language than the default language of the page. |
Partially supports |
There can be instances of various research output (publications, activities, etc.) that can be in a different language than the page default, but they are not marked with a lang attribute. |
4.1.1: Parsing (A) Use valid, error-free HTML |
Partially supports |
HTML and CSS passes concerning these 4 specific criteria: (i) elements have complete start and end tags, (ii) elements are nested according to their specifications (iii) elements do not contain duplicate attributes (iv) any IDs are unique, except where the specifications allow these features.
Profile Details: The copyright tooltips all share the same ID. |
Labeling | ||
WCAG 2.1 Checkpoint |
Supporting Features |
Remarks |
For all UI components, the name, value, and role can be programmatically determined. |
Partially supports |
UI components communicate their state programmatically in most cases.
Exceptions: Homepage: The image slideshow has incorrect ARIA markup that would cause confusion.
Profile Details: The contact modal should have aria-modal="true" and a proper label. |
Multimedia | ||
WCAG 2.1 Checkpoint |
Supporting Features |
Remarks |
Users can stop, pause, or hide moving, blinking, scrolling, or auto-updating information. |
Partially supports |
There is no moving, blinking, or scrolling content on most pages.
Exceptions: Homepage: There is an auto-rotating image slideshow that cannot be paused. |
We’ve assessed the cost of fixing the issues above. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the new interface for Pure Portal is built by the end of 2026.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on the 24th of June 2024.
This website was last tested on the 4th of August 2023 against the WCAG 2.1 AA standard.
The test was carried out by the Elsevier accessibility team using the following key tools and methods: Hands-on keyboard operation, Firebug/Code inspection, Firefox Web Developer Toolbar (removing style sheets), JAWS 18 on Mozilla Firefox 63 and MS IE 11 on Windows 10, NVDA screen reader v2019.2.1, Wave Extension, Color Contrast Analyzer, W3C WAI Pages
You can read the full accessibility test report here.
Updated at June 25, 2024