Accessibility Conformance Report (ACR)

Product: SuSy

Version 1 – May 2026

Introduction

Product Name: SuSy

Report Version: Version 1 – May 2026

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

Product Description

SuSy is MDPI’s Submission System. It is a web‑based platform that supports manuscript submission, peer review, editorial decision‑making, and publication workflows. It is used by authors, reviewers, editors, and editorial staff to manage manuscripts, communications, and review processes across MDPI journals.

Product Scope

The SuSy ACR covers the public-facing web pages and functionalities available through the SuSy platform, as well as supporting documentation on other platforms like https://www.mdpi.com, related to manuscript submission workflows. SuSy does not contain non-web documents or standalone software components.

Public journal websites, as well as Topics, Special Issues, Articles, Author Services, Books, and other MDPI products, are covered in their respective, separate ACRs.

Notes

For technical support regarding SuSy, unrelated to accessibility, please contact . For support regarding accessibility issues, please contact .

Contact:

Evaluation Methods Used

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

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) Not Applicable
1.2.2 Captions (Prerecorded) (Level A) Not Applicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Not Applicable
1.2.4 Captions (Live) (Level AA) Not Applicable
1.2.5 Audio Description (Prerecorded) (Level AA) Not Applicable
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) Does Not Support
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) Does Not Support
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) Does Not Support
1.4.12 Text Spacing (Level AA 2.1 and 2.2) Partially Supports
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Does Not Support
2.1.1 Keyboard (Level A) Does Not Support
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) Not Applicable
2.2.2 Pause, Stop, Hide (Level A) Not Applicable
2.3.1 Three Flashes or Below Threshold (Level A) Not Applicable
2.4.1 Bypass Blocks (Level A) Supports
2.4.2 Page Titled (Level A) Partially Supports
2.4.3 Focus Order (Level A) Partially 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) 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) Partially 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) Not Applicable
2.5.8 Target Size (Minimum) (Level AA 2.2 only) Supports
3.1.1 Language of Page (Level A) Supports
3.1.2 Language of Parts (Level AA) Supports
3.2.1 On Focus (Level A) Supports
3.2.2 On Input (Level A) Supports
3.2.3 Consistent Navigation (Level AA) Supports
3.2.4 Consistent Identification (Level AA) Supports
3.2.6 Consistent Help (Level A 2.2 only) Supports
3.3.1 Error Identification (Level A) 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.1 Parsing (Level A) Supports
4.1.2 Name, Role, Value (Level A) Does Not Support
4.1.3 Status Messages (Level AA 2.1 and 2.2) Partially Supports

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
  • System icons and logos generally include alternative text.
  • SuSy supports receiving article documents with alt text.
  • Third-party integrations (e.g., Cloudflare security checks) support non-text content alternatives.
Does not support or partially supports examples
  • Some legacy thumbnails lack descriptive alt text.
  • SuSy cannot enforce alt text on user-uploaded PDF or Word documents.
Workarounds
  • Missing alt texts on legacy components are being systematically addressed as part of the ongoing frontend migration.
  • We are currently developing internal tools and processes to add alternative texts to all non-text content. Please contact to request text alternatives.

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

Not Applicable
Notes
  • SuSy does not contain any audio or video content.

1.2.2 Captions (Prerecorded) (Level A)

Not Applicable
Notes
  • SuSy does not contain any prerecorded audio-only or video-only media.
  • SuSy is capable of hosting captioned video files, but does not automatically generate or force the use of captions in user-uploaded prerecorded materials.

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

Not Applicable
Notes
  • SuSy does not contain any prerecorded media.

1.2.4 Captions (Live) (Level AA)

Not Applicable
Notes
  • SuSy does not contain any live content.

1.2.5 Audio Description (Prerecorded) (Level AA)

Not Applicable
Notes
  • SuSy does not contain any prerecorded media.

1.3.1 Info and Relationships (Level A)

Partially Supports
Does not support or partially supports examples
  • The web application generally uses semantic HTML to convey information and relationships programmatically, though some exceptions exist in legacy components. For instance, headers are not always identified correctly.
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 required.

1.3.2 Meaningful Sequence (Level A)

Partially Supports
Support examples
  • SuSy's document object model order matches the visual order, ensuring a logical reading sequence for assistive technologies.
Does not support or partially supports examples
  • For some interactive elements on SuSy, unusable hidden content is readable with a screen reader.
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 required.

1.3.3 Sensory Characteristics (Level A)

Supports
Support examples
  • Instructions provided for understanding and operating content on SuSy do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports
