Accessibility Conformance Report (ACR)

Product: Preprints.org

Version 1 – June 2026

Introduction

Product Name: Preprints.org

Report Version: Version 1 – June 2026

VPAT Version: Voluntary Product Accessibility Template® (VPAT®) International Edition Version 2.5Rev

Product Description

MDPI operates Preprints.org: an open-access preprint posting platform providing manuscript submission, preprint hosting, article pages, search and browse functionality, and help resources for authors and readers.

Product Scope

This report covers the Preprints.org platform. This includes all publicly accessible web pages on https://www.preprints.org, including article pages, search and browse pages, article submission, help center, blog, and other content available through the platform. Please see https://www.mdpi.com/accessibility for the Accessibility Conformance Reports for other MDPI products.

Notes

As Preprints.org continues to evolve, accessibility improvements are incorporated into ongoing platform development to provide a more inclusive experience for all users.

Contact:

Evaluation Methods Used

  1. Use of browser developer tools and common accessibility heuristics (structure, semantics, keyboard support, color contrast, focus visibility, error handling, and ARIA usage).
  2. Consideration of expected interoperability with modern screen readers and other assistive technologies based on standard HTML and ARIA patterns.
  3. Audit of shared MDPI pages and workflows by Deque.

WCAG 2.2 A+AA

WCAG Overview

WCAG 2.2 overview
CriteriaConformance Level
1.1.1 Non-text Content (Level A) Partially Supports
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Supports
1.2.2 Captions (Prerecorded) (Level A) Supports
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Partially Supports
1.2.4 Captions (Live) (Level AA) Not Applicable
1.2.5 Audio Description (Prerecorded) (Level AA) Partially Supports
1.3.1 Info and Relationships (Level A) Partially Supports
1.3.2 Meaningful Sequence (Level A) Partially Supports
1.3.3 Sensory Characteristics (Level A) Supports
1.3.4 Orientation (Level AA 2.1 and 2.2) Supports
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) Partially Supports
1.4.1 Use of Color (Level A) Partially Supports
1.4.2 Audio Control (Level A) Not Applicable
1.4.3 Contrast (Minimum) (Level AA) Partially Supports
1.4.4 Resize text (Level AA) Supports
1.4.5 Images of Text (Level AA) Supports
1.4.10 Reflow (Level AA 2.1 and 2.2) Partially Supports
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) Partially Supports
1.4.12 Text Spacing (Level AA 2.1 and 2.2) Supports
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Partially Supports
2.1.1 Keyboard (Level A) Partially Supports
2.1.2 No Keyboard Trap (Level A) Supports
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Supports
2.2.1 Timing Adjustable (Level A) Partially Supports
2.2.2 Pause, Stop, Hide (Level A) Partially Supports
2.3.1 Three Flashes or Below Threshold (Level A) Not Applicable
2.4.1 Bypass Blocks (Level A) Does Not Support
2.4.2 Page Titled (Level A) Partially Supports
2.4.3 Focus Order (Level A) Supports
2.4.4 Link Purpose (In Context) (Level A) Partially Supports
2.4.5 Multiple Ways (Level AA) Supports
2.4.6 Headings and Labels (Level AA) Partially Supports
2.4.7 Focus Visible (Level AA) Partially Supports
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) Partially Supports
2.5.1 Pointer Gestures (Level A 2.1 and 2.2) Not Applicable
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) Supports
2.5.3 Label in Name (Level A 2.1 and 2.2) Supports
2.5.4 Motion Actuation (Level A 2.1 and 2.2) Not Applicable
2.5.7 Dragging Movements (Level AA 2.2 only) Supports
2.5.8 Target Size (Minimum) (Level AA 2.2 only) Supports
3.1.1 Language of Page (Level A) Partially Supports
3.1.2 Language of Parts (Level AA) Partially Supports
3.2.1 On Focus (Level A) Supports
3.2.2 On Input (Level A) Partially Supports
3.2.3 Consistent Navigation (Level AA) Supports
3.2.4 Consistent Identification (Level AA) Partially Supports
3.2.6 Consistent Help (Level A 2.2 only) Supports
3.3.1 Error Identification (Level A) Partially Supports
3.3.2 Labels or Instructions (Level A) Partially Supports
3.3.3 Error Suggestion (Level AA) Supports
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Supports
3.3.7 Redundant Entry (Level A 2.2 only) Supports
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) Supports
4.1.2 Name, Role, Value (Level A) Partially Supports
4.1.3 Status Messages (Level AA 2.1 and 2.2) Does Not Support

