Accessibility Conformance Report (ACR)

Product: MDPI Journals (current platform)

Version 1 – April 2026

Introduction

Product Name: MDPI Journals (current platform)

Report Version: Version 1 – April 2026

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

Product Description

MDPI operates an open-access scholarly publishing platform providing journal homepages, article pages, search and browse functionality, and help resources for authors, reviewers, and readers.

Product Scope

MDPI Journals refers to all publicly accessible web pages for journals on https://www.MDPI.com, as well as Topics, Special Issues, and Articles associated with these journals. MDPI's Submission System (SuSy), Author Services, Books, and other products are covered in their respective, separate ACRs.

Notes

This report covers the MDPI Journals product on the old MDPI web platform, which will be phased out soon in favor of a new platform. Please note that we our focusing our efforts on making this new platform fully accessible.

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) Supports
1.2.2 Captions (Prerecorded) (Level A) Supports
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) 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) Does Not Support
1.4.5 Images of Text (Level AA) Does Not Support
1.4.10 Reflow (Level AA 2.1 and 2.2) Does Not Support
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) Partially Supports
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Partially Supports
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) Does Not Support
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) Does Not Support
2.4.4 Link Purpose (In Context) (Level A) Does Not Support
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) Does Not Support
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) Does Not Support
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) Does Not Support
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) 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) Partially Supports
3.3.1 Error Identification (Level A) Supports
3.3.2 Labels or Instructions (Level A) Does Not Support
3.3.3 Error Suggestion (Level AA) Partially Supports
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Supports
3.3.7 Redundant Entry (Level A 2.2 only) Partially Supports
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) Supports
4.1.1 Parsing (Level A) Partially Supports
4.1.2 Name, Role, Value (Level A) Does Not Support
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 journal and publisher logos.
  • All article figures are accompanied by figure captions. Alt text is added if provided by authors.
Does not support or partially supports examples
  • Some decorative and functional icons in navigation, filter controls, 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.
  • The CAPTCHA in the support form does not have alt text.
Notes
  • Images in articles have alt text if provided by the authors.
Workarounds
  • Missing alt texts or other text alternatives will be added in the upcoming new MDPI.com platform version.
  • We are currently developing internal tools and processes to add alternative texts to all images to future MDPI articles. For older articles, please reach out to corresponding authors or contact to request individual, remediated PDF versions of articles with alt text.
  • There is an audio CAPTCHA alternative to the image CAPTCHA. If you cannot use the support form, please reach out to for support.

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

Supports
Support examples
  • Content of videos is also described in text form.
  • Videos are media alternatives for accessible text.

1.2.2 Captions (Prerecorded) (Level A)

Supports
Support examples
  • Where videos are used, captions are available and consistent across all instances.

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

Supports
Support examples
  • For videos containing visual information, audio descriptions or equivalent media alternatives are provided.

1.2.4 Captions (Live) (Level AA)

Not Applicable
Notes
  • There is no live audio content on MDPI.com.

1.2.5 Audio Description (Prerecorded) (Level AA)

Partially Supports
Does not support or partially supports examples
  • Text or audio description of videos does not cover select text elements such as logos or written quotes within the videos.
Workarounds

For full transcriptions including text elements, please contact either the journal team, or support through our contact form or send an email to .

1.3.1 Info and Relationships (Level A)

Partially Supports
Support examples
  • Articles, journals and pages use headings, lists, and tables in HTML, to present document structure.
  • Info and Relationships (such as headers and lists) are tagged correctly in the bodies of web versions of articles.
Does not support or partially supports examples
  • Some complex UI elements (filter panels, tabbed content, related‑article carousels) rely mainly on visual layout, with relationships not fully represented via landmarks or ARIA roles.
  • Some tables and lists on supporting pages (e.g., Journal-specific overviews, instructions for authors) are not tagged correctly and don't reliably convey structural information.
  • The PDF versions of articles are not reliably accessible to all screen readers.
  • The list of authors is not tagged as a list in the web versions of articles.
  • On supporting pages, there are instances of incorrect or missing header tags or list tags.
