Introduction
Accessibility is a core aspect of ORCID’s vision of ‘a world where all who participate in research, scholarship, and innovation are uniquely identified and connected to their contributions across disciplines, borders, and time.’ One of ORCID’s values is inclusivity, and we strive to ensure that every member of the ORCID community feels welcome, respected, and treated with dignity, and we are committed to making our websites, applications, tools, and services accessible to the widest possible audience, regardless of technology or ability.
Our Commitment to Accessibility
ORCID endeavors to meet level Double-A (AA) of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines 2.2 These guidelines provide detailed information on how to make web content more accessible for everyone.
Level of conformity
The ORCID registry and info.orcid.org is partially conformant with both WCAG 2.1 and WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
As of October 2026, ORCID is WCAG 2.2 compliant across most of the infosite ( info.orcid.org) and we are working towards more complete compliance on the registry (orcid.org.)
See below for more on how we are working towards greater accessibility for all and what work we have completed so far.
info.orcid.org
As of October 2026 ORCID is accredited WCAG 2.2 compliant over a subset of the infosite ( info.orcid.org) pages and also the ORCID homepage, see our DAC Silver accreditation Certificate for more details. By extension we have worked to make the whole of info.orcid.org WCAG 2.2 compliant. As the audit was based on a subset of the very large number of pages we host on the info site, there may be a small number of pages that have accessibility issues due to legacy issues. As we become aware of these, we will address them.
orcid.org
We are continuing to make progress towards WCAG 2.2 compliance in the ORCID Registry and have made significant inroads into the number of issues found in the Registry since we started this process in 2023.
Scope
orcid.org, info.orcid.org
The statement covers the ORCID registry – including the homepage, sign-in, registration, my-orcid, search and the public record landing pages as well as our informational pages hosted on info.orcid.org.
Other subdomains of orcid.org
We rebuilt our user support site, support.orcid.org, in 2023 with accessibility requirements in mind. Although we believe support.orcid.org to be broadly accessible, it requires auditing before it can be included in this statement. Once auditing is complete we will update this statement to include the findings.
3rd party tools and services
Where services or tools used on ORCID.org have been supplied by a 3rd party, this content is not covered by the commitments set out in this statement. We regularly review agreements with these 3rd party providers, assess accessibility within our procurement processes, and actively work to improve the accessibility of our 3rd party integrations.
We actively work with our tool providers to continually improve the accessibility of their tools and their implementation in the ORCID Registry. One example of this is our fixes to cookie consent in late 2024 which removed barriers to use for screen readers.
Technical specifications
Accessibility of the ORCID registry and info.orcid.org relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
- HTML
- WAI-ARIA
- CSS
- JavaScript
- WordPress
These technologies are relied upon for conformance with the accessibility standards used.
Technical prerequisites for using the ORCID registry
Meeting the standards
ORCID is continually looking to improve the accessibility of our websites, applications, tools, and services. Our design, development, and quality assurance processes have accessibility ‘baked in’ from the outset. We focus on making the registry functionally usable as well as conformant.
Measures taken to ensure accessibility:
- Targeted accessibility work.
- We prioritize specific accessibility improvements when possible and reserve time to do so.
- Continual improvements.
- Whenever we update a user interface component, we incorporate changes to make it conform to WCAG2.2 and as accessible as possible.
- Accessibility fully incorporated into the QA process.
- New features are checked for keyboard navigation, screen reader accessibility, flexibility of content across multiple devices, and compatibility with a wide range of desktop and mobile browsers.
- External auditing.
- The ORCID registry and info site have been externally audited by the Digital Accessibility Centre. We used their feedback to prioritize and inform our development.
- ORCID accessibility guidelines.
- Detailed guidance for accessible design and development is in place and regularly updated.
Our opportunities for improvement
The remaining WCAG2.2 conformance issues are in the following areas:
orcid.org
- Drag and drop.
- Users cannot reorder lists of items with a keyboard
- Focus order and styling.
- Users may encounter unexpected focus order
- Focus styling on certain components can be unclear
- Session time outs
- After a period of inactivity users are timed out of the Registry without warning
- Users cannot stop the timeout or change the duration
- Communicating status changes and notices.
- Dynamic changes in status or page information are sometimes not communicated to screen reader users
- Semantic grouping of elements.
- Visually grouped elements that are not marked up as such
- Communicating button state
- Button states, in particular those operating show/hide functionality, don’t communicate state effectively
- It may not be clear to screen reader users if a panel is open or closed
info.orcid.org
We were audited by DAC on a specific subset of pages indicated in the certificate, although every effort was made to fix the problems indicated in the testing everywhere else they existed across info.orcid.org there may be incidences where we have missed them. We continue to monitor and fix accessibility problems as we find them and are aware that there may be some areas, particularly on legacy blog posts and older pages, that still need some attention. These are:
- PDFs
- Videos
- Embedded Documents
Exemptions
- Where content in ORCID records has been supplied to ORCID in a mix of two or more languages we cannot guarantee that the languages used are marked up in the appropriate fashion.
Contact us
Please get in touch with ORCID if you:
- Have a problem accessing or using an ORCID website or application
- Need ORCID content in an alternative, accessible format
- Have a suggestion on how we could further improve our accessibility
- Would be interested in taking part in accessibility testing with ORCID
Who to contact
The ORCID support team will make sure your enquiry reaches the right people at ORCID to help you with your issue. We will get back to you as soon as we can.
Contact the ORCID support team
ORCID’s Accessibility Progress
In 2023 we made significant progress towards WCAG 2.1 AA in the ORCID Registry and reduced the number of WCAG A and AA issues in the ORCID registry from 50 to 21.
In June 2023 we undertook a second accessibility audit, with our baseline standard now set to the newly-released WCAG 2.2.
In January 2024 we addressed several accessibility issues that occurred during registration and the sign in process , bringing the outstanding WCAG issue count down to 17.
In February 2025 we undertook an initial audit of info.orcid.org against the WCAG 2.2 standard which found 33 WCAG A and AA issues. We addressed all of those issues over the course of 2025. We then had the site retested in February 2026 which resulted in 4 A and AA issues. We worked on resolving these final issues into October 2026 when we had a final audit in which we had no A or AA issues and we received DAC Silver Accreditation for the pages we had audited.
Although the accreditation only covers a subset of the pages on the infosite, we took the time to try to resolve the issues that arose from testing these pages everywhere else they may have existed on the site.
Read more about our accessibility work on our blog.
Timeline
- Statement created on 22nd June 2020
- Last updated on 11th December 2023
- Last updated on 11th March 2024
- Last updated October, 2026