Supports / Not Applicable Partially Supports Does Not Support

WCAG 2.2 A+AA - Details

1.1.1 Non-text Content (Level A)

Partially Supports
Support examples
  • Alt texts are added for most core images such as preprints logos.
  • All article figures are accompanied by figure captions. Alt text is added if provided by authors.
  • All the images on the Product page have alt text.
  • All the images on the support page have alt text.
Does not support or partially supports examples
  • Some functional icons in navigation, error page, and carousels lack descriptive text alternatives.
  • Most article figures do not have alt text. Figure captions may be informative, but they don't serve the same purpose as alt texts.
  • We cannot guarantee the standard of software components from third parties.
Workarounds
  • The missing alternative text or other explanatory content will be added as soon as possible.
  • If you need any additional information on article figures, please contact the corresponding author.
  • If you encounter any issues with third-party software, please contact us at .

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Supports
Support examples
  • The information contained in the promotional videos is also available in text form on the About page and 10th Anniversary page.
Notes
  • There is no audio or video related to core Preprints workflows. There are two promotional videos on the Preprints' 10th Anniversary page.

1.2.2 Captions (Prerecorded) (Level A)

Supports
Support examples
  • The promotional videos contain captions.
Notes
  • There is no audio or video related to core Preprints workflows. There are two promotional videos on the Preprints' 10th Anniversary page.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Partially Supports
Does not support or partially supports examples
  • There are no audio descriptions or media alternatives publicly available for the promotional videos.
Notes
  • There is no audio or video related to core Preprints workflows. There are two promotional videos on the Preprints' 10th Anniversary page.
Workarounds

If you have any questions related to the promotional videos for Preprints' 10th anniversary or for a transcript of the videos, please contact .

1.2.4 Captions (Live) (Level AA)

Not Applicable
Notes
  • All the audio content that is played simultaneously comes with subtitles. There are no live videos available.

1.2.5 Audio Description (Prerecorded) (Level AA)

Partially Supports
Does not support or partially supports examples
  • There are no audio descriptions or media alternatives publicly available for the promotional videos.
Notes
  • There is no audio or video related to core Preprints workflows. There are two promotional videos on the Preprints' 10th Anniversary page.
Workarounds

If you have any questions related to the promotional videos for Preprints' 10th anniversary or for a transcript of the videos, please contact .

1.3.1 Info and Relationships (Level A)

Partially Supports
Support examples
  • Tables use correct HTML elements, such as the table heading and table row.
  • All header tags or list tags are correct on the Instructions for Authors page.
  • Semantic structure to convey information and relationships through presentation is programmatically determinable.
Does not support or partially supports examples
  • Headers are not always identified correctly.
  • The PDF versions of articles are not reliably accessible to all screen readers.
Workarounds
  • The identified issues will be remediated as soon as possible. Until then, please reach out to if any support is required.
  • For screen reader users, it is advisable to use the web version of articles. If individual, remediated PDF versions are required, please contact .

1.3.2 Meaningful Sequence (Level A)

Partially Supports
Support examples
  • Visual display sequences of page content are consistent with DOM arrangement sequences in the code. There is no disorder in the logical arrangement of the content. All text, images, form components, and module blocks that have sequential relationships can be recognized and read by assistive programs in the intended reading order. There will be no semantic understanding deviation due to sequence deviations.
  • The content sequence of non-article documents is logically consistent and can be parsed by assistive programs in a normal and orderly manner.
  • The arrangement of the support section fulfills accessibility criteria, and there is no deviation in the semantic interpretation.
Does not support or partially supports examples
  • The PDF versions of articles are not reliably accessible to all screen readers.
Workarounds

For screen reader users, it is advisable to use the web version of articles. If individual, remediated PDF versions are required, please contact .

1.3.3 Sensory Characteristics (Level A)

