(Based on VPAT® Version 2.4Rev)
Report Date: 18th August 2023
Name of Product/Version: Nature.com (we do not version our software)
Product Description:
Nature.com publishes peer-reviewed research, reviews and news across a number of journals. This report refers entirely to the accessibility of editorial, journal, and magazine web documents published at the top level domain of www.nature.com, including informational pages, and to all web documents found at idp.nature.com and payment.nature.com (for account management and subscription and payment management respectively).
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.
Background images such as icons on user interface elements are generally identified with visible text labels. Sometimes we may use visually-hidden text or WAI-ARIA techniques instead. 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). The Nature subscription pages at https://www.nature.com/nature/subscribe currently contain SVG images without text alternatives, and decorative SVG images that are not marked up to be ignored by Assistive Technologies. We are actively working to repair these problems. Third party scripts may inject non-text content without text alternatives, or with inadequate text alternatives. These include images in advertising scripts and in Disqus commenting widgets. 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 |
Nature.com has a diverse mix of multimedia content, both self-hosted and hosted on third party sites. Video-only content is generally used to support text-based content.
Audio-only content may be used to support text-based content. Audio-only content may also be used in Podcasts across various journals. Some but not all podcasts provide transcripts. While Nature Magazine generally provides transcripts and/or text descriptions of multimedia content in new Magazine articles, they may be absent from older Nature Magazine content and journal content supplied by authors who publish with us. 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 |
Nature.com has a diverse mix of multimedia content, both self-hosted and hosted on third party sites. Captions and/or transcripts may be provided for some pre-recorded content, but we currently have no method of confirming the inclusion of transcripts or captions.
While Nature Magazine generally provides captions and/or transcripts for pre-recorded content in new Magazine articles, they may be absent from older Nature Magazine content and journal content supplied by authors who publish with us. We currently have no method of confirming the inclusion of transcripts or captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Nature.com has a diverse mix of multimedia content, both self-hosted and hosted on third party sites. Audio description is not generally used across our content, but some media may provide 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 |
We generally use progressive enhancement techniques and semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.
We make use of WAI-ARIA roles to support (named) landmarks, and use WAI-ARIA roles and properties when required for more complex functionality such as popup menus and dialogs. We do not use WAI-ARIA where it is not required. Some parts of the checkout flow and the "My Account" pages contain unsemantic markup, including out-of-sequence headings and incorrectly-applied landmarks. We are actively working to find and repair these problems. Some functionality may omit required WAI-ARIA roles, states, or attributes, or misuse WAI-ARIA markup and techniques. When we become aware of content with these problems, we immediately take steps to repair the issues. Third party scripts may inject content with incorrect or absent information about structure and relationships. These include content in advertising scripts and in Disqus commenting widgets, among others. |
| 1.3.2 Meaningful Sequence (Level A)
Also applies to: EN 301 549 Criteria
|
Supports |
The meaning of the content in the pages of Nature.com does not depend on the order of the sections.
We use semantically-correct markup to allow Assistive Technologies to interpret the meaning of content and controls within each section. |
| 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 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 text decoration underlines and/or luminosity differences per WAI advisory techniques G183 and C15. When supplied by authors who publish with us, some complex images may rely on colour as the only visual means of understanding information. Examples may include images of charts, graphs, 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 audio files supplied by us, either hosted on our own platform or through a third party, have mechanisms for pausing, stopping, and controlling volume.
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 |
All first-party components in Nature.com can be navigated by keyboard alone. Complex elements like flyout menus can be exited with the esc key. 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. Other types of third party content such as JavaScript-based file viewers (e.g. Figshare), commenting systems (e.g. Disqus), or customer services widgets may be difficult to use with keyboard alone. When we become aware of deficiencies, we contact third party suppliers to request repairs. Additionally, where possible, we aim to provide equivalent alternatives to problematic content. |
| 2.1.2 No Keyboard Trap (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Keyboard trapping inside components on Nature.com 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).
Third party content such as survey modal dialogs or the Disqus commenting widget may trap focus and provide inadequate methods of escaping. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 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 |
Any moving, blinking or scrolling content on Nature.com generally does not start automatically, and is complemented by controls that allow users to pause or otherwise stop the content. Moving images in the form of gifs may not meet this criterion.
Automatically updating information is rare on Nature.com. The Disqus commenting widget may update new comments on screen automatically. If users are actively interacting with the widget, then new comments may be progressively disclosed to users at their request by activating a "load new comments" button. 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 |
We use semantically-correct markup so that Assistive Technology users can recognise elements and move around them accordingly. We make use of HTML and WAI-ARIA roles to support landmarks. We also provide skip links for bypassing repetitive navigation elements.
Some third party content, for example embedded widgets that provide alternative means of exploring data, may prevent users from being able to bypass repetitive information. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 2.4.2 Page Titled (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Most of the pages on Nature.com have unique page titles that describe the purpose of the page.
Some pages (e.g in checkout flows) do not have unique page titles at every stage in a process. We are actively working to find and repair these problems. |
| 2.4.3 Focus Order (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The meaning or operation of the pages on Nature.com is generally unaffected by focus order. Additionally, in most cases, the focus order of all page content matches the visual order.
Third party scripts including advertising scripts, the Disqus commenting widget, or survey 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 first party links can be determined by their descriptive text labels. Links that are not primarily text-based (e.g. images or icons) have alternative accessible text or supplementary text labels.
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
|
Supports | This product generally does not contain any functionality that uses multipoint or path-based gestures for operation.
Special feature content may use multipoint gestures for functionality such as pan and zoom controls. Alternatives to multipoint gestures are provided, including single point and keyboard controls. For complex functionality, simple instructions may be provided to explain the available options. |
| 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. Some third party scripts may inject content that does not meet this criterion. Supplementary pages (such as special features or marketing pages) may fail to 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 | All of the pages in this product use the language attribute on the HTML element to specify the default language of the page. |
| 3.2.1 On Focus (Level A)
Also applies to: EN 301 549 Criteria
|
Supports | Components in the interface of the pages 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. |
| 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).
Pages located at payment.nature.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. Third party scripts including the Disqus commenting widget, or other widgets that accept user input, may automatically detect errors but fail to present the errors to users in text. They may rely on visual characteristics alone to indicate user input errors, or place error text in locations that are difficult for screen reader users to access. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 3.3.2 Labels or Instructions (Level A)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Generally, visible and appropriately associated labels are provided for input fields. In limited cases, a visually-hidden label may be provided instead, but we prefer to avoid this pattern.
Additional instructions for specific input fields may not be adequately associated (e.g. with WAI-ARIA) 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 |
The pages of this product generally use semantically-correct markup that meets the HTML5 specification for interface elements. Some very old archived content may occasionally contain unclosed or illegally nested elements.
Third party advertising scripts may inject content that omits start and end tags, contains duplicate attributes or contains 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.
WAI-ARIA attributes may be omitted where they would be useful, for example to support HTML5 features that are not widely supported by client technology. 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 Disqus commenting widget, may present interactive elements such as tooltips 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 | A limited number of form fields may have autocomplete values that allow the field purpose to be determined programmatically, but we have not widely implemented this functionality. |
| 1.4.3 Contrast (Minimum) (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Generally, all text and images of text supplied by us on the pages of this product have a contrast ratio of at least 4.5:1.
Some placeholder text (e.g. on payment pages) may have insufficient contrast. We are actively working to find and repair these problems. 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 |
All first party text on the pages of this product can be resized up to 400% without loss of information or functionality.
Third party scripts (for example advertisements) may inject non-responsive content that loses or obscures information when text is resized. |
| 1.4.5 Images of Text (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Outside of editorial content managed by content management system (CMS), the contents of author-submitted published books and papers, and third party scripts, the pages of this product 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.
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 images of text. |
| 1.4.10 Reflow (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Supports | All 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.
|
| 1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
The visual presentation of User Interface Components in this product have a contrast ratio of at least 3:1 against adjacent colours.
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
|
Supports | No loss of content or functionality occurs by setting the text spacing properties specified by this criterion anywhere in this product.
Third party content (e.g. advertising, customer services widgets) may inject elements that fail to meet this criterion. When we become aware of deficiencies, we immediately take steps to request repairs from third party vendors. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to: EN 301 549 Criteria
|
Partially Supports | Additional content that becomes visible on hover or focus (for example tooltips) is extremely rare in this product. In all cases where content is initially hidden and displayed on interaction, we trigger that display with explicit, unambiguous input such as a click or keypress. Content is persistently visible until dismissed by a similarly unambiguous interaction. We never rely on hover alone.
Third party content (e.g. advertising, customer services widgets) may inject elements that fail to meet this criterion. When we become aware of deficiencies, we immediately take steps to request repairs from third party vendors. |
| 2.4.5 Multiple Ways (Level AA)
Also applies to: EN 301 549 Criteria
|
Supports | Users may use the search function or the provided links to access any part of this product. Breadcrumb menus are provided to return users to the index page. The main navigation component can also be used to access the main subject index pages. |
| 2.4.6 Headings and Labels (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Our document structure is semantically marked up using headings to create a sequential hierarchy of content. Rarely, headings or labels may be visually hidden but available to Assistive Technologies, though we prefer to keep this pattern to a minimum.
Nature magazine and a limited number of journals publish editorial content from a content management system (CMS). Content generated by CMS may occasionally lack appropriate headings (e.g. using bold text as implicit headings instead of semantically-marked up heading elements). Other third party scripts, including survey or customer services widgets, may inject content with inadequate or inappropriate headings or labels. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 2.4.7 Focus Visible (Level AA)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
Generally, we provide high-visibility yellow focus rings on all focusable elements. Some items (such as links) may use changes in text-decoration to indicate focus in addition to the focus ring.
Some pages (e.g. some payment pages) use default focus rings only. On some of these pages, the default focus ring has been removed from input elements and replaced with a different focus style that provides inadequate visibility. Some components on payment pages remove focus styles. We are actively working to repair these problems; the high-visibility focus ring across the majority of Nature.com is intended to be the default. 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
|
Does Not Support | Language of Parts is not applicable for the majority of this content. All first-party components on the pages of this product that are part of dynamic templates are written in English.
Editorial content or published papers may be written in or include text in languages other than English. Article content may be marked up with a separate lang attribute that matches the written language, though this is not consistently applied.
Third party scripts may inject components with non-English text - for example a targeted advertisement or file presented in a file viewer (e.g. Figshare) may use a different language to the main document. These may not be marked up with a separate lang attribute.
We currently have no method of confirming the inclusion of appropriate lang attributes for pieces of text in content that may use a different language to the main document.
|
| 3.2.3 Consistent Navigation (Level AA)
Also applies to: EN 301 549 Criteria
|
Supports |
Navigational mechanisms that are repeated on multiple Web pages within the Nature.com website occur in the same relative order each time they are repeated. Although some older archive content on the Nature.com website may be rendered in older design templates, the navigation of each of these sets of pages is internally consistent.
Pages that deal with sensitive information (including payment pages and "my account" 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
|
Supports |
Components that have the same functionality within a set of Web pages are identified consistently. Although some older archive content on the Nature.com website may be rendered in older design templates, the identification of components in each of these sets of pages is internally consistent.
Pages that deal with sensitive information (including payment pages and "my account" 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 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.
Third party scripts including the Disqus commenting widget, or other widgets that accept user input, may automatically detect errors but fail to present the errors to users in ways that they can perceive. They may rely on visual characteristics alone to indicate user input errors, or place error text in locations that are difficult for screen reader users to access. When we become aware of deficiencies, we contact third party suppliers to request repairs. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to: EN 301 549 Criteria
|
Supports | The payment pages checkout flow includes a pre-payment verification page. The user must confirm that their choices are correct on the verification page 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
|
Does not support | Status messages that do not receive focus are presented in text. These are generally not marked up with programmatic roles to indicate their purpose. |
Notes: This product has not been evaluated for WCAG 2.x Level AAA conformance.
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | The majority of content is marked up for Assistive Technology. 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. Fonts are set as rems and use pixels as a fallback if not supported. The product does not impede the user from zooming into the page. Third party scripts may inject content with inadequate accessibility support. |
| 302.3 Without Perception of Color | Supports | Color 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. 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 generally have a consistent presentation with clear labels, titles, and accessible names for controls. 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
| 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.
See WCAG sections 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value 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.
See WCAG sections 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value for further detail. |
| 502.3.3 Row, Column, and Headers | Partially Supports |
Data tables in original research or editorial content 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 | Supports |
The pages in this product use labels on components that require user input.
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. Third party scripts may inject content that obscures the relationships between components.
See WCAG section 1.3.1 Info and Relationships for further detail. |
| 502.3.8 Text | Partially Supports |
The pages of this product use standard plain text in HTML.
Original research or editorial content 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 third party scripts may inject content that cannot be interacted with easily or at all by keyboard or by some Assistive Technologies. See WCAG section 2.1.1 Keyboard for further detail. |
| 502.3.12 Focus Cursor | Partially Supports |
We provide focus styles on most 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.
Rarely, components may 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 color 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 | |
| 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:
| 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 | ||
| 11.5.2 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.