Skip to main content

Wiley Current Protocols

Summary

This report reflects the findings of a high-level assessment of the Wiley Current Protocols platform for its conformance with the W3C Web Content Accessibility Guidelines version 2.1 (WCAG 2.1).

Overall, there are very few issues with the Wiley Current Protocols platform. There are, however, some essential WCAG 2.1 A and AA level requirements that need to be met for compliance around information and relationships and color contrast. Additionally, there are a few other issues that may improve the general usability of the site that are not direct violations of any specific SC. Below are the most critical issues to address to improve system compliance.

Top Findings

  1. Site Navigation: There are several instances where links do not have discernible text, meaning that these links are not being picked up by screen readers. This makes it extremely difficult for users that require the use of assistive technologies to navigate the site. Additionally, the Advanced Search page does not have a title, this can make it very difficult for users to keep track of which page they’re currently on.
  2. PDF Content: The PDF that was evaluated as a part of this report does not appear to have been set up correctly for accessibility. This can make interacting with PDF content very difficult for users with a variety of disabilities, and should be remediated in conformance with the Section 508 guidelines for PDF accessibility.
  3. Information, Relationships, and Compatibility: While the issues surrounding SC 1.3.1 and SC 4.1.2 are common issues, they can lead to significant obstacles for screen readers and site navigability. These typically are due to improper ARIA implementation. Please refer to the WAI-ARIA Authoring Best Practices guide for suitable implementation techniques.
  4. Focus Ring: Currently, the focus state of components is inconsistent across the site. While most of them do show a focus state, in several cases the focus ring does not meet the minimum color contrast ratio of 3:1 with the background and the edge of the component. This is technically not an AA violation; however, it causes difficulty for keyboard users and vision impaired users to navigate the site. It is strongly recommended to improve the focus state for components.