Supports
Support examples
  • Any website content with sensory components also has an appropriate descriptive text or text alternative.
  • Instructions and guidelines are all explained in clear text, and do not solely rely on sensory characteristics.
  • All operation prompts in the software interface are marked with textual labels. They do not merely convey operation requirements through sensory information such as color, position, or icons.
Workarounds

In case an article contains content that relies on sensory characteristics, please contact the corresponding author to obtain alternative descriptions.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports
Support examples
  • The website is responsive and usable on different viewports.
  • The website pages support switching between portrait and landscape orientations. The display direction is not forcibly locked, allowing for normal reading and operation.
  • Software elements support automatic adaptation to both portrait and landscape screen orientations.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • Preprints generally uses programmatic attributes (such as HTML autocomplete) to identify the purpose of input fields.
Does not support or partially supports examples
  • There are forms, such as the Input Author Details form, or the Any Suggestions form, in which autocomplete attributes for some elements are missing.
Workarounds

The identified issues will be remedied as soon as possible. Until then, please reach out to if any support is required.

1.4.1 Use of Color (Level A)

Partially Supports
Support examples
  • Most of the information transmission, status indications and operation instructions do not rely solely on colors for presentation. Instead, they are complemented by multiple forms of identification such as text and styles to enhance the meaning.
  • Forms that encounter an error on one of the inputs become red, but also display an error text.
Does not support or partially supports examples
  • Some links on Preprints only identify as links through use of color.
Workarounds

The identified issues will be remediated as soon as possible, and the old pages will be replaced with updated versions, in accordance with the WCAG specifications. Until then, please reach out to if any support is needed.

1.4.2 Audio Control (Level A)

Not Applicable
Notes
  • There is no automatically playing audio content on Preprints.

1.4.3 Contrast (Minimum) (Level AA)

Partially Supports
Support examples
  • The contrast between the text and background colors (including links and content text) on most pages is at least 4.5:1 against the background color.
Does not support or partially supports examples
  • The color of the author names in the "Recent Preprints" section does not meet the contrast ratio requirement of 4.5:1.
Workarounds

In the subsequent updates, we will update the colors that do not conform to the standards.

1.4.4 Resize text (Level AA)

Supports
Support examples
  • All text can be enlarged up to 200% without losing functionality.
  • All PDFs can be enlarged up to 200% without losing functionality.

1.4.5 Images of Text (Level AA)

Supports
Support examples
  • No images of text are used on Preprints.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • The website generally looks like the mobile version when the browser is zoomed in to 400% or more.
  • Article presentation is responsive and adapts to narrow screens. When scaled up by 400%, there is no double-sided scrolling. Content and functions are fully available.
Does not support or partially supports examples
  • If the screen is zoomed in to 400% or higher, the footer disclaimer and the step bar on the submission page cannot be fully read.
Workarounds

We will adjust the footer layout and text wrapping to ensure all disclaimer content remains readable at 400% zoom without horizontal scrolling or truncation. In case of support needed until then, please contact .

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • All UI elements such as buttons are clearly differentiated from the rest of the page.
  • The color contrast of the content within article PDFs meets the requirements.
  • Color contrast between elements and their adjacent colors is sufficient in most cases.
Does not support or partially supports examples
  • The CAPTCHA element used when subscribing or creating a new account may lack sufficient contrast.
Workarounds

If you encounter any issues with the CAPTCHA element, please contact .

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Supports
Support examples
  • The spacing between words, lines and letters is adjustable.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • For the majority of elements across Preprints, the hover and focus states work as desired.
  • The Feedback menu can be closed by pressing the Esc key on the keyboard, or by clicking on the blank area of the page. There is no need to move the mouse or switch the focus.
Does not support or partially supports examples
  • The footer disclaimer is not dismissible once it opens and it hides some content behind it. On the https://www.preprints.org/user/notification/settings page, the Tooltip cannot be closed and it may cover the content.
  • The additional content shown when hovering over "Disclaimer" in the website footer can be dismissed only by moving the mouse.
Workarounds

In upcoming updates, we will ensure hover and focus content can be dismissed, remains visible while hovered or focused, and does not obscure content. In case of support needed until then, please contact .

2.1.1 Keyboard (Level A)

Partially Supports
Support examples
  • The clickable elements on the home page and most of the other pages meet the requirements.
  • Overall, articles and their internal elements can be navigated and selected by keyboard.