Workarounds
  • The upcoming, new mdpi.com platform is better suited for most accessibility needs, including for screen readers. Visit https://www.mdpi.com/redirect/new_site.
  • 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
  • The reading order for primary content follows the visual layout on basic key templates.
Does not support or partially supports examples
  • There are instances of hidden content readable with screen readers, reducing the consistency of content read with screen readers.
  • The PDF versions of articles are not reliably accessible to all screen readers.
Workarounds
  • The upcoming, new mdpi.com platform is better suited for most accessibility needs, including for screen readers. Visit https://www.mdpi.com/redirect/new_site.
  • 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
  • There are no instances in which instructions or operations rely on sensory characteristics. Instructions for search, filters, and forms do not depend solely on color, shape, or position. Additionally, text labels or field names describe actions (e.g., "Select journal", "Choose subject area"), supporting users who cannot rely on sensory cues.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports
Support examples
  • MDPI.com content and articles are not restricted to a single display orientation.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • The majority of input fields on MDPI.com have correct and useful identification and autocomplete attributes.
Does not support or partially supports examples
  • Identifiable input purpose is missing for 'email' in the newsletter subscription and email alert features.
  • Identifiable input purpose is missing for 'name' and 'email' in the support form.
Workarounds
  • Please contact the journal team for the respective journal newsletter you would like to subscribe to.
  • Please contact for further support.

1.4.1 Use of Color (Level A)

Partially Supports
Support examples
  • In most cases, color is used to emphasize categories and states. However, link states, selections, and errors also include textual indicators, ensuring important information is not conveyed by color alone.
Does not support or partially supports examples
  • When article image previews are toggled in article search or journal overview pages, the color contrast indicating state change is insufficient. The color contrast indicating the currently selected page in the Journal Menu list is insufficient.
Workarounds

Instances of insufficient color contrast will be remediated on the new MDPI.com platform.

1.4.2 Audio Control (Level A)

Not Applicable
Notes
  • There is no automatic audio content on MDPI.com.

1.4.3 Contrast (Minimum) (Level AA)

Partially Supports
Support examples
  • Standard text and primary buttons generally meet the 4.5:1 contrast requirement.
Does not support or partially supports examples
  • Secondary links, muted UI text, low‑contrast icons, and some focus outlines may fall below the minimum contrast in certain themes or areas.
Workarounds

The upcoming, new mdpi.com platform is better suited for most accessibility needs. This includes consistent sufficient color contrast ratio. Visit https://www.mdpi.com/redirect/new_site.

1.4.4 Resize text (Level AA)

Does Not Support
Does not support or partially supports examples
  • When users zoom or increase text size up to 200%, content enlargement causes horizontal scrolling, overlapping elements, or truncated labels.
Workarounds

The mobile version of MDPI.com is better optimized for small screens and can also be used for high zoom levels on larger screens.

1.4.5 Images of Text (Level AA)

Does Not Support
Does not support or partially supports examples
  • Links to journal metrics can be images containing text, which are not tagged properly.
  • Advertisements may be images containing text, which are not tagged properly.
Workarounds
  • Information on journal metrics is also included on journal pages in text form.
  • Instances of missing alt text or link tags will be remediated on the new MDPI.com platform.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Does Not Support
Does not support or partially supports examples
  • When content is viewed on small devices, key layouts (including article search results, journal overview pages, and some article detail sections) require horizontal scrolling in both directions and/or cause content and controls to be partially hidden or overlap, meaning the page does not reflow within a single column.
Workarounds

The upcoming new MDPI.com platform is better suited for most accessibility needs, including small screens. Visit https://www.mdpi.com/redirect/new_site.

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

Partially Supports
Support examples
  • The majority of visual presentations have contrast ratios of at least 3:1 against adjacent colors.
