Protocols.io Accessibility Conformance Report
protocols.io empowers researchers with disabilities to create, collaborate, and contribute structured scientific knowledge.
Based on the Voluntary Product Accessibility Template (VPAT®) 2.4 Rev WCAG
Name of Product: protocols.io
Product Description: protocols.io is a secure web platform which has the only way to interact with the stored content - via web interface through a modern browser. Protocols.io planform allows creating, editing, running, organizing, sharing and working on methods, and collaboration with the workspace members.
Date: December 3rd, 2025
Scope: The scope of this report is limited to the following user scenarios: Search protocols, Review a protocol, Create a new account, Sign in, Join a workspace, Review settings, Read notifications, Read and edit a protocol within a workspace File Manager, Run a protocol, Sign out.
Contact information: info@protocols.io
Evaluation Methods Used: Scenarios were tested using: Keyboard-only interactions, Google Chrome, Axe, Color Contrast Analyzer, Platform features such as high contrast and zoom.
Applicable Standards/Guidelines
This report covers the degree of conformance to the level A and AA criteria of the Web Content Accessibility Guidelines version 2.1 (WCAG 2.1 AA).
Terms
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.
WCAG 2.1
Level A Success Criteria
| Criteria | Conformance Level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | |
| 1.2.2 Captions (Prerecorded) | Supports | |
| 1.2.3 Audio Description or Media Alternative | Supports | |
| 1.3.1 Info and Relationships | Supports | |
| 1.3.2 Meaningful Sequence | Supports | |
| 1.3.3 Sensory Characteristics | Supports | |
| 1.4.1 Use of Color | Supports | |
| 1.4.2 Audio Control | Supports | |
| 2.1.1 Keyboard | Supports | |
| 2.1.2 No Keyboard Trap | Supports | |
| 2.1.4 Character Key Shortcuts | Supports | |
| 2.2.1 Timing Adjustable | Supports | |
| 2.2.2 Pause Stop Hide | Supports | |
| 2.3.1 Three Flashes or Below Threshold | Supports | |
| 2.4.1 Bypass Blocks | Supports | |
| 2.4.2 Page Titled | Supports | |
| 2.4.3 Focus Order | Supports | |
| 2.4.4 Link Purpose (In Context) | Supports | |
| 2.5.1 Pointer Gestures | Supports | |
| 2.5.2 Pointer Cancellation | Supports | |
| 2.5.3 Label in Name | Supports | |
| 2.5.4 Motion Actuation | Supports | |
| 3.1.1 Language of Page | Supports | |
| 3.2.1 On Focus | Supports | |
| 3.2.2 On Input | Supports | |
| 3.3.1 Error Identification | Supports | |
| 3.3.2 Labels or Instructions | Supports | |
| 4.1.1 Parsing | Supports | |
| 4.1.2 Name Role Value | Supports |
Level AA Success Criteria
| Criteria | Conformance Level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Supports | |
| 1.2.5 Audio Description (Prerecorded) | Supports | |
| 1.3.4 Orientation | Supports | |
| 1.3.5 Identify Input Purpose | Supports | |
| 1.4.3 Contrast (Minimum) | Supports | |
| 1.4.4 Resize text | Partially Supports | Text can be resized up to 200% without loss of content or functionality for the majority of pages. Some legacy and data-dense layouts may introduce horizontal scrolling or minor clipping at high zoom levels; these areas are being gradually refactored to fully support responsive layouts. |
| 1.4.5 Images of Text | Supports | |
| 1.4.10 Reflow | Partially Supports | Most content reflows without requiring two-dimensional scrolling at 400% zoom. A small number of complex, multi-pane layouts and data-heavy views (for example, some File Manager screens) may still require horizontal scrolling. These are scheduled for responsive redesign. |
| 1.4.11 Non-text Contrast | Supports | |
| 1.4.12 Text-spacing | Partially Supports | The majority of text adapts correctly when users override line height, paragraph spacing, letter spacing, and word spacing. Certain dense UI regions and legacy layouts can cause truncation or overlapping when spacing is significantly increased. These areas are being updated to better support custom text spacing. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Most tooltips, menus, and popups behave predictably and can be perceived and dismissed when triggered by hover or keyboard focus. In some components, controls expose additional information only on mouse hover and do not yet follow the dismissible / hoverable / persistent pattern for keyboard users. We are updating these components to rely on accessible patterns and ensure that the same information and functionality are available when controls receive keyboard focus. |
| 2.4.5 Multiple Ways | Supports | |
| 2.4.6 Headings and Labels | Partially Supports | Headings and labels within the core protocols.io application are designed to be descriptive and consistent. Some embedded third-party experiences expose headings and labels that we cannot fully control and which may not always be descriptive. We work with these vendors and monitor updates to improve the experience over time. |
| 2.4.7 Focus Visible | Partially Supports | A visible focus indicator is provided for most interactive controls, and many key workflows also offer documented keyboard shortcuts as an additional navigation mechanism. A small number of custom or legacy controls still have a low-visibility focus style, particularly on complex backgrounds. These controls are being updated to use a high-contrast, consistent focus outline. |
| 3.1.2 Language of Parts | Supports | |
| 3.2.3 Consistent Navigation | Supports | |
| 3.2.4 Consistent Identification | Supports | |
| 3.3.3 Error Suggestion | Supports | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | |
| 4.1.3 Status Messages | Partially Supports | Within the core application, important status updates (such as form errors, success messages, and long-running operations) are exposed via programmatic status messages (for example, ARIA live regions). Some embedded third-party components use custom status patterns that are not fully exposed to assistive technologies. We continue to work with vendors to improve support for accessible status messaging. |
Third-Party Component Accessibility Note
The protocols.io platform integrates third-party services, such as payment and billing providers, to support specific workflows (for example, subscription management and checkout). While the core protocols.io application has been evaluated against WCAG 2.1 Level A and AA criteria, certain aspects of these embedded experiences are outside of our direct control.
In particular, these third-party components may impact:
- 2.4.6 Headings and Labels: Some headings and form labels within embedded widgets may not be fully descriptive or consistent.
- 4.1.3 Status Messages: Status updates (such as loading, errors, or confirmation messages) may not always be exposed via programmatically determinable status messages for assistive technologies.
- 3.3.4 Error Prevention (Legal, Financial, Data): Error-prevention patterns for legal and financial transactions (for example, review screens, undo options) are implemented by the third-party provider and may differ from the patterns used in the core protocols.io interface.
We monitor accessibility behavior in these third-party components, report issues to vendors, and evaluate alternative integrations where feasible. If users encounter accessibility barriers in these areas, we encourage them to contact us at info@protocols.io.