Does not support or partially supports examples
  • On the submission page, expanding and zooming of the author information cannot be selected via the keyboard.
  • The subject selection box on the search page cannot be expanded to select secondary subjects.
  • The elements on the help page cannot be focused.
  • The "report" image on the "about" page cannot be selected via the keyboard.
  • The buttons in the feedback pop-up window do not support full keyboard operation.
Workarounds
  • We will fix these issues as soon as possible. Users who cannot operate the affected submission or search controls using a keyboard can contact Preprints.org at for assistance.
  • Users who cannot access the keyword links using a keyboard can use the main article text, site search, or subject browse pages to locate related content.
  • Users who cannot operate the feedback pop-up using a keyboard can contact Preprints.org through the Help Center contact options or by emailing .

2.1.2 No Keyboard Trap (Level A)

Supports
Support examples
  • There are no keyboard traps on Preprints.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Supports
Support examples
  • No single-character keyboard shortcuts are implemented in the Preprints web interface.

2.2.1 Timing Adjustable (Level A)

Partially Supports
Support examples
  • The login function has a time limit of one day. It is refreshed after the user's operation. There are no other time limits on Preprints.
Does not support or partially supports examples
  • The prompt window will automatically disappear and the user cannot adjust it.
Workarounds

If the prompt window disappears before the user can act, the user can refresh the page or repeat the relevant action to reopen the prompt. If additional assistance is needed, users may contact .

2.2.2 Pause, Stop, Hide (Level A)

Partially Supports
Does not support or partially supports examples
  • The images or videos in the advertisement carousel on manuscript pages cannot be paused manually.
Workarounds

The PDF versions of articles do not contain any moving elements.

2.3.1 Three Flashes or Below Threshold (Level A)

Not Applicable
Notes
  • There is no flashing content on Preprints or in Preprint articles.

2.4.1 Bypass Blocks (Level A)

Does Not Support
Does not support or partially supports examples
  • Most pages do not provide links to main content.
Workarounds

If no bypass link is provided, keyboard users can use the browser's find function, heading navigation, or tab through repeated navigation to reach the main content area. Users may also contact for assistance.

2.4.2 Page Titled (Level A)

Partially Supports
Support examples
  • Each web page has a corresponding title.
  • PDF articles are always named according to the journal, the volume number, and the chronological article number within the volume.
Does not support or partially supports examples
  • Product materials such as supporting PDFs do not have a title set.
Workarounds

Users can identify the content through the file name, the document heading on the page, the opening content of the file, or the description provided on the download page.

2.4.3 Focus Order (Level A)

Supports

2.4.5 Multiple Ways (Level AA)

Supports
Support examples
  • Content or webpages can be found through multiple ways such as the search bar and the menu.

2.4.6 Headings and Labels (Level AA)

Partially Supports
Support examples
  • The majority of headings and labels describe sections and controls clearly, supporting navigation and comprehension.
Does not support or partially supports examples
  • On the submission page, some of the filter boxes lack titles.
Workarounds

We will make the adjustment as soon as possible. If you have any questions, please contact info@preprints.

2.4.7 Focus Visible (Level AA)

Partially Supports
Support examples
  • The majority of UI elements have an appropriate "focus visible" styling.
Does not support or partially supports examples
  • Some elements become less distinct when focused on, such as the Download button on article pages.
Workarounds

We will make the adjustment as soon as possible. If you have any questions, please contact info@preprints.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

Partially Supports
Does not support or partially supports examples
  • Some buttons will be obscured when they are in focus, such as on the article detail page.
Workarounds

Users can adjust the zoom level or use alternative navigation paths to access the same function. For further assistance, please contact .

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Not Applicable
Notes
  • There are no functions requiring pointer gestures on Preprints.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Supports
Support examples
  • Links and buttons always activate on up events not on down events. Users can abort actions by moving their mouse away from the link or button.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Supports
Support examples
  • The text labels of user interface components correspond to the text that is presented visually.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Not Applicable
Notes
  • There are no functions on Preprints that require specific motion input.

2.5.7 Dragging Movements (Level AA 2.2 only)

Supports

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

Supports
Notes
  • All elements on Preprints support the success criterion for Target Size.