Does not support or partially supports examples
  • Some form fields such as journal selection in the footer newsletter subscription function or active user interface components such as the year slider on the advanced search page lack sufficient contrast.
  • Color contrast is insufficient in individual articles' access statistics charts.
  • Input fields in the contact form lack sufficient contrast.
  • The CAPTCHA element on the payment page may lack sufficient contrast.
Workarounds
  • Most instances of insufficient color contrast will be remediated on the new MDPI.com platform.
  • For further information on access statistics for individual articles, please contact the journal team.
  • If support is required to use the contact form, please contact .

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • Most body text and standard content areas remain readable and usable.
Does not support or partially supports examples
  • Some tight UI components such as navigation bars, filter chips, and certain button/label combinations, can exhibit clipping, overlapping, or truncated text.
Workarounds

The upcoming, new mdpi.com platform is better suited for most accessibility needs, including text spacing adjustment. Visit https://www.mdpi.com/redirect/new_site.

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

Partially Supports
Does not support or partially supports examples
  • Some hover‑only content is not reliably available via keyboard focus, and in certain cases users cannot easily dismiss the additional content without moving pointer focus away.
  • In video content the thumbnail preview in the seek bar disappears automatically after a short time.
  • The additional content shown when hovering over disclaimer in the website footer can be dismissed only by moving the mouse.
Notes
  • There is no core feature or workflow on MDPI.com for which content on hover or focus is required. But such content may be used to provide useful additional information or insight.
Workarounds
  • Instances of indismissable hover content will be remediated on the new MDPI.com platform.
  • Text alternatives exist for all video content on MDPI.com.

2.1.1 Keyboard (Level A)

Does Not Support
Support examples
  • The majority of core functionality is operable via keyboard alone.
Does not support or partially supports examples
  • Some navigation elements or custom components may not yet be fully operable via keyboard alone. This includes some dropdown selection elements, link copying functions, articles' Open Access disclaimers and the general website disclaimer, navigating between figures in articles previews, closing the 'help' window on journal information pages, or using keyboard to focus on tables or figures in web versions of articles.
Workarounds

2.1.2 No Keyboard Trap (Level A)

Supports
Support examples
  • The audited web pages do not contain keyboard traps.
Workarounds

In case you encounter a keyboard trap, please reach out to and our website team will fix it as soon as possible.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Supports
Support examples
  • Keyboard shortcuts for user interface components are only active when that component has focus.

2.2.1 Timing Adjustable (Level A)

Not Applicable
Notes
  • There are no time limits for journal-related content on MDPI.com.

2.2.2 Pause, Stop, Hide (Level A)

Does Not Support
Support examples
  • There is no automatically playing content in MDPI documents.
Does not support or partially supports examples
  • There may be automatically playing or updating banners on MDPI.com, without integrated pause, stop, or hide functions.
Workarounds

If additional support is needed, please contact us through our support form, or by email at .

2.3.1 Three Flashes or Below Threshold (Level A)

Not Applicable
Notes
  • There is no flashing content on MDPI.com or in MDPI articles.

2.4.1 Bypass Blocks (Level A)

Does Not Support
Does not support or partially supports examples
  • There is no "Skip to main content" or equivalent bypass mechanism on MDPI.com. Keyboard users will need to tab through repeated navigation elements before reaching the main content.
Workarounds

Ease of use for keyboard-only users will be improved on the new MDPI.com platform.

2.4.2 Page Titled (Level A)

Partially Supports
Support examples
  • Most web pages, including all article pages, have clear, descriptive titles.
  • 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
  • Individual web pages such as the search results page, have a generic title.
Workarounds

Instances of insufficiently clear or descriptive web page titles will be remediated on the new MDPI.com platform.

2.4.3 Focus Order (Level A)

Does Not Support
Does not support or partially supports examples
  • There are multiple instances on MDPI.com where keyboard focus does not move to intended targets, use of positive tabindex value is not logical, hidden or empty elements receive focus, or keyboard focus is not placed or maintained on opened modals.
Workarounds