Support examples
  • SuSy utilizes responsive web design and does not restrict its view or operation to a single display orientation (portrait or landscape).

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • SuSy generally uses programmatic attributes (such as HTML autocomplete) to identify the purpose of input fields that collect user information.
Does not support or partially supports examples
  • There are forms, such as the Input Author Details form, in which autocomplete attributes for some elements are missing.
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 required.

1.4.1 Use of Color (Level A)

Does Not Support
Does not support or partially supports examples
  • Some form elements on SuSy only use color to indicate which element is currently active.
  • Some links on SuSy are only identifiable 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 required.

1.4.2 Audio Control (Level A)

Not Applicable
Notes
  • SuSy does not contain any audio that plays automatically.

1.4.3 Contrast (Minimum) (Level AA)

Partially Supports
Support examples
  • CSS variables are used to maintain consistent contrast ratios on most SuSy pages.
Does not support or partially supports examples
  • There are individual elements which fail to meet the 4.5:1 color contrast ratio for text.
Workarounds

Theme colors are being audited and adjusted to ensure that all text and UI elements meet the 4.5:1 ratio as part of our Vue.js design system update. Until then, please contact in case any support is required.

1.4.4 Resize text (Level AA)

Does Not Support
Support examples
  • Standard PDF/Word viewers provided by browsers support zooming.
  • Third-party interfaces and editor tools respond correctly to browser zoom.
Does not support or partially supports examples
  • Loss of functionality and information is possible at high zoom levels. Content enlargement may cause horizontal scrolling, overlapping elements, or truncated labels.
Workarounds

Users who require larger text on desktop can combine browser zoom or text‑size settings with the use of built‑in magnification features on their operating system (for example, Windows Magnifier, macOS Zoom, or platform screen magnifiers), which allow localised enlargement of content without relying on the page layout alone. Users who still encounter difficulties with reading or layout at high zoom levels can contact for assistance and alternative access options.

1.4.5 Images of Text (Level AA)

Supports
Support examples
  • Text is used to convey information rather than images of text throughout SuSy.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • Content can be presented without loss of function and largely without loss of information at a width of 320 CSS pixels.
Does not support or partially supports examples
  • At high zoom the data protection button can overlap with the page footer.
Workarounds

The data protection button is provided by third-party consent management platform User Centrics and we are currently not able to solve the issue. If it prevents you from using any SuSy functionality, please reach out to so we can provide a solution.

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

Does Not Support
Does not support or partially supports examples
  • Some interactive form elements, as well as some icons within interactive forms do not have a sufficient contrast ratio.
Workarounds

Contrast for disabled UI states will be enhanced in the upcoming CSS framework updates. Until then, please contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • The application does not override browser settings that adjust text spacing. In general, there is no loss of information or function.
Does not support or partially supports examples
  • In SuSy's page header under the Information tab, there are two links in which textual cut-off may occur when increasing spacing.
Workarounds

Hovering over these two lines shows the URL these links refer to, and which provides the missing information. There are multiple ways to reach these pages, both of which are not located on SuSy but on mdpi.com. In case you cannot find the information you are looking for due to accessibility reasons or any other reasons, please either use the support form or reach out to .

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

Does Not Support
Does not support or partially supports examples
  • There is additional hover content which either cannot be dismissed without moving pointer hover of keyboard focus, or which does not allow the user to move the pointer over that same additional content without the additional content disappearing.
Notes
  • There are no core workflows on SuSy that require hover content. Although hover content may be used to provide further context information.
Workarounds

Currently used custom tooltips are being replaced with native or fully accessible Vue components in upcoming updates. Until then, please contact for individual support.

2.1.1 Keyboard (Level A)

Does Not Support
Does not support or partially supports examples
  • Some elements across multiple SuSy workflows, including header navigation, do not yet fully support keyboard navigation.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

2.1.2 No Keyboard Trap (Level A)

Supports
Support examples
  • The audit did not identify any instances of keyboard traps across SuSy.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Supports
Support examples
  • The audit did not show any issues relating to character key shortcuts on SuSy.

2.2.1 Timing Adjustable (Level A)

Not Applicable
Notes
  • There is no timed content on SuSy.

2.2.2 Pause, Stop, Hide (Level A)

Not Applicable
Notes
  • There is no moving, blinking, scrolling, or autoplaying content on SuSy.

2.3.1 Three Flashes or Below Threshold (Level A)

Not Applicable
Notes
  • There is no flashing content on SuSy.

2.4.1 Bypass Blocks (Level A)

Supports
Support examples
  • SuSy supports "Skip Navigation, Headings or Landmarks".

2.4.2 Page Titled (Level A)

Partially Supports
Support examples
  • Most pages on SuSy have descriptive and informative title elements.