3.1.1 Language of Page (Level A)

Partially Supports
Support examples
  • All Preprints web pages are tagged as English language pages.
Does not support or partially supports examples
  • PDF versions of articles do not currently have language tags.
Workarounds

We are working toward improving the accessibility tagging of article PDFs in upcoming updates. Until then, individual accessibility-tagged PDF versions of articles can be requested from .

3.1.2 Language of Parts (Level AA)

Partially Supports
Support examples
  • All general Preprint pages are in English.
  • Individual names or technical terms which are part of articles or scientific discourse may be non-English, but are generally recognizable within the scope of the content.
Does not support or partially supports examples
  • Some acquired journals may have article content that includes mixed languages (for example, German and Japanese) on a single page.
Workarounds

Should any clarification be necessary, please reach out to the corresponding author(s) of the article, the journal team, or to .

3.2.1 On Focus (Level A)

Supports
Support examples
  • No components trigger changes in context when they receive focus.

3.2.2 On Input (Level A)

Partially Supports
Support examples
  • Changes in search conditions are properly announced by screen readers, such as the application of filter options.
Does not support or partially supports examples
  • Updates to search results based on user inputs (such as applying a filter) are not properly announced.
Workarounds

Filtering or changing a search option of a search interface will be announced and this will directly trigger a new search. You can then check the items that have been returned.

3.2.3 Consistent Navigation (Level AA)

Supports
Support examples
  • Navigation elements (global header, footer, essential journal navigation) appear in consistent locations and order across pages, supporting predictable use.
  • All Preprints articles follow the same layout and navigation templates.

3.2.4 Consistent Identification (Level AA)

Partially Supports
Support examples
  • Most repetitive controls, such as the submit button, have a consistent identification method.
Does not support or partially supports examples
  • The login buttons on the mobile version and the PC version are not the same.
Workarounds

The different login button design issue will be fixed as soon as possible.

3.2.6 Consistent Help (Level A 2.2 only)

Supports
Support examples
  • Feedback and other support-related entries are designed to maintain a consistent relative position and display order across all pages of the entire website.

3.3.1 Error Identification (Level A)

Partially Supports
Support examples
  • For the majority of pages, if any input error is detected, the erroneous item is visually marked and the error is described to the user in text.
Does not support or partially supports examples
  • Error messages relating to the human verification CAPTCHA may not be announced properly to screen reader users.
Workarounds

If any support is needed, please contact us through the contact form or by email at .

3.3.2 Labels or Instructions (Level A)

Partially Supports
Support examples
  • The majority of form controls contain visible labels.
Does not support or partially supports examples
  • Some selection components do not have a visible label near the component itself.
Workarounds

The labels will be fixed as soon as possible. If any support is needed until then, please contact us through the contact form or by email at .

3.3.3 Error Suggestion (Level AA)

Supports
Support examples
  • When input errors are detected on Preprints pages, suggestions for correction are provided. For example, forms provide inline messages suggesting how to correct an error, such as "Invalid email format". This level of guidance is consistently applied across all forms and flows.

3.3.7 Redundant Entry (Level A 2.2 only)

Supports
Support examples
  • After the user logs in, the system can automatically obtain the user's name, email address and other existing user information, and automatically fill them in the subsequent forms, or provide selection options for the user to directly use, without requiring the user to repeatedly input the same information in the same process.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

Supports
Support examples
  • A cognitive function test is not required to login to Preprints.

4.1.2 Name, Role, Value (Level A)

Partially Supports
Does not support or partially supports examples
  • Some checkboxes and input fields do not have names.
Workarounds

We will fix this issue as soon as possible. If you have any questions, please contact .

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Does Not Support
Does not support or partially supports examples
  • Pop-up messages on Preprints are not properly read by screen readers. These may include the disclaimer in the page footer, notifications related to subscriptions and submissions, and the "feedback - any suggestions" pop-up.
Workarounds

We will fix this issue as soon as possible. Until then, please contact for any questions or support.

Section 508

Section 508: Functional

