(Based on VPAT® Version 2.4Rev)
Report Date: 24 August 2023
Name of Product/Version: SpringerLink (we do not version our software)
Product Description: SpringerLink provides researchers with access to scientific documents from journals, books, series, protocols, collections, reference works and proceedings. This report refers entirely to the accessibility of all web documents published at the subdomains link.springer.com and rd.springer.com (both subdomains are referred to as link.springer.com throughout this report), and supporting informational pages such as journal homepages located at the top level domain, springer.com. Also included are all web documents included in the purchasing and subscription process, found at order.springer.com.
Contact information: Please contact your Institutional Sales representative.
Notes:
Evaluation Methods Used: Conformance to the listed accessibility standards has been evaluated by Springer Nature's dedicated Accessibility Specialists. We use a combination of static analysis tools (including but not limited to axe by Deque, WAVE by WebAIM, and all of the tools described in our Frontend Playbook's Accessibility Guide). Our manual testing uses WCAG-EM as its base strategy, and further details are also described in our Frontend Playbook under the "Manual testing" and "Assistive technology" sections.
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
| Web Content Accessibility Guidelines 2.0 | Level A – Yes Level AA – Yes Level AAA – No |
| Web Content Accessibility Guidelines 2.1 | Level A – Yes Level AA – Yes Level AAA – No |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
| EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11) AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03) | Yes |
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.x Level AAA.
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
With rare exceptions, most images supplied by Springer Nature provide alternative text, or descriptions, or figure captions. We may use WAI-ARIA techniques to link some complex images with their descriptions if alternative text is unable to provide adequate context.
Images such as icons on user interface elements may be identified with visible text labels, visually-hidden text, or WAI-ARIA techniques. Some icons (e.g. "next" and "previous" pagination controls on search results pages) are known to have inadequate or missing text alternatives. We are actively working to find and repair these problems. We mark up some images so that they can be ignored by Assistive Technologies if they are pure decoration (as defined by WCAG 2.1). Third party scripts may inject non-text content without text alternatives, or with inadequate text alternatives. These include the Freshdesk customer services widget, and may include images in advertising scripts. When we become aware of deficiencies, we contact third party suppliers to request repairs. When supplied by authors who publish with us, some complex images may lack adequate alternative text, descriptions, and/or captions. Examples may include images of charts, graphs, or maps. Generally, these images are used to supplement text content. A large-scale and currently-active programme of work to improve alternative text content submitted by our authors is under way to address this. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
SpringerLink offers multimedia content through the third party MovingImage platform, or as downloadable video files in various formats.
Video-only and audio-only content are generally used to support existing text-based content. We currently have no method of confirming the inclusion of adequate media alternatives or transcripts. |
| 1.2.2 Captions (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
|
Partially supports |
SpringerLink offers multimedia content through the third party MovingImage platform, or as downloadable video files in various formats.
Captions and/or transcripts maybe be provided for some pre-recorded content in journals, books, series, protocols, reference works or proceedings. We currently have no method of confirming the inclusion of transcripts or captions. "Springer Nature Video" learning content published at link.springer.com/video uses the third party MovingImage platform. Both captions and transcripts are available. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
SpringerLink offers multimedia content through the third party MovingImage platform, or as downloadable video files in various formats.
Audio description is not generally used across our content, but some media may be presented alongside media alternatives such as text descriptions of video content. We currently have no method of confirming the inclusion of adequate media alternatives. |
| 1.3.1 Info and Relationships (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) may use unsemantic markup, including inadequate, misleading, or incorrectly-applied landmarks. Some UI controls (e.g. "next" and "previous" pagination controls on search results pages) lack accessible names. Pages may omit level one headings. On pages rendered in the newer design (currently articles, chapters, books, book series, reference works, reference work entries, and collections), we generally use progressive enhancement techniques and semantically-correct markup so that information, structure, and relationships can be understood independently of presentation. We make use of WAI-ARIA roles to support landmarks, and use WAI-ARIA roles and properties when required for more complex functionality such as popup menus and dialogs. Some complex functionality may omit required WAI-ARIA roles, states, or attributes, or misuse WAI-ARIA markup and techniques. We are actively working to find and repair these problems. The SpringerLink checkout process pages found at order.springer.com use multiple landmarks of the same type without unique labels. The pages use form fields that rely solely on built-in browser error checking, which can lead to error messages being unavailable for users with older browser technology, or Assistive Technology that doesn't support these features. Third party scripts may inject content with incorrect or absent information about structure and relationships. These may include content in advertising scripts and the Freshdesk customer services widget, among others. |
| 1.3.2 Meaningful Sequence (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | The meaning of the content on the pages of SpringerLink does not depend on the order of the sections. |
| 1.3.3 Sensory Characteristics (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The pages of this product do not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content.
Icons may be displayed to control functionality, but adjacent visible text labels or (less commonly) WAI-ARIA labels are also provided to ensure that relationships are available to Assistive Technologies. When supplied by authors who publish with us, some complex images may rely on sensory characteristics to be understood. Examples may include images of charts, graphs, or maps. Generally, these images are used to supplement text content. |
| 1.4.1 Use of Color (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Colour alone is generally not used to convey information in the pages of this product.
Links and icons may use colour to indicate hover or active states. These are supplemented with visible focus rings and/or background colours and/or text decoration underlines and/or luminosity differences per WAI techniques G183 and C15. Some complex images in journals, books, series, protocols, reference works and proceedings may rely on colour as the only visual means of understanding information. Examples may include images of charts, graphs, diagrams or maps. Generally, these images are used to supplement text content. |
| 1.4.2 Audio Control (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Content supplied by us does not play automatically.
All video with audio hosted through the third party MovingImage platform has a mechanism for pausing, stopping, and controlling volume. We play audio-only files directly on our pages. Audio files hosted by us are supplied as downloadable files only, for use in the users' own media player. Third party advertisements may load video and audio that automatically starts, and may not provide adequate controls for pausing, stopping, and/or controlling volume. When we become aware of active advertisements with these problems, we immediately take steps to remove those advertisements from our pages. |
| 2.1.1 Keyboard (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The majority of components in this product can be navigated by keyboard alone. We also provide skip links for bypassing repetitive navigation elements.
Third party advertising scripts may inject content that cannot be interacted with easily or at all by keyboard. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 2.1.2 No Keyboard Trap (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Keyboard trapping inside components on SpringerLink pages is rare, and in most cases is managed appropriately, allowing focus to be moved away from any component using standard keystrokes (tab, shift, esc).
Modal dialogs (including those generated by third party scripts) may trap focus and provide inadequate methods of escaping. When we become aware of deficiencies, we actively work on repairs of our own, and with third party vendors where required. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to: EN 301 549 Criteria
|
Not Applicable | This product does not implement character key shortcuts. |
| 2.2.1 Timing Adjustable (Level A)
Also applies to: EN 301 549 Criteria
|
Not applicable | No time limits are set by the content in the pages of this product. |
| 2.2.2 Pause, Stop, Hide (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Moving, blinking or scrolling content on SpringerLink pages generally does not start automatically, and is complemented by controls that allow users to pause or otherwise stop the content. When supplied by authors who publish with us, moving images in the form of GIFs may not meet this criterion.
Third party advertising scripts may inject content that automatically moves or blinks and lasts more than five seconds, without providing a mechanism to pause, stop, or hide that content. |
| 2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | The pages of this product do not contain anything that flashes. |
| 2.4.1 Bypass Blocks (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The pages of this product generally use semantically-correct markup so that Assistive Technology users can recognise elements and move around them accordingly. We make use of WAI-ARIA roles to support landmarks. We also provide skip links for bypassing repetitive navigation elements.
Pages located at order.springer.com have landmarks present. Some are duplicated without unique labels. |
| 2.4.2 Page Titled (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
SpringerLink pages mostly have unique page titles that describe the purpose of the page.
Where multiple versions of the same content exist (e.g. in original research that has been updated), the page titles do not differentiate between versions. |
| 2.4.3 Focus Order (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The meaning and/or operation of content on SpringerLink is generally unaffected by focus order.
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design. Some pages rendered in the older design may contain components where some items in the focus order do not match the visual order (for example the "date published" filtering on search results pages). On pages rendered in the newer design (currently articles, chapters, books, book series, reference works, reference work entries, and collections), the focus order of page content matches the visual order. Third party scripts including advertising scripts or customer services widgets (among others), may inject content where the focus order does not match the visual order. The operation and meaning of these components should be unaffected by the focus order. |
| 2.4.4 Link Purpose (In Context) (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Generally, the purpose of each link in this product can be determined by its descriptive text label. Most linked images or icons have alternative text or supplementary text labels. Some images, such as icons on user interface elements, are known to have inadequate or missing text alternatives. We are actively working to find and repair these problems.
In submitted articles, anchor links that refer to supplementary figures or tables may have insufficient context in their link text (e.g. figure numbers only). In limited cases we may support inadequate link text with the use of WAI-ARIA techniques. We are actively working to repair these problems. Third party scripts including advertising scripts, the Disqus commenting widget, survey or customer services widgets (among others), may inject content that includes links with no accessible text, or poorly-named accessible text. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to: EN 301 549 Criteria
|
Not Applicable | This product does not contain any functionality that uses multipoint or path-based gestures for operation. |
| 2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to: EN 301 549 Criteria
|
Supports | All functionality that can be operated using a single pointer can also be cancelled using standard browser and operating system methods. |
| 2.5.3 Label in Name (Level A 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports | In most cases where controls contain visible text, that text is also the label for the control. We are continually working to find and repair instances that do not meet this criterion. |
| 2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to: EN 301 549 Criteria
|
Not Applicable | This product does not contain any functionality that can be operated by device motion or user motion. |
| 3.1.1 Language of Page (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | Pages in this product may contain mixed languages, though the primary language of the product is English. Most pages have a `lang="en"` attribute applied to the `html` element, except for older legacy pages (for example the search results page) which allows the user to switch between English and German. On switching to German, a `lang="de"` attribute is applied to the `html` element instead. |
| 3.2.1 On Focus (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | Components in the interface of the pages of this product that receive focus do not initiate a change of context. |
| 3.2.2 On Input (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | Changing the setting of any user interface component does not automatically cause a change of context on any of the pages of this product. |
| 3.3.1 Error Identification (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Where user input errors are automatically detected by our own software, those errors are identified with warning text adjacent to the input field. We do not rely on visual characteristics alone (e.g. colour) to indicate user input errors.
In some parts of the site, we additionally use an `aria-describedby` property to associate error messages with invalid fields. User account pages located at link.springer.com/account use unsemantic, unassociated, `label` elements to mark up errors. Pages located at order.springer.com rely solely on built-in browser error checking, and do not identify errors in text. Some users with and without Assistive Technology may be unable to access these error states. |
| 3.3.2 Labels or Instructions (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) generally display visible and appropriately associated labels for input fields. Exceptions include the pagination number field on advanced search results pages and in the main search component in the page banner, both of which omit any label or WAI-ARIA description, and use only placeholder text as instruction. We are actively working to find and repair these problems. Pages rendered in the newer design (currently articles, chapters, books, book series, reference works, reference work entries, and collections) generally display visible and appropriately associated labels for input fields. Instructions such as those that explain mandatory fields may be absent or only present at the end of forms. (e.g. some payment information pages). Additional instructions for specific input fields may not be adequately associated (e.g. with `aria-describedby`) with the fields they describe. We are actively working to find and repair these problems. |
| 4.1.1 Parsing (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Most of the pages of this product generally use semantically-correct markup that meets the HTML5 specification for interface elements.
Where errors exist, they are usually minor, such as the presence of invalid `alt` and `src` attributes in SVG image nodes (ignored by user agents). There are some instances of incorrectly-nested elements (e.g. "flow content" wrapped in "phrasing content"), also generally ignored by user agents. The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design. Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) have a slightly higher volume of parsing errors, which include more problematic errors such as `li` elements outside of `ul` elements and duplicate IDs, that may interfere with the ability of Assistive Technology to correctly identify some components. Ancillary static pages (e.g. the pages linked to at the footer of each page, such as Terms and Conditions, Legal Information, and Accessibility, among others) are hand-built in HTML, without the use of a dynamic templating system. Hand-built content may contain unclosed or illegally nested elements. When we become aware of content with these problems, we immediately take steps to repair the HTML. Pages located at order.springer.com contain parsing errors that may be problematic for Assistive Technology, including illegally-nested elements (including illegally-nested controls), invalid autocomplete values, and incomplete closing tags. Third party advertising scripts may inject content that omits start and end tags, contains duplicate attributes or illegally nested elements. When we become aware of active advertisements with these problems, we immediately take steps to remove those advertisements from our pages. |
| 4.1.2 Name, Role, Value (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The pages of this product generally use standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
In some cases, WAI-ARIA attributes have been omitted where they would be helpful (e.g. progress indicators are not marked up as step counters in the checkout flow). In other cases WAI-ARIA roles or attributes may be misused in ways that cause elements to have misleading semantics. We are actively working to find and repair these problems. Other third party scripts, including the Freshdesk customer services widget, may present elements that lack adequate names and roles, making them difficult for screen reader users to access. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA)
Also applies to: EN 301 549 Criteria
|
Not Applicable | We do not publish live video. |
| 1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to: EN 301 549 Criteria
|
Does Not Support | We do not generally provide audio description for prerecorded video. A limited form of audio description may be provided for some pre-recorded content, but we currently have no method of confirming the inclusion of audio description. |
| 1.3.4 Orientation (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Supports | This product does not contain any content that restricts its view and operation to a single display orientation, such as portrait or landscape. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports | Some form fields (for example checkout flows) have autocomplete values that allow the field purpose to be determined programmatically, though this functionality is not universal across this product. |
| 1.4.3 Contrast (Minimum) (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) use gradient background images that do not meet minimum contrast requirements between the text and one or more of the gradient background colours. Images of product covers (e.g. journals, books displayed on the [homepage](https://link.springer.com)) may contain text that does not meet WCAG AA contrast guidelines. On the homepage, these images are supplemented with visible text labels. Pages rendered in the newer design (currently articles, chapters, books, book series, reference works, reference work entries, and collections) meet WCAG AA contrast ratio requirements. Third party advertising scripts may inject content with insufficient contrast. |
| 1.4.4 Resize text (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The pages of this product can generally be resized without Assistive Technology up to 200 percent without loss of content or functionality.
Third party advertising scripts may inject non-responsive content that loses or obscures information when text is resized or the screen is magnified. |
| 1.4.5 Images of Text (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
With some exceptions, the pages of this product generally do not use images of text to convey information except in the case of logotypes (considered essential per WCAG 2.1) or when the image is pure decoration.
Exceptions where this criterion is not met may include:
CMS content and published books and papers may include complex images that contain images of text. In most cases these images are used to supplement the text content they appear alongside. In some cases (e.g. charts, graphs, or maps, among others), the text content presented alongside may be insufficient to explain the contents of the image. A large-scale and currently-active programme of work to improve alternative text content submitted by our authors is under way to address this. Third party advertising scripts may inject images containing text. |
| 1.4.10 Reflow (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports | Most parts of this product are responsive. Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, except where necessary. Examples of necessary exclusions that are permitted under the guidelines include the display of large tables or figures - in these cases we provide an additional "full screen" view so that more data can be visible at once.
Third party advertising scripts may inject non-responsive content that loses or obscures information when text is resized or the screen is magnified. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) contain user interface icons that do not meet minimum contrast requirements for non-text content. When supplied by authors who publish with us, Graphical Objects (e.g. charts, graphs, or maps, among others) may have inadequate contrast. Third party content (e.g. advertising, customer services widgets) may inject non-text elements with inadequate contrast. When we become aware of deficiencies, we immediately take steps to request repairs from third party vendors. |
| 1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
No loss of content or functionality occurs by setting the text spacing properties specified by this criterion anywhere in this product, except for the search results page and [homepage](https://link.springer.com) where a collision may occur between some of the filters.
The search results page is rendered in an older design - we are in the process of transferring this content from the older design to the newer design which will pass this criterion. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Does Not Support |
Additional content that becomes visible on hover or focus (for example tooltips) is rare in this product. In cases where content is initially hidden and displayed on interaction, we also trigger that display with the tab key.
Content triggered in this way does not meet this criterion's requirements for Dismissable (the content cannot be dismissed without changing focus) or Hoverable (the pointer cannot be moved over the additional content without it disappearing). |
| 2.4.5 Multiple Ways (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Users may use the search function or the provided category browsing links to access any part of this product. The main navigation component can also be used to access the main content index pages.
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design. |
| 2.4.6 Headings and Labels (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) may incorrectly use `label` elements for other purposes (e.g. for error messages on account management pages), omit labels for some functionality (e.g. the pagination number field on advanced search results pages and the text input for the main search component in the page banner). Level one headings are omitted on some pages (e.g. search results pages). Other pages have multiple level one headings (e.g. static ancillary pages such as link.springer.com/termsandconditions). Some informational pages (e.g. Journal updates) do not use correctly-structured heading levels. We are actively working to find and repair these problems. Pages rendered in the newer design (currently articles, Chapters, books, book series, reference works, reference work entries, and collections) use correctly-structured headings and generally display visible and appropriately associated labels for input fields. |
| 2.4.7 Focus Visible (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) use default browser focus rings only for interactive components. Pages rendered in the newer design (currently articles, chapters, books, book series, reference works, reference work entries, and collections) use highly-visible focus styles, including yellow focus rings or yellow backgrounds. Pages found at order.springer.com use default browser focus rings only for interactive components. Third party scripts, including advertising, may inject components that remove focus styles. |
| 3.1.2 Language of Parts (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Content in journals, books, series, protocols, reference works or proceedings may include or be completely composed of text in languages other than that defined in the HTML `lang` attribute. Mixed language content may be marked up with a separate `lang` attribute that matches the written language, though this is not consistently applied.
Titles in the cart at order.springer.com may be published in multiple languages. The correct `lang` attribute for titles in a language different to that of the overall document is omitted. Third party scripts may inject components that use a different language to the page content - for example a targeted advertisement may use the native language of the user, and not be marked up with a separate `lang` attribute. |
| 3.2.3 Consistent Navigation (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate, inconsistent designs. The designs have different navigation methods, within the same collections of pages. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design are currently journals, and ancillary pages such as search, indexes, and account management. Pages rendered in the newer design are currently articles, chapters, books, book series, reference works, reference work entries, and collections. When the transfer process is complete, the navigation methods between designs will be broadly consistent. Pages that deal with sensitive information (for example payment pages) have intentionally simpler designs, and do not share the same navigation system as the main site. The navigation of each of these sets of pages is internally consistent. |
| 3.2.4 Consistent Identification (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The SpringerLink website contains content that is rendered in two separate, inconsistent designs. We are in the process of transferring all content from the older design to the newer design.
Pages rendered in the older design are currently journals, and ancillary pages such as search, indexes, and account management. Pages rendered in the newer design are currently articles, chapters, books, book series, reference works, reference work entries, and collections. When the transfer process is complete, content will use a unified design style with consistent presentation and functionality. Pages that deal with sensitive information (for example payment pages) have intentionally simpler designs. The presentation of each of these sets of pages is internally consistent, and the tasks performed are unlike those performed elsewhere on the site. |
| 3.3.3 Error Suggestion (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Where user input errors are automatically detected by our own software, those errors are identified to the user with warning text adjacent to the input field. Unless it would present a risk to security, the warning text describes the error and what the user should do to correct it.
The SpringerLink website contains content that is rendered in two separate designs. We are in the process of transferring all content from the older design to the newer design. Pages rendered in the older design (currently journals, and ancillary pages such as search, indexes, and account management) use unsemantic, unassociated `label` elements to mark up errors. Pages located at order.springer.com rely solely on built-in browser error checking, and do not identify errors in text. Some users with and without Assistive Technology may be unable to access these error states. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to: EN 301 549 Criteria
|
Supports | Payment pages at order.springer.com have a checkout flow that includes a verification step. There, the user must confirm that their choices are correct before they may enter their payment details. At this stage they may return to a previous step to make corrections, cancel, or abandon the process. |
| 4.1.3 Status Messages (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports | Status messages that do not receive focus are presented in text. Some are marked up with programmatic roles (e.g. `role="alert"` on some error messages), but there is no consistent, single approach to status messages across the multiple designs. ARIA Live Regions are not generally used. |
Notes: This product has not been evaluated for WCAG 2.x Level AAA conformance.
Chapter 3: Functional Performance Criteria (FPC)
Notes: See WCAG section for full details.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | The majority of content is marked up for Assistive Technology. Some pages and interactive components may be difficult to use. Third party scripts may inject content with inadequate accessible alternatives. |
| 302.2 With Limited Vision | Partially Supports | Markup is written with support for Assistive Technology. Text is resizable by the user. The product does not impede the user from zooming into the page. Some functionality may be difficult to use at high magnification. Third party scripts may inject content with inadequate accessibility support. |
| 302.3 Without Perception of Color | Supports | Colour perception is not generally needed to use this product. |
| 302.4 Without Hearing | Partially Supports | Some but not all audio is supported by captions or transcripts. |
| 302.5 With Limited Hearing | Partially Supports | Some but not all audio is supported by captions or transcripts. |
| 302.6 Without Speech | Not Applicable | Speech is not needed to use this product. |
| 302.7 With Limited Manipulation | Partially Supports | This product supports standard input mechanisms such as keyboards, pointing devices, and speech input. Fine motor control and simultaneous actions are not required to operate this product. Third party scripts may inject content that is difficult to use without a pointing device. |
| 302.8 With Limited Reach and Strength | Partially Supports | This product supports standard input mechanisms such as keyboards, pointing devices, and speech input. Some content requires the use of a mouse. Third party scripts may inject content that is difficult to use without a pointing device. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | The pages of this product comprise multiple designs with inconsistent presentation between designs. Each design is internally consistent. Clear labels, titles, and accessible names are generally used for controls. Some pages lack accessible names for some controls and fail to explain the meanings of icons. Third party scripts may inject content with inconsistent or absent labelling of interface components. |
Chapter 4: Hardware
Notes: This product is a web software application and is not subject to the requirements of this chapter.
Chapter 5: Software
Notes: See WCAG section for full details.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.1 AA | See WCAG 2.1 section | See information in WCAG section |
| 502 Interoperability with Assistive Technology | ||
| 502.2.1 User Control of Accessibility Features | Not Applicable | This product is not considered platform software as defined by Section 508. See E103 Definitions, section E103.4. |
| 502.2.2 No Disruption of Accessibility Features | Not Applicable |
This product has no platform features as defined by Section 508. The product is compatible with operating system and browser accessibility features configured by the user.
Third party scripts may inject content that disrupts standard operating system and browser accessibility features. See information in WCAG section for complete details. |
| 502.3 Accessibility Services | ||
| 502.3.1 Object Information | Partially Supports |
Object role, state(s), properties, boundary, name, and description are generally programmatically determinable, with some exceptions.
See WCAG sections 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.3 Sensory Characteristics, 2.4.4 Link Purpose (In Context), 3.3.2 Labels or Instructions, 4.1.1 Parsing, 4.1.2 Name, Role, Value, 1.4.3 Contrast (Minimum), and 2.4.6 Headings and Labels for further detail. |
| 502.3.2 Modification of Object Information | Partially Supports |
The pages of this product use standard HTML or WAI-ARIA object roles for maximum compatibility with Assistive Technologies, with some exceptions.
See WCAG sections 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.3 Sensory Characteristics, 2.4.4 Link Purpose (In Context), 3.3.2 Labels or Instructions, 4.1.1 Parsing, 4.1.2 Name, Role, Value, 1.4.3 Contrast (Minimum), and 2.4.6 Headings and Labels for further detail. |
| 502.3.3 Row, Column, and Headers | Partially Supports |
Data tables in journals, books, series, protocols, reference works or proceedings may not be marked up with adequate table header information.
Data tables in dynamic templates are rare, but where they do appear, they are marked up with standard HTML `table` elements. Row headers are present and associated with rows and columns as necessary. |
| 502.3.4 Values | Supports | The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with Assistive Technologies. |
| 502.3.5 Modification of Values | Supports | The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with Assistive Technologies. |
| 502.3.6 Label Relationships | Partially Supports |
Generally, the pages of this product use labels on components that require user input, with some exceptions.
See WCAG sections 2.4.6 Headings and Labels and 3.3.2 Labels or Instructions for further detail. |
| 502.3.7 Hierarchical Relationships | Partially Supports |
The pages of this product generally use standard HTML to express hierarchy, with some exceptions and errors. Third party scripts may inject content that obscures the relationships between components.
See WCAG sections 1.3.1 Info and Relationships, and 2.4.6 Headings and Labels for further detail. |
| 502.3.8 Text | Partially Supports |
The pages of this product use standard plain text in HTML.
Content in journals, books, series, protocols, reference works or proceedings may contain images of text without adequate programmatically determinable alternatives. |
| 502.3.9 Modification of Text | Supports | The pages of this product use standard HTML for user input. |
| 502.3.10 List of Actions | Supports | The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with Assistive Technologies. |
| 502.3.11 Actions on Objects | Partially Supports |
The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with Assistive Technologies. Some content, including that injected by third party scripts, cannot be interacted with easily or at all by keyboard or by other Assistive Technologies.
See WCAG sections 1.3.1 Info and Relationships, and 2.1.1 Keyboard for further detail. |
| 502.3.12 Focus Cursor | Partially Supports |
We provide focus styles on all focusable elements. Third party scripts may inject components that remove focus styles or alter focus in a way that makes them difficult to perceive by all users.
See WCAG sections 1.4.1 Use of Color and 2.4.7 Focus Visible for further detail. |
| 502.3.13 Modification of Focus Cursor | Supports | The pages of this product use standard HTML elements and cursor controls for user input that may be overridden by Assistive Technology. |
| 502.3.14 Event Notification | Partially Supports |
The pages of this product use standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
Some components omit or misuse WAI-ARIA attributes in a way that prevents users of some Assistive Technologies from being able to perceive changes in state. We are actively working to find and repair these problems. Some third party scripts may inject content that fails to notify users of changes in state. See WCAG sections 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value for further detail. |
| 502.4 Platform Accessibility Features | Not Applicable | This product is not considered platform software as defined by Section 508. See E103 Definitions, section E103.4. |
| 503 Applications | ||
| 503.2 User Preferences | Supports | This product does not override user selected contrast and colour selections and other individual display attributes. |
| 503.3 Alternative User Interfaces | Not Applicable | We do not provide any alternative user interface for this product that functions as Assistive Technology. |
| 503.4 User Controls for Captions and Audio Description | ||
| 503.4.1 Caption Controls | Partially Supports | Not all video content provides captions. Where captions are provided, the controls for adjusting those captions are found at the same menu level as the user controls for volume or program selection. |
| 503.4.2 Audio Description Controls | Does Not Support | Audio description is not generally used across our content. |
| 504 Authoring Tools | ||
| 504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | Not Applicable | This product is not used as an authoring tool. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | This product is not used as an authoring tool. |
| 504.2.2 PDF Export | Not Applicable | This product is not used as an authoring tool. |
| 504.3 Prompts | Not Applicable | This product is not used as an authoring tool. |
| 504.4 Templates | Not Applicable | This product is not used as an authoring tool. |
Chapter 6: Support Documentation and Services
Notes: This report covers accessibility conformance for the web product and does not provide Documentation or Support Services.
Chapter 4: 4.2 Functional Performance Statements (FPS)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | See Revised Section 508 Report Ch.3 302.1 | See Revised Section 508 Report Ch.3 302.1 |
| 4.2.2 Usage with limited vision | See Revised Section 508 Report Ch.3 302.2 | See Revised Section 508 Report Ch.3 302.2 |
| 4.2.3 Usage without Perception of Color | See Revised Section 508 Report Ch.3 302.3 | See Revised Section 508 Report Ch.3 302.3 |
| 4.2.4 Usage without hearing | See Revised Section 508 Report Ch.3 302.4 | See Revised Section 508 Report Ch.3 302.4 |
| 4.2.5 Usage with limited hearing | See Revised Section 508 Report Ch.3 302.5 | See Revised Section 508 Report Ch.3 302.5 |
| 4.2.6 Usage without vocal capability | See Revised Section 508 Report Ch.3 302.6 | See Revised Section 508 Report Ch.3 302.6 |
| 4.2.7 Usage with limited manipulation or strength | See Revised Section 508 Report Ch.3 302.7 and 302.8 | See Revised Section 508 Report Ch.3 302.7 and 302.8 |
| 4.2.8 Usage with limited reach | See Revised Section 508 Report Ch.3 302.8 | See Revised Section 508 Report Ch.3 302.8 |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | The pages of this product do not contain anything that flashes. |
| 4.2.10 Usage with limited cognition | See Revised Section 508 Report Ch.3 302.9 | See Revised Section 508 Report Ch.3 302.9 |
| 4.2.11 Privacy | Supports | Standard HTML and WAI-ARIA attributes are used on these pages. The product does not impede the user from using their own privacy tools when interacting with the content. |
Chapter 5: Generic Requirements
Notes: This product supports standard web Assistive Technologies and is therefore not subject to the Closed Functionality criteria described in this chapter.
Notes: This product does not offer two-way voice communication and is therefore not subject to the requirements of this chapter.
Chapter 7: ICT with Video Capabilities
Notes: See WCAG section for full details.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 7.1 Caption processing technology | ||
| 7.1.1 Captioning playback | Partially Supports | Some but not all audio is supported by captions. Where captions are available, the user can choose whether or not to display them. |
| 7.1.2 Captioning synchronization | Partially Supports | Some but not all audio is supported by captions. Where captions are available, they are synchronised with the audio. |
| 7.1.3 Preservation of captioning | Partially Supports | Some but not all audio is supported by captions. Where captions are available, we do not override the appearance of the default caption display. |
| 7.2.1 Audio description playback | Does Not Support | Audio description is not generally used across our content. |
| 7.2.2 Audio description synchronization | Does Not Support | Audio description is not generally used across our content. |
| 7.2.3 Preservation of audio description | Does Not Support | Audio description is not generally used across our content. |
| 7.3 User controls for captions and audio description | Partially Supports | Audio description is not generally used across our content. Some but not all audio is supported by captions. Where captions are available, the mechanism for selecting them is presented at the same level as other playback controls. |
Chapter 8: Hardware
Notes: This product is a web software application and is not subject to the requirements of this chapter.
Chapter 9: Web
Notes: Please see WCAG 2.1 section.
Chapter 10: Non-Web Documents
Notes: This product does not include non-web documents and is therefore not subject to the requirements of this chapter.
Chapter 11: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.0 General (informative) | ||
| 11.1.1 through 11.4.1.3 | See WCAG 2.x Section | See information in WCAG section |
| 11.5 Interoperability with assistive technology | ||
| 11.5.1 Closed functionality (informative) | ||
| 11.5.2.1 Accessibility services | ||
| 11.5.2.1 Platform accessibility service support for software that provides a user interface | See 11.5.2.5 through 11.5.2.17 | See information in 11.5.2.5 through 11.5.2.17 |
| 11.5.2.2 Platform accessibility service support for assistive technologies | See 11.5.2.5 through 11.5.2.17 | See information in 11.5.2.5 through 11.5.2.17 |
| 11.5.2.3 Use of accessibility services | See information in 11.5.2.5 through 11.5.2.17 | See information in 11.5.2.5 through 11.5.2.17 |
| 11.5.2.4 Assistive technology | Not Applicable | This product is not an Assistive Technology. |
| 11.5.2.5 Object information | See Revised Section 508 Report Ch.5 502.3.1 and 502.3.2 | See Revised Section 508 Report Ch.5 502.3.1 and 502.3.2 |
| 11.5.2.6 Row, column, and headers | See Revised Section 508 Report Ch.5 502.3.3 | See Revised Section 508 Report Ch.5 502.3.3 |
| 11.5.2.7 Values | See Revised Section 508 Report Ch.5 502.3.4 and 502.3.5 | See Revised Section 508 Report Ch.5 502.3.4 and 502.3.5 |
| 11.5.2.8 Label relationships | See Revised Section 508 Report Ch.5 502.3.6 | See Revised Section 508 Report Ch.5 502.3.6 |
| 11.5.2.9 Parent-child relationships | See Revised Section 508 Report Ch.5 502.3.7 | See Revised Section 508 Report Ch.5 502.3.7 |
| 11.5.2.10 Text | See Revised Section 508 Report Ch.5 502.3.8 and 502.3.9 | See Revised Section 508 Report Ch.5 502.3.8 and 502.3.9 |
| 11.5.2.11 List of available actions | See Revised Section 508 Report Ch.5 502.3.10 | See Revised Section 508 Report Ch.5 502.3.10 |
| 11.5.2.12 Execution of available actions | See Revised Section 508 Report Ch.5 502.3.11 | See Revised Section 508 Report Ch.5 502.3.11 |
| 11.5.2.13 Tracking of focus and selection attributes | See Revised Section 508 Report Ch.5 502.3.12 | See Revised Section 508 Report Ch.5 502.3.12 |
| 11.5.2.14 Modification of focus and selection attributes | See Revised Section 508 Report Ch.5 502.3.13 | See Revised Section 508 Report Ch.5 502.3.13 |
| 11.5.2.15 Change notification | See Revised Section 508 Report Ch.5 502.3.14 | See Revised Section 508 Report Ch.5 502.3.14 |
| 11.5.2.16 Modifications of states and properties | See Revised Section 508 Report Ch.5 502.3.14 | See Revised Section 508 Report Ch.5 502.3.14 |
| 11.5.2.17 Modifications of values and text | See Revised Section 508 Report Ch.5 502.3.5 and 502.3.9 | See Revised Section 508 Report Ch.5 502.3.5 and 502.3.9 |
| 11.6 Documented accessibility usage | ||
| 11.6.1 User control of accessibility features | Not Applicable | This product is not considered platform software as defined by EN 301 549 V1.1.2. See 3.1 Definitions. |
| 11.6.2 No disruption of accessibility features | Not Applicable | This product is not considered platform software as defined by EN 301 549 V1.1.2. The product does not impede the user in using accessibility features provided by their operating system and Assistive Technologies. |
| 11.7 User preferences | Supports | The pages of this product use standard HTML and CSS attributes that may be overridden in user-supplied style sheets. |
| 11.8 Authoring tools | ||
| 11.8.1 Content technology | ||
| 11.8.2 Accessible content creation (if not authoring tool, enter “not applicable”) | Not Applicable | This product is not used as an authoring tool. |
| 11.8.3 Preservation of accessibility information in transformations | Not Applicable | This product is not used as an authoring tool. |
| 11.8.4 Repair assistance | Not Applicable | This product is not used as an authoring tool. |
| 11.8.5 Templates | Not Applicable | This product is not used as an authoring tool. |
Notes: This report covers accessibility conformance for the web product and does not provide Documentation or Support Services.
Notes: This product does not provide any relay services, or access for Emergency Services.
This document is provided for information purposes only and the contents hereof are subject to change without notice. Springer Nature does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Springer Nature specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Springer Nature further makes no representation concerning the ability of Assistive Technologies or other products to interoperate with Springer Nature products. This document addresses the named product(s) or platforms only.