| Criteria | @@ -95,7 +99,7 @@ Tables 1 and 2 also document conformance with:
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. +Images such as icons on user interface elements may be identified with visible text labels, visually-hidden text, or WAI-ARIA techniques. Some icons are known to have inadequate or missing text alternatives (e.g. the chevron icon in dropdowns). We are actively working to repair this problem. 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). @@ -209,17 +213,15 @@ We currently have no method of confirming the inclusion of adequate media altern |
Partially Supports |
-This product 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.
+This product's pages generally use progressive enhancement techniques and semantically-correct markup so that information, structure, and relationships can be understood independently of presentation.
-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. +A-Z index pages for journals and books may use unsemantic markup, including inadequate, misleading, or incorrectly-applied landmarks, and may omit level one headings. 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. -Checkout process pages 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. +Checkout process 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 for 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. |
@@ -299,8 +301,6 @@ When supplied by authors who publish with us, some complex images may rely on se
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. |
Partially Supports | +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. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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. +On Springer Nature Video pages, the autoplay button is not accessible by keyboard only. We are working on fixing this issue. We are working on repairing this issue. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Partially Supports | +Supports |
Keyboard trapping inside components on this product's 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. +Modal dialogs 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 with third party vendors where required. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) + | 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
Partially Supports |
Moving, blinking or scrolling content on this product's 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.
-Checkout process pages have landmarks present. Some are duplicated without unique labels. +Pages on Springer Nature Video do not include a skip link to bypass repetitive navigation elements. We are actively working to repair this problem. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Partially Supports |
-This product's pages mostly have unique page titles that describe the purpose of the page.
+Most pages in this product 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. |
@@ -549,11 +545,7 @@ Where multiple versions of the same content exist (e.g. in original research tha
The meaning and/or operation of content on this product is generally unaffected by focus order.
-This product 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. +A-Z index pages for journals and books may contain components where some items in the focus order do not match 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. |
@@ -587,7 +579,7 @@ Third party scripts including advertising scripts, the Disqus commenting widget,
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2.5.1 Pointer Gestures (Level A 2.1 only) + | 2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
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) + | 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
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) + | 2.5.3 Label in Name (Level A 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
|
-Partially Supports | +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. +Where controls contain visible text, that text is also the label for the control. When we become aware of deficiencies, we work to repair instances that do not meet this criterion. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2.5.4 Motion Actuation (Level A 2.1 only) + | 2.5.4 Motion Actuation (Level A 2.1 and 2.2)
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. | +Partially Supports | +Generally, changing the setting of any user interface component does not automatically cause a change of context on any of the pages of this product.
+ +Some user interface components (e.g. quantity box on checkout process pages, filter radio buttons on collections pages) cause the page to reload based on changing their setting. + |
+||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3.2.6 Consistent Help (Level A 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
++ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3.3.1 Error Identification (Level A)
@@ -753,8 +756,6 @@ Where user input errors are automatically detected by our own software, those er
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. - Checkout process pages 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. |
Partially Supports |
-This product 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. |
+|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3.3.7 Redundant Entry (Level A 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
+Supports | +This product does not require users to enter information more than once in the process without the information being available for the user to select. Checkout pages include a checkbox to populate inputs with the same values as previously entered (e.g. where the billing address and shipping address is the same). | +|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 4.1.1 Parsing (Level A)
- Also applies to: + Applies to: +WCAG 2.0 and 2.1 - Supports +WCAG 2.2 (obsolete and removed) - Does not apply 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. - -This product 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. + | WCAG 2.0 and 2.1 - Supports
-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. - -Checkout process pages 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. +WCAG 2.2 (obsolete and removed) - Does not apply + |
+||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. +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. |
@@ -857,7 +852,7 @@ Other third party scripts, including the Freshdesk customer services widget, may
### Table 2: Success Criteria, Level AA
-|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Criteria | @@ -912,7 +907,7 @@ Other third party scripts, including the Freshdesk customer services widget, may||||||
|---|---|---|---|---|---|---|
| 1.3.4 Orientation (Level AA 2.1 only) + | 1.3.4 Orientation (Level AA 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
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) + | 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
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. | +Some form fields (e.g. 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) @@ -968,19 +963,15 @@ Other third party scripts, including the Freshdesk customer services widget, may | Partially Supports |
-This product 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. +Checkout process pages have some instances of low text contrast (e.g. where optional fields are indicated in text). Third party advertising scripts may inject content with insufficient contrast. |
||||
| 1.4.4 Resize text (Level AA) + | 1.4.4 Resize Text (Level AA)
Also applies to: EN 301 549 Criteria
|
-Partially Supports | +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. +The pages of this product can be resized without Assistive Technology up to 200 percent without loss of content or functionality. |
||
| 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.
-
+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. +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) + | 1.4.10 Reflow (Level AA 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
|
-Partially Supports | +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) + | 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
|
Partially Supports |
-This product 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. +On this product's homepage, the focus ring in the "About Springer Nature Link" section has inadequate contrast against the blue background. + 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) + | 1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
|
-Partially Supports | +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 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. +No loss of content or functionality occurs by setting the text spacing properties specified by this criterion anywhere in this product. |
||
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) + | 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Also applies to: EN 301 549 Criteria
|
-Does Not Support | +Partially Supports |
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). 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. @@ -1154,9 +1137,9 @@ Third party content (e.g. advertising, customer services widgets) may inject ele |
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.
+On most pages of this product, 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.
-This product 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. +A-Z index pages for journals and books have a search function to access any part of this product but do not provide other ways to navigate this product, and do not meet this criterion. |
| Partially Supports |
-This product 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. +Most pages in this product use correctly-structured headings and generally display visible and appropriately associated labels for input fields. -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. +Multiple level one headings are used on some pages (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. |
|||||
| Partially Supports |
-This product 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. +Most pages in this product highly-visible focus styles, such as blue focus rings. -Checkout process pages use default browser focus rings only for interactive components. +Checkout process pages omit a visible focus style on product image links. Third party scripts, including advertising, may inject components that remove focus styles. |
|||||
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
+Supports | +There are no instances of obscured focus as specified by this criterion anywhere in this product. + | +||||
| 2.5.7 Dragging Movements (Level AA 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
+Supports | +There is no functionality in this product that requires dragging movements. All interactive elements are operable using single pointer actions. | +||||
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
+Partially Supports | +With rare exceptions, this product has targets that either meet the minimum size or have sufficient spacing around them, as specified by this criterion.
+ +Superscript link targets that are undersized, or have insufficient spacing around them, are considered inline elements and are excempt from this criterion. + +The footer on Springer Nature Video pages includes undersized targets that do not have sufficient spacing around them. We are actively working to repair this issue. |
+||||
| 3.1.2 Language of Parts (Level AA)
Also applies to: @@ -1272,15 +1274,11 @@ Third party scripts may inject components that use a different language to the p |
Partially Supports |
-This product 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. +Most pages in this product have consistent navigation methods across collections of pages. -Pages rendered in the newer design are currently articles, chapters, books, book series, reference works, reference work entries, and collections. +A-Z index pages for journals and books have different navigation methods than the majority of the site. We are working on making the navigation methods on these pages consistent with the wider site. -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. +Pages that deal with sensitive information (e.g. 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. |
||||
| Partially Supports |
-This product 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. +Most pages in this product have consistent presentation and functionality. -When the transfer process is complete, content will use a unified design style with consistent presentation and functionality. +A-Z index pages for journals and books have a different presentation and functionality than most of the site, and do not meet this criterion. -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. +Pages that deal with sensitive information (e.g. 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. |
|||||
|
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.
-This product 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. - Checkout process pages 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. |
Supports | Checkout process pages include 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. | +||||
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
+ EN 301 549 Criteria - Does not apply +Revised Section 508 - Does not apply + |
+Supports | +Account management pages in this product do not rely on memory or transcription alone for authentication. Alternative login methods such as copy-paste, password managers, and browser autofill are supported in this product. | +||||
| 4.1.3 Status Messages (Level AA 2.1 only) + | 4.1.3 Status Messages (Level AA 2.1 and 2.2)
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. | +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. There are instances of ARIA Live Regions on account management pages, but they are not generally used elsewhere. |
| 501.1 Scope – Incorporation of WCAG 2.1 AA | -See WCAG 2.1 section | +See WCAG 2.2 section | See information in WCAG section | ||||
| 502.3 Accessibility Services | +502.3 Accessibility Services | ||||||
|---|---|---|---|---|---|---|---|
| 502.3.1 Object Information | @@ -1503,7 +1501,7 @@ Third party scripts may inject content that disrupts standard operating system a
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. +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.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 journals, books, series, protocols, reference works or proceedings are marked up with marked up with standard HTML `table` elements, with rare exceptions.
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. |
@@ -1626,7 +1624,7 @@ See WCAG sections 1.3.1 Info and Relationships
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 User Controls for Captions and Audio Description | ||||||
| 503.4.1 Caption Controls | @@ -1754,7 +1752,7 @@ Notes: This product does not offer two-way voice communication and is therefore ### Clause [7: ICT with Video Capabilities](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf#page=35) -Notes: See [WCAG section](#wcag-21-report) for full details. +Notes: See [WCAG section](#wcag-22-report) for full details.|||||||
| 11.1.1 through 11.4.1.3 | See WCAG 2.x Section | -See information in WCAG section | +See information in [WCAG section](#wcag-22-report). |
| 11.5 Interoperability with assistive technology | |||
|---|---|---|---|