Section 508: Functional detail
Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Partially Supports Most workflows can be completed without vision, but some aspects can be further improved, as described through the WCAG criteria.
302.2 With Limited Vision Partially Supports The website generally looks like the mobile version when the browser is zoomed in to 400% or more. If the screen is zoomed in to 400% or higher, the footer disclaimer and the step bar on the submission page cannot be fully read. We will adjust the footer layout and text wrapping to ensure all disclaimer content remains readable at 400% zoom without horizontal scrolling or truncation. In case of support needed until then, please contact .
302.3 Without Perception of Color Partially Supports The contrast between the text and background colors (including links and content text) on most pages is at least 4.5:1 against the background color. The color of the author names in the "Recent Preprints" section does not meet the contrast ratio requirement of 4.5:1. In the subsequent updates, we will update the colors that do not conform to the standards.
302.4 Without Hearing Supports All audio content (including videos) on Preprints comes with complete subtitles or text alternatives.
302.5 With Limited Hearing Supports
302.6 Without Speech Supports Speech is not required for Preprints.
302.7 With Limited Manipulation Supports The Preprints website supports single-key operation on the keyboard. Click areas fulfill the size criterion, and there are alternative solutions for all fine interactions.
302.8 With Limited Reach and Strength Supports All functions are accessible via the keyboard, without requiring users to exert force, press continuously, or operate from a distance. There are no interaction scenarios that necessitate high physical strength or specific postures to complete.
302.9 With Limited Language, Cognitive, and Learning Abilities Partially Supports Most common workflows provide visible labels, text guidance, and predictable interaction patterns. Some interface patterns may increase cognitive load, including unclear result updates after filtering, insufficiently labeled selection controls, and overlay content that may affect ease of understanding. Users may rely on on-screen instructions and error messages, and may contact if further assistance is needed.

Section 508: Software interoperability with assistive Technology

Section 508: Software interoperability with assistive Technology detail
Criteria Conformance Level Remarks and Explanations
502.2.1 User Control of Accessibility Features Supports Preprints does not restrict accessibility features or assistive technology. Preprints supports platform accessibility features such as system font scaling, system high contrast, and screen readers.
502.2.2 No Disruption of Accessibility Features Supports The no-code interface system's accessibility feature and dynamic page logic do not disrupt accessibility features.
502.3.1 Object Information Supports Information such as control roles, states, names, and descriptions can all be programmatically recognized by screen readers.
502.3.2 Modification of Object Information Supports Both the native controls of the site and third-party components can have their properties modified by assistive technologies.
502.3.3 Row, Column, and Headers Not Applicable
502.3.4 Values Supports The input field and checkbox for Cloudflare verification code are accessible via screen readers.
502.3.5 Modification of Values Supports Cloudflare verification codes allow users to manually modify the values, and the auxiliary technology can also programmatically adjust the values.
502.3.6 Label Relationships Supports Cloudflare's association with input boxes follows a specific standard, and the binding relationship can be recognized by screen readers.
502.3.7 Hierarchical Relationships Supports Cloudflare control's DOM hierarchy specification: Parent-child relationships can be accessed by screen readers.
502.3.8 Text Partially Supports Cloudflare presents text based on native DOM rendering. The content, attributes, and boundaries can all be accessed by screen readers. Usersnap, User centrics, Cookies only perform basic data collection, without custom special rendering text controls. If you have any questions, please contact info@preprints.
502.3.9 Modification of Text Partially Supports Cloudflare verification code input box can be modified by both manual methods and auxiliary tools. Usersnap, User Centrics, Cookies are for statistical tagging, and there are no editable text boxes. If you have any questions, please contact info@preprints.
502.3.10 List of Actions Supports All actions that can be executed on an object are programmatically determinable.
502.3.11 Actions on Objects Supports All the controls can be correctly identified.
502.3.12 Focus Cursor Supports The focus can be tracked and read by assistive technologies.
502.3.13 Modification of Focus Cursor Supports The native controls of the website support modifications of focus, input cursor and text selection through assistive technologies, without requiring code interception for assistive operations.
502.3.14 Event Notification Supports The third-party software scripts do not have code interception or obstacle events.
502.4 Platform Accessibility Features Supports Cloudflare, Usersnap, User Centrics, and Cookies are all front-end scripts for web pages. There is no need to implement system-level accessibility configuration.
503.2 User Preferences Not Applicable
503.3 Alternative User Interfaces Not Applicable
503.4.1 Caption Controls Not Applicable
503.4.2 Audio Description Controls Supports