Does not support or partially supports examples
  • Some sub-pages such as the Edit Profile page may not have a sufficiently descriptive title element.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

2.4.3 Focus Order (Level A)

Partially Supports
Support examples
  • The sequential order of focusable components is correct.
Does not support or partially supports examples
  • Some drop-down selections may cause a hidden element to receive focus.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

2.4.5 Multiple Ways (Level AA)

Supports
Support examples
  • All SuSy pages offer at least two ways to find other pages. These ways can include links between pages, navigation menus, website searches, sitemaps, directory lists or lists of related pages.

2.4.6 Headings and Labels (Level AA)

Partially Supports
Support examples
  • The majority of headings and labels are descriptive and clearly convey the intended purpose.
Does not support or partially supports examples
  • In some cases, controls with slightly different actions have the same name. Such as form fields related to either suggesting a reviewer, or excluding a reviewer.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

2.4.7 Focus Visible (Level AA)

Partially Supports
Support examples
  • For the majority of elements on SuSy, focus is clearly visible.
Does not support or partially supports examples
  • Clickable buttons on SuSy do not make it sufficiently visible when they are focused.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

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

Supports
Support examples
  • When user interface components receive keyboard focus, the components are highlighted and not hidden by other content.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Not Applicable
Notes
  • SuSy does not require any multipoint or path-based gestures for operation.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Supports
Support examples
  • The down-event of the pointer is never used to execute any functions on SuSy.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Partially Supports
Support examples
  • The majority of user interface components have an accessible name and contain a visible label.
Does not support or partially supports examples
  • Some individual user interface components do not contain a visible label with an accessible name.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Not Applicable
Notes
  • SuSy does not require any motion actuation.

2.5.7 Dragging Movements (Level AA 2.2 only)

Not Applicable
Notes
  • SuSy does not require any dragging movements.

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

Supports
Support examples
  • The majority of pages support this criteria.
Does not support or partially supports examples
  • All pointer inputs meet the required target size.

3.1.1 Language of Page (Level A)

Supports
Support examples
  • All SuSy pages declare the page language.

3.1.2 Language of Parts (Level AA)

Supports
Support examples
  • All SuSy pages are entirely in English and can be programmatically determined as English.
  • All supporting documentation and services are in English and can be programmatically determined as English.

3.2.1 On Focus (Level A)

Supports
Support examples
  • When any component receives focus, it does not initiate a change of context.

3.2.2 On Input (Level A)

Supports
Support examples
  • Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

3.2.3 Consistent Navigation (Level AA)

Supports
Support examples
  • The main navigation bar appears at the top with identical order on all pages.

3.2.4 Consistent Identification (Level AA)

Supports
Support examples
  • Repeated controls (search fields, login buttons, icons) are identified consistently across the platform, promoting recognition.
  • Components that have the same functionality within a set of web pages are identified consistently.

3.2.6 Consistent Help (Level A 2.2 only)

Supports
Support examples
  • The Feedback & Help function is consistently located in the mid-left of the user's screen with a consistent label and behavior.

3.3.1 Error Identification (Level A)

Supports
Support examples
  • If an input error is detected, the erroneous item is visually marked and the error is described to the user in text.

3.3.2 Labels or Instructions (Level A)

Partially Supports
Support examples
  • The majority of form fields have consistent and appropriate labels and instructions.
Does not support or partially supports examples
  • The three different "Name" form fields (First Name/Given Name; Middle Name; Last Name/Surname) are only differentiated by placeholder texts which disappear when the form field receives focus.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

3.3.3 Error Suggestion (Level AA)

Supports
Support examples
  • If an input error is detected, suggestions are provided to the user.

3.3.7 Redundant Entry (Level A 2.2 only)

Supports
Support examples
  • In most cases, relevant workflows (e.g., forms and certain submission steps) can reuse previously entered information so users do not need to re‑enter the same data. Whether auto-completion is applied in these forms depends on the user's browser settings.

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

Supports
Support examples
  • Login and authentication processes do not require cognitive function tests. Multiple authentication methods are provided.

4.1.1 Parsing (Level A)

Supports
Support examples
  • We have not identified any parsing issues on SuSy.

4.1.2 Name, Role, Value (Level A)

Does Not Support
Does not support or partially supports examples
  • There are numerous instances of custom controls (for example, submission navigation, comboboxes, form elements) missing accessible names or states, or exposing incorrect ARIA attributes.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • The majority of status messages for user interface components can be programmatically determined.
Does not support or partially supports examples
  • Status messages (for dynamic updates, errors, and successes) are not always properly announced by screen reader technology. For example, when a text search within a dropdown selection on SuSy returns no results.
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 contact for any technical support needed regarding SuSy, or for issues specifically related to accessibility.

