This report reflects the findings of a high-level assessment of the Cambridge Core Platform for its conformance with the W3C Web Content Accessibility Guidelines version 2.1 (WCAG 2.1). There are very few WCAG 2.1 compliance issues with the platform, and the few that are present are programmatic in nature and should be relatively easy to fix. However, creating an accessible platform is a constantly moving goalpost, so it is important to keep in mind that there are continual updates to the WCAG standards that may require more work in the future. Below are the most critical issues to focus on correcting to improve access for all potential users of the system.
Top 3 Issues:
- Information and Relationships: There seems to be an issue with screen reader support that causes elements to be read out of order. It may be a bug with the browser and screen reader combination that we used during testing, however it is something that needs to be addressed in order to support users that need screen readers.
- Compatibility: There are very few issues with this system overall and the only compliance issue that stands out is around the use of unique id’s. This is a relatively minor issue and is primarily programmatic and should not cause a serious problem with usability or accessibility. For an in-depth guide to ARIA implementation, please see the WAI-ARIA Authoring Best Practices Guide from W3.
- Color Contrast: At a cursory glance, the colors used on the site do not seem to fall outside of acceptable contrast ratios, with the potential exception of the lightest gray used for subheadings/text. The errors should be reviewed manually for accuracy, but it might just be a problem with the automatic analysis.