The upcoming, new mdpi.com platform is better suited for most accessibility needs, including better optimization of focus order. Visit https://www.mdpi.com/redirect/new_site.

2.4.5 Multiple Ways (Level AA)

Supports
Support examples
  • Users can find journals and articles in multiple ways (e.g., search, journal list, subject/category navigation), providing more than one method to locate most content.

2.4.6 Headings and Labels (Level AA)

Partially Supports
Support examples
  • Headings and labels typically describe sections and controls clearly (e.g., "Latest Articles", "For Authors", "Advanced Search"), supporting navigation and comprehension.
Does not support or partially supports examples
  • There are individual controls such as search fields that have the same name but different actions.
  • There are individual programmatic labels such as the article type selection dropdown in the article search function, that do not convey the purpose of the control.
Workarounds

Instances of inappropriate descriptive labels will be remediated on the new MDPI.com platform.

2.4.7 Focus Visible (Level AA)

Does Not Support
Does not support or partially supports examples
  • Keyboard focus indicator is frequently absent, or indistinguishable from the surrounding UI, especially for links, icon‑only buttons, and secondary actions. As a result, keyboard users often cannot reliably determine which element has focus, and the criterion is not met for a substantial portion of the site's interactive components.
Workarounds

Instances of inappropriate focus indication will be remediated on the new MDPI.com platform.

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
  • There are no functions requiring pointer gestures on MDPI.com.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Supports
Support examples
  • All functionality that can be operated using a single pointer is executed on the up-event of the pointer, not the down-event of the pointer. After a down-event of the pointer, execution of the function can be aborted by moving the pointer elsewhere.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Does Not Support
Does not support or partially supports examples
  • Some inputs, composite buttons, and custom widgets (e.g., certain filter toggles, preview/image controls, and menu icons) either have no accessible name or use a generic label that does not match the visible text or purpose, meaning the “label in name” requirement is not consistently met across all components.
Workarounds

Instances of missing or inadequate label names will be remediated on the new MDPI.com platform.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

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

2.5.7 Dragging Movements (Level AA 2.2 only)

Supports
Support examples
  • All functionality that uses a dragging movement for operation (for example, a slider control to selection publication years in the article search) can also be achieved by a single pointer without dragging or by text-input.

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

Does Not Support
Does not support or partially supports examples
  • Not all interactive elements on MDPI.com have sufficiently large target sizes for pointer inputs.
Workarounds

Instances of insufficient target sizes will be remediated on the new MDPI.com platform.

3.1.1 Language of Page (Level A)

Partially Supports
Support examples
  • All MDPI.com web pages are tagged as English language pages.
  • Some non-article PDFs have already been accessibility-tagged.
Does not support or partially supports examples
  • PDF versions of articles do not currently have language tags.
  • Some non-article PDFs have not been accessibility-tagged yet.
Workarounds
  • Accessibility-tagged PDF versions of articles can be requested from .
  • We will continue replacing non-article PDFs with accessibility-tagged versions.

3.1.2 Language of Parts (Level AA)

Partially Supports
Support examples
  • All MDPI.com pages are in English.
Does not support or partially supports examples
  • Some acquired journals may have article content that includes mixed languages (e.g., German, French, in addition to English) on a single page, but language changes are not always marked with appropriate attributes.
Notes
  • Proper 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.
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
  • User interface components receiving focus does not initiate changes of context.

3.2.2 On Input (Level A)

Supports
Support examples
  • Changing the setting of user interface components does not automatically cause changes of context, unless this is the express and clearly labeled purpose of the component.

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 MDPI articles follow the same layout and navigation templates.

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.

3.2.6 Consistent Help (Level A 2.2 only)

Partially Supports
Support examples
  • Help mechanisms such as links to the Help Center, contact pages, and author instructions are present on many pages (e.g., in the global navigation and footer).
Does not support or partially supports examples
  • Help links and resources do not always appear in a fully consistent relative position across all page templates.
Workarounds

