protocols.io Accessibility Conformance Report
protocols.io empowers researchers with disabilities to create, collaborate, and contribute structured scientific knowledge.
WCAG Edition, based on VPAT® Version 2.5. Report date:
Conformance status
protocols.io partially conforms with WCAG 2.2 Level AA. Partially conforms means that some parts of the content do not fully conform to the accessibility standard. The issues found are listed in the WCAG 2.x report below.
| Supports | Partially Supports | Does Not Support | Not Applicable | |
|---|---|---|---|---|
| Level A | 18 | 8 | 0 | 6 |
| Level AA | 14 | 7 | 0 | 3 |
Report information
- Name of Product/Version
- protocols.io web application (https://www.protocols.io/), as live 14 August – 4 September 2026.
- Report Date
- October 2026
- Product Description
- protocols.io is a web platform for developing, sharing and publishing research methods and protocols.
- Contact Information
- [email protected]
- Notes
- This report is based on an independent audit by Funka against WCAG 2.2 Level A and AA. Third-party solutions were not audited. Criteria where errors were found are reported as Partially Supports; criteria with no errors found are reported as Supports.
- Evaluation Methods Used
- Expert manual evaluation against WCAG 2.2 Level A and AA, including keyboard-only testing, screen reader testing, zoom, reflow and text-spacing tests, colour-contrast measurement and HTML validation. Equipment: Windows 11 with NVDA, and iPhone 13 with VoiceOver. Browsers: Google Chrome, Edge, Firefox and Safari for MacOS and iOS (latest versions).
Applicable standards/guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 |
|
| Web Content Accessibility Guidelines 2.1 |
|
| Web Content Accessibility Guidelines 2.2 |
|
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. This can only be used in WCAG Level AAA criteria.
WCAG 2.x report
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.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes: Conformance levels are based on Funka’s WCAG 2.2 audit. Level A and AA results also apply to WCAG 2.0 and 2.1 for the criteria included in those versions.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | No accessibility issues were found in the audited content. Meaningful images and graphical elements have text alternatives and button functions are clear. No image maps are used. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | No prerecorded audio-only or video-only content was identified in the audited content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Supports | No accessibility issues were found in the audited content. Prerecorded video includes captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | No accessibility issues were found in the audited content. Visual information in video is available through audio. |
| 1.3.1 Info and Relationships (Level A) | Partially Supports | Multiple main landmarks are used on every page, one of them wrapping the whole page, and some navigation landmarks have non-descriptive names (e.g. two navigations both named "menu"). Text that visually functions as headings is not coded as headings in protocols, the publishing flow and many modal dialogs. Some form labels are not programmatically associated with their fields, e.g. "Date range" in the Events feed, "Filter" on the community timeline, and fields in the publishing and new-workspace flows. Custom radio buttons are built with span elements instead of the native input. Headings, lists, paragraphs, tables, form grouping and error-message association otherwise meet the criterion. |
| 1.3.2 Meaningful Sequence (Level A) | Partially Supports | The general reading order is logical, but dynamically added content such as the search-suggestion list in the publishing flow is inserted at the end of the DOM rather than after the triggering element, so assistive technology users encounter it out of context. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | No accessibility issues were found in the audited content. |
| 1.4.1 Use of Color (Level A) | Supports | No accessibility issues were found in the audited content. |
| 1.4.2 Audio Control (Level A) | Not Applicable | No automatically playing audio was identified. |
| 2.1.1 Keyboard (Level A) | Partially Supports | Several controls cannot be operated with the keyboard: options in dropdown lists (div role="button" nested inside button elements), the submit button in the troubleshooting text area, and radio buttons in the publishing, run-a-new-record and create-workspace flows, where users interact with span elements rather than the native radio input. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | No keyboard traps were identified in the audited content. Keyboard operability issues are reported under 2.1.1. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Not Applicable | No single character key shortcuts are used. |
| 2.2.1 Timing Adjustable (Level A) | Not Applicable | No time limits were identified. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | No accessibility issues were found in the audited content. No disturbing moving, blinking or auto-updating content. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | No accessibility issues were found in the audited content. No flashing content. |
| 2.4.1 Bypass Blocks (Level A) | Supports | No accessibility issues were found in the audited content. A skip link to the main content is provided. |
| 2.4.2 Page Titled (Level A) | Supports | Pages have unique and relevant titles. Recommended improvements: add the website name to page titles and make titles of the settings pages (Edit profile, Email notifications, etc.) more descriptive. |
| 2.4.3 Focus Order (Level A) | Partially Supports | Dynamically opened areas (menus, search suggestions, etc.) are placed at the end of the DOM. Focus is moved into them, but when the user tabs out or closes them, focus returns to the top of the page instead of the triggering control. When new fields are added (e.g. "Add" funder in the publishing flow, new workspace), they appear above the Add button and focus is not moved to them. Modal dialogs keep focus correctly. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link purpose is generally clear. Improvement recommended: carousel links on the home page combine image alt text, heading and text into one long link text; decorative alt text could be emptied or only the heading linked. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Not Applicable | No multipoint or path-based gestures are used. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | No accessibility issues were found in the audited content. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Partially Supports | Some controls have an accessible name that does not contain the visible label, e.g. a link with visible text "Fred Hutch Cancer Center" has aria-label="user profile". |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Not Applicable | No motion-actuated functionality is used. |
| 3.1.1 Language of Page (Level A) | Supports | No accessibility issues were found in the audited content. The page language is programmatically set. |
| 3.2.1 On Focus (Level A) | Supports | No unexpected changes of context on focus were identified. Keyboard operability issues are reported under 2.1.1. |
| 3.2.2 On Input (Level A) | Supports | No unexpected changes of context on input were identified. Keyboard operability issues are reported under 2.1.1. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | No accessibility issues were found in the audited content. Help functions are consistently placed. |
| 3.3.1 Error Identification (Level A) | Partially Supports | When creating an account with required fields left empty, the error message is only shown as a tooltip when the "Create free account" button has hover or keyboard focus; otherwise no error is presented. Errors are otherwise described in text. |
| 3.3.2 Labels or Instructions (Level A) | Partially Supports | Some input fields rely only on placeholder text (and an icon) without a visible label, and the search function has no visible submit button. The "Date range" label in the Events feed serves two fields, and some labels are not programmatically associated with their fields. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | No accessibility issues were found in the audited content. |
| 4.1.1 Parsing (Level A) | WCAG 2.0 and 2.1 – Always answer ‘Supports’ WCAG 2.2 (obsolete and removed) - Does not apply Supports | For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. Note for WCAG 2.2: the criterion is obsolete. HTML validation found errors that do not affect conformance; correcting them is recommended. |
| 4.1.2 Name, Role, Value (Level A) | Partially Supports | Many custom controls are built with WAI-ARIA instead of native HTML elements; custom radio buttons are not operable. Some controls that expand and collapse content, in the main sidebar and the cookie dialog, do not expose their expanded/collapsed state. Some accessible names are inaccurate or non-descriptive, e.g. the "Filter" dropdown named "Open menu". |
Table 2: Success Criteria, Level AA
Notes: Conformance levels are based on Funka’s WCAG 2.2 audit. Level A and AA results also apply to WCAG 2.0 and 2.1 for the criteria included in those versions.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | No live audio content was identified. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | No accessibility issues were found in the audited content. Visual information in video is available through audio. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | No accessibility issues were found in the audited content. Content is not restricted to one orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | No accessibility issues were found in the audited content. Input fields use the autocomplete attribute correctly. |
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | Text contrast is generally very good in both light and dark themes, but some text falls below 4.5:1: the "Skip to main content" link against the dark sidebar (2.3:1), a link in the publishing flow, and the placeholder text "Untitled section" (1.8:1), which conveys information as the field has no visible label. |
| 1.4.4 Resize text (Level AA) | Supports | No accessibility issues were found in the audited content. Content is legible and usable at 200% zoom. |
| 1.4.5 Images of Text (Level AA) | Supports | No accessibility issues were found in the audited content. Text is presented as text, not images of text. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Partially Supports | At a width equivalent to 320 CSS pixels, content is cut off in the main sidebar, the Events feed, and the protocol editor (the placeholder "Untitled section" is truncated). No two-dimensional scrolling was otherwise required. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Partially Supports | Some user interface components have insufficient contrast against adjacent colors: the user menu icon (1.3:1), an information icon (2.5:1), rating stars (1.1:1) and switch buttons in the off state in the cookie dialog (1.8:1). Informative graphics otherwise meet the criterion. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | No accessibility issues were found in the audited content. Content works with custom text spacing. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Partially Supports | Custom tooltips shown on hover disappear when the pointer is moved over them, e.g. on the "Create an account" page. |
| 2.4.5 Multiple Ways (Level AA) | Supports | No accessibility issues were found in the audited content. A search function is available. |
| 2.4.6 Headings and Labels (Level AA) | Partially Supports | Headings are descriptive, but some labels do not describe the purpose of their controls, e.g. the "Filter" dropdown named "Open menu", and the field under "3. Invite colleagues" in the new-workspace flow, which only has the hidden label "Email". |
| 2.4.7 Focus Visible (Level AA) | Supports | No accessibility issues were found in the audited content. Keyboard focus is clearly visible. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Partially Supports | In the publishing flow, keyboard focus can move to controls in the hidden previous and next steps, and to elements behind the search-suggestion list. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | No accessibility issues were found in the audited content. Functions can be used without dragging. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Some targets are smaller than 24 by 24 CSS pixels but have enough spacing to meet the criterion. Larger targets are recommended. |
| 3.1.2 Language of Parts (Level AA) | Not Applicable | No content in a language other than the page language was identified. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | No accessibility issues were found in the audited content. Navigation is consistent across pages. |
| 3.2.4 Consistent Identification (Level AA) | Supports | No accessibility issues were found in the audited content. Components are identified consistently. |
| 3.3.3 Error Suggestion (Level AA) | Partially Supports | Some error messages state that a value is invalid without explaining how to correct it, e.g. "Email address must be properly formatted" when creating an account, and fields under "Edit profile". The account-creation error message is also displayed below the submit button, away from the field. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Not Applicable | No legal or financial transactions were identified in the audited content. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | No accessibility issues were found in the audited content. No cognitive function test is required to log in. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | No accessibility issues were found in the audited content. Status messages are conveyed to assistive technologies. |
Table 3: Success Criteria, Level AAA
Notes: Level AAA criteria were not included in the audit scope and are reported as Not Evaluated.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.2.8 Media Alternative (Prerecorded) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.2.9 Audio-only (Live) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.3.6 Identify Purpose (Level AAA 2.1 and 2.2) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.4.6 Contrast (Enhanced) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.4.7 Low or No Background Audio (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.4.8 Visual Presentation (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 1.4.9 Images of Text (No Exception) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.1.3 Keyboard (No Exception) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.2.3 No Timing (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.2.4 Interruptions (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.2.5 Re-authenticating (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.2.6 Timeouts (Level AAA 2.1 and 2.2) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.3.2 Three Flashes (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.4.8 Location (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.4.9 Link Purpose (Link Only) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.4.10 Section Headings (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.4.13 Focus Appearance (Level AAA 2.2 only) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.5.5 Target Size (Level AAA 2.1 and 2.2) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.1.3 Unusual Words (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.1.4 Abbreviations (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.1.5 Reading Level (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.1.6 Pronunciation (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.2.5 Change on Request (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.3.5 Help (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.3.6 Error Prevention (All) (Level AAA) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
| 3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) | Not Evaluated | Not included in the audit scope (WCAG 2.2 Level AA). |
Third-party components
The protocols.io platform integrates third-party services, such as payment and billing providers, to support specific workflows (for example, subscription management and checkout). These third-party solutions were not included in the audit, and some aspects of these embedded experiences are outside of our direct control.
We monitor accessibility behavior in these third-party components, report issues to vendors, and evaluate alternative integrations where feasible.
Feedback and assistance
We welcome your feedback on the accessibility of protocols.io. If you encounter an accessibility barrier, need information in an alternative format, or need help completing a task, contact us at [email protected].
To help us respond, please include:
- the web address (URL) of the page where you had the problem;
- what you were trying to do and what happened;
- the browser and any assistive technology you were using (for example, NVDA with Firefox).
We are working to resolve the issues identified in this report and will update it as fixes are released and after future evaluations.
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).