Section 508

Section 508: Functional

Section 508: Functional detail
Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Does Not Support There are multiple WCAG criteria related to vision which are only partially supported by SuSy. Therefore, users without vision may run into accessibility issues when using SuSy. Please contact either the journal's editorial office, or , or so we can support your requirements.
302.2 With Limited Vision Does Not Support There are multiple WCAG criteria related to vision which are only partially supported by SuSy. Therefore, users with limited vision may run into accessibility issues when using SuSy. Please contact either the journal's editorial office, or , or so we can support your requirements.
302.3 Without Perception of Color Partially Supports There are multiple WCAG criteria related to perception of color or color contrast which are only partially supported by SuSy. Therefore, users without perception of color may run into accessibility issues when using SuSy. Please contact either the journal's editorial office, or , or so we can support your requirements.
302.4 Without Hearing Supports Hearing is not required to use SuSy.
302.5 With Limited Hearing Supports Hearing is not required to use SuSy.
302.6 Without Speech Supports Speech is not required to use SuSy.
302.7 With Limited Manipulation Supports Physical manipulation is not required to use SuSy.
302.8 With Limited Reach and Strength Supports Physical manipulation is not required to use SuSy.
302.9 With Limited Language, Cognitive, and Learning Abilities Supports Please reach out to if any further support can be provided to make SuSy easier to use.

Section 508: Support Documentation

Section 508: Support Documentation detail
Criteria Conformance Level Remarks and Explanations
602.2 Accessibility and Compatibility Features Supports Throughout SuSy, a link to MDPI's Accessibility page is available in the SuSy page footer.
602.3 Electronic Support Documentation Supports
602.4 Alternate Formats for Non-Electronic Support Documentation Not Applicable All support documentation for SuSy is available in electronic formats.

Section 508: Support Services

Section 508: Support Services detail
Criteria Conformance Level Remarks and Explanations
603.2 Information on Accessibility and Compatibility Features Supports Throughout SuSy, a link to MDPI's Accessibility page is available in the SuSy page footer.
603.3 Accommodation of Communication Needs Supports In case the Feedback widget or Support form can not guarantee appropriate support, the SuSy team can be contacted through for individual support.

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 Does Not Support Missing alt text, incorrect table semantics, keyboard-only failures, and incomplete names, roles, and values on many custom controls can create significant barriers for usage without vision. Please contact either the journal's editorial office, or , or so we can support your requirements.
4.2.2 Usage with limited vision Does Not Support Contrast failures and small target sizes of elements across multiple templates and workflows, plus missing focus indicators, reduce usability for low-vision users. Please contact either the journal's editorial office, or , or so we can support your requirements.
4.2.3 Usage without perception of colour Partially Supports Color is never the only indicator for information on SuSy. Due to non-text contrast issues and sometimes subtle visual styling, some states and controls may be hard to distinguish for users who do not perceive color well and rely on contrast. Please contact either the journal's editorial office, or , or so we can support your requirements.
4.2.4 Usage without hearing Supports
4.2.5 Usage with limited hearing Supports
4.2.6 Usage with no or limited vocal capability Supports
4.2.7 Usage with limited manipulation or strength Supports
4.2.8 Usage with limited reach Supports
4.2.9 Minimize photosensitive seizure triggers Supports
4.2.10 Usage with limited cognition, language or learning Supports
4.2.11 Privacy Supports

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 SuSy does not have any closed functionality software components.
5.2 Activation of accessibility features Supports Where accessibility features are provided, they can be activated without relying on methods that do not support that need.
5.3 Biometrics Not Applicable SuSy does not require any biometric input.
5.4 Preservation of accessibility information during conversion Partially Supports The majority of pages support this criteria. Attachments of manuscripts are currently not tagged for accessibility. 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.
5.5.1 Means of operation Not Applicable SuSy does not require any physical operation.
5.5.2 Operable parts discernibility Not Applicable
5.6 Locking or toggle controls Not Applicable
5.7 Key repeat Not Applicable SuSy does not include a physical keyboard.
5.8 Double-strike key acceptance Not Applicable
5.9 Simultaneous user actions Not Applicable

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 Throughout SuSy, a link to MDPI's Accessibility page is available in the SuSy page footer.
12.2.2 Information on accessibility and compatibility features Supports Throughout SuSy, a link to MDPI's Accessibility page is available in the SuSy page footer.
12.2.3 Effective communication Supports ICT support is available on SuSy through the Feedback widget or a contact form. In case of additional accessibility-related support needs, please contact .