If you cannot find or access the required support on our websites, please contact us by email via .

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.
Does not support or partially supports examples
  • Error messages are not consistently programmatically associated with the corresponding form controls and are not always announced by assistive technologies, so some users, especially screen reader users, may not reliably perceive or locate all errors.
Workarounds

If additional support is needed, please reach out through the contact form or by email to .

3.3.2 Labels or Instructions (Level A)

Does Not Support
Does not support or partially supports examples
  • There are labels that are not persistently visible or missing in certain search functions across MDPI.com, and some dropdown controls are missing visible labels.
Workarounds

Instances of missing or insufficient labels will be remediated on the new MDPI.com platform.

3.3.3 Error Suggestion (Level AA)

Partially Supports
Support examples
  • When input errors are detected on MDPI.com pages, suggestions for correction are provided. For example, forms provide inline messages suggesting how to correct an error (e.g., "Invalid email format"). This level of guidance is consistently applied across all forms and flows.
  • When input errors are made in the support form, clear instructions on the error are provided.
  • When input errors are made in response to captchas, instructions and alternatives are provided.
Does not support or partially supports examples
  • The level of guidance is not consistent between forms and workflows. Due to error identification and form feedback issues, error suggestions can be inconsistent, especially across complex workflows such as the payment portal.
Workarounds

If you require any support on either technical or accessibility issues, please contact us through our support forms or by email at or .

3.3.7 Redundant Entry (Level A 2.2 only)

Partially 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.
Does not support or partially supports examples
  • There are also some individual cases where users are asked to re‑enter identical information within a flow (such as repeating contact details or affiliation data, and Proceedings proposals) without auto‑population.
Workarounds

Instances where redundant entries are required will be remediated on the new MDPI.com platform.

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

Supports
Support examples
  • Authentication is possible without a cognitive function test and alternatives are offered.

4.1.1 Parsing (Level A)

Partially Supports
Does not support or partially supports examples
  • The PDF versions of articles are not reliably tagged for accessibility.
Workarounds

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

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 (submission nav, popups, filters, payment widgets, search, special issues) missing accessible names or states, or exposing incorrect ARIA attributes.
  • Button labels to expand figures or tables in web versions of articles are missing both role and name.
Workarounds

Missing or incorrect names, roles, and values will be remediated on the new MDPI.com platform.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Does Not Support
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 MDPI.com returns no results.
Workarounds

Announcement of status messages will be improved on the new MDPI.com platform. If further support is needed, please contact us through the contact form, or contact the journal team by email, or send an email to .

Section 508

Section 508: Applications

Section 508: Applications detail
Criteria Conformance Level Remarks and Explanations
503.2 User Preferences Supports MDPI.com runs in standard browsers and does not function as a standalone native application. It does not limit or override any browser or operating system settings, functions, or user preferences. If you encounter a specific instance of any specific accessibility feature being limited or blocked on MDPI.com, please send an email to so we can make sure all accessibility features are compatible.
503.3 Alternative User Interfaces Not Applicable The platform does not provide an alternative user interface that functions as assistive technology.
503.4.1 Caption Controls Not Applicable The platform does not provide its own media player.
503.4.2 Audio Description Controls Not Applicable The platform does not implement a custom media playback interface.

Section 508: Functional

Section 508: Functional detail
Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Partially Supports The upcoming, new mdpi.com platform is better suited for most accessibility needs. Please visit https://www.mdpi.com/redirect/new_site.
302.2 With Limited Vision Partially Supports
302.3 Without Perception of Color Partially Supports
302.4 Without Hearing Supports Text alternatives as well as subtitles are available for audio and video content.
302.5 With Limited Hearing Supports
302.6 Without Speech Supports Vocal capabilities are not required for any function of MDPI.com.
302.7 With Limited Manipulation Supports Physical manipulation is not required for any function of MDPI.com.
302.8 With Limited Reach and Strength Supports
302.9 With Limited Language, Cognitive, and Learning Abilities Supports