Section 508: Support Documentation

Section 508: Support Documentation detail
Criteria Conformance Level Remarks and Explanations
602.2 Accessibility and Compatibility Features Supports This Accessibility Conformance Report lists accessibility features and potential issues and workarounds.
602.3 Electronic Support Documentation Partially Supports The elements on the help page do not fully support keyboard operations (for instance, the Terms of Use PDF). We will fix this issue as soon as possible. If you have any questions in the meantime, please contact info@preprints.
602.4 Alternate Formats for Non-Electronic Support Documentation Not Applicable All support functions are electronic.

Section 508: Support Services

Section 508: Support Services detail
Criteria Conformance Level Remarks and Explanations
603.2 Information on Accessibility and Compatibility Features Supports If you have any additional questions, please contact info@preprints.
603.3 Accommodation of Communication Needs Supports

EN 301 549

EN 301 549: Clause 4 - Functional Performance Statements

EN 301 549: Clause 4 - Functional Performance Statements detail
Criteria Conformance Level Remarks and Explanations
4.2.1 Usage without vision Partially Supports Most workflows can be completed without vision, but some aspects can be further improved, as described through the WCAG criteria.
4.2.2 Usage with limited vision Partially Supports Some buttons do not have clear focus. The pop-up prompts automatically disappear, and users are unable to pause. We will fix this issue as soon as possible. If you have any questions, please contact .
4.2.3 Usage without perception of colour Partially Supports When focusing on a link, only the color changes. We will fix this issue as soon as possible. If you have any questions, please contact .
4.2.4 Usage without hearing Supports Preprints does not require hearing. Core workflows do not contain any audio content. Text alternatives as well as subtitles are available for promotional audio and video content. Videos are accompanied by subtitles.
4.2.5 Usage with limited hearing Supports
4.2.6 Usage with no or limited vocal capability Supports Speech is not required for any function of Preprints.
4.2.7 Usage with limited manipulation or strength Partially Supports Currently, a minority of elements and buttons cannot be operated using the keyboard, for example tab switching on the Help Center page. We will fix this issue as soon as possible. If you have any questions, please contact info@preprints.
4.2.8 Usage with limited reach Supports
4.2.9 Minimize photosensitive seizure triggers Supports Preprints does not contain any rapidly flashing or high-intensity visual content that increases risks of triggering photosensitive seizures.
4.2.10 Usage with limited cognition, language or learning Supports The information on the website is clear, the operation is simple, and the prompts are accurate.
4.2.11 Privacy Supports MDPI's Privacy Policy provides further information on the data protection standards used for Preprints: https://www.mdpi.com/about/privacy.

EN 301 549: Clause 5 - Generic Requirements

EN 301 549: Clause 5 - Generic Requirements detail
Criteria Conformance Level Remarks and Explanations
5.1 Closed functionality Not Applicable Preprints.org does not use any closed functionality and does not restrict the use of assistive technology.
5.2 Activation of accessibility features Not Applicable
5.3 Biometrics Not Applicable Biometric information is not required by Preprints.
5.4 Preservation of accessibility information during conversion Not Applicable
5.5 Operable parts Not Applicable Preprints is purely a web service and does not contain any manually operable parts.
5.6 Locking or toggle controls Not Applicable
5.7 Key repeat Not Applicable
5.8 Double-strike key acceptance Not Applicable
5.9 Simultaneous user actions Not Applicable No Preprints workflow requires simultaneous user actions.

EN 301 549: Clause 10 - Non-Web Documents

EN 301 549: Clause 10 - Non-Web Documents detail
Criteria Conformance Level Remarks and Explanations
10.5 Caption positioning Supports Video subtitles are all set in a safe area, where they don't obscure key content of the video.
10.6 Audio description timing Supports The voiceovers in the videos have been optimized in terms of timing.

EN 301 549: Clause 12 - Documentation and Support Services

EN 301 549: Clause 12 - Documentation and Support Services detail
Criteria Conformance Level Remarks and Explanations
12.1.1 Accessibility and compatibility features Supports This Accessibility Conformance Report provides information on accessibility features of Preprints.
12.2.2 Information on accessibility and compatibility features Not Applicable
12.2.3 Effective communication Supports