Section 508: Interoperability with assistive Technology

Section 508: Interoperability with assistive Technology detail
Criteria Conformance Level Remarks and Explanations
502.2.1 User Control of Accessibility Features Supports MDPI provides and maintains web platforms. Any software components on MDPI platforms are maintained and developed by third-parties. We strive to work with third-party providers whose software supports all accessibility needs and to integrate partner software in a manner that does not disrupt or diminish any accessibility features. If any support is needed regarding accessibility topics, please contact .
502.2.2 No Disruption of Accessibility Features Supports
502.3.1 Object Information Supports
502.3.2 Modification of Object Information Supports
502.3.3 Row, Column, and Headers Supports
502.3.4 Values Supports
502.3.5 Modification of Values Supports
502.3.6 Label Relationships Supports
502.3.7 Hierarchical Relationships Supports
502.3.8 Text Supports
502.3.9 Modification of Text Supports
502.3.10 List of Actions Supports
502.3.11 Actions on Objects Supports
502.3.12 Focus Cursor Supports
502.3.13 Modification of Focus Cursor Supports
502.3.14 Event Notification Supports
502.4 Platform Accessibility Features Supports

Section 508: Support Documentation

Section 508: Support Documentation detail
Criteria Conformance Level Remarks and Explanations
602.2 Accessibility and Compatibility Features Supports
602.3 Electronic Support Documentation Supports
602.4 Alternate Formats for Non-Electronic Support Documentation Supports All support documentation 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
603.3 Accommodation of Communication Needs Supports For any specific accessibility accommodations, please contact .

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 Screen reader users can reach and read core content. 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. The upcoming, new mdpi.com platform is better suited for most accessibility needs. Please visit https://www.mdpi.com/redirect/new_site.
4.2.2 Usage with limited vision Partially Supports Users relying on zoom and high contrast can read most content. Contrast failures and small target sizes of elements across multiple templates and workflows, plus missing focus indicators, reduce usability for low‑vision users.
4.2.3 Usage without perception of colour Partially Supports Color is never the only indicator for information on MDPI.com. 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.
4.2.4 Usage without hearing Supports Text alternatives as well as subtitles are available for audio and video content.
4.2.5 Usage with limited hearing Supports
4.2.6 Usage with no or limited vocal capability Supports Vocal capabilities are not required for any function of MDPI.com.
4.2.7 Usage with limited manipulation or strength Supports Physical manipulation is not required for any function of MDPI.com.
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 MDPI.com does not operate with closed functionality.
5.2 Activation of accessibility features Supports Where accessibility features are provided, they can be activated without relying on methods that do not support such needs.
5.3 Biometrics Not Applicable MDPI products do not use biometric information.
5.4 Preservation of accessibility information during conversion Partially Supports PDF versions of MDPI articles are currently not tagged for accessibility. The website versions of articles are generally better suited for accessibility needs than the PDF version. We are actively working on making PDF versions of articles more accessible and hope to achieve this by Q3 2026. Until then, please contact to request individual, remediated PDF versions of articles with alt text.
5.5 Operable parts Not Applicable MDPI products are web-based and do not have manually operable components.
5.6 Locking or toggle controls Not Applicable MDPI.com does not use locking or toggle controls.
5.7 Key repeat Not Applicable There are no key repeat functions on MDPI.com.
5.8 Double-strike key acceptance Not Applicable MDPI products are web-based and do not contain a physical keyboard.
5.9 Simultaneous user actions Not Applicable Functions on MDPI.com do not require 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 Not Applicable
10.6 Audio description timing 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 The Accessibility Compliance Report (ACR) is publicly available on a dedicated accessibility page.
12.1.2 Accessible documentation Supports Product documentation is provided in an electronic and accessible web format and available in a non-web format on request. To request an accessible PDF version of this accessibility report, please contact .
12.2.2 Information on accessibility and compatibility features Supports
12.2.3 Effective communication Supports Please contact for assistance of any kind on accessibility-related matters.