Accessibility Conformance Report (ACR)

Product: MDPI Books

Version 1 – July 2026

Introduction

Product Name: MDPI Books

Report Version: Version 1 – July 2026

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

Product Description

MDPI Books brings together several kinds of book content at https://www.mdpi.com/books, including curated reprints from journal publishing, user-compiled selections, original open access books, and single-article reprints. The public website is used to browse, search, purchase or access books, and to find information about publishing, support, and account services.

Product Scope

MDPI Books refers to all publicly accessible web pages for books and reprints on https://www.mdpi.com/books, as well as associated workflows.

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) Partially 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) 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) Partially 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) 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) Partially Supports
2.1.2 No Keyboard Trap (Level A) Supports
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Not Applicable
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) Does Not Support
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) Does Not Support
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) Partially Supports
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) Not Applicable
2.5.8 Target Size (Minimum) (Level AA 2.2 only) Partially 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) 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) Partially Supports
3.3.2 Labels or Instructions (Level A) 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) Partially 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 text is 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.
  • All documents and guidelines in PDF format are correct and accessible.
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 text.
  • The CAPTCHA in the support form does not have alt text.
Notes
  • Images in books and reprints have alt text if provided by the authors.
Workarounds
  • Missing alt text or other text alternatives will be added in upcoming platform version releases.
  • We are currently developing internal tools and processes to add alternative text to all images in future MDPI Books and Reprints. For older books and reprints, please contact to request individual, remediated PDF versions of any books or reprints with alt text.
  • An audio alternative is available for the image CAPTCHA. If you are unable to use the support form, contact for accessibility assistance. Technical accessibility issues can be escalated to .

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

Not Applicable
Notes
  • There is no audio or video content on MDPI.com/books.

1.2.2 Captions (Prerecorded) (Level A)

Not Applicable
Notes
  • There is no audio or video content on MDPI.com/books.

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

Not Applicable
Notes
  • There is no audio or video content on MDPI.com/books.

1.2.4 Captions (Live) (Level AA)

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

1.2.5 Audio Description (Prerecorded) (Level AA)

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

1.3.1 Info and Relationships (Level A)

Partially Supports
Support examples
  • Most pages use semantic headings. Global navigation and footers use proper landmarks and list markup. Book detail pages generally expose title, sections, and <main> correctly.
  • Supporting documents such as Guidelines or Flyers in PDF format are tagged correctly.
  • Support/search flows include labeled controls (e.g., FAQ search with visually hidden label, breadcrumb nav with aria-label, sort buttons with accessible names).
  • The Nuxt-based Books web application exposes many interactive UI states via ARIA on controls (search, sort, breadcrumbs, icon buttons with labels).
Does not support or partially supports examples
  • Many core templates lack a <main> landmark, and some grouped content, such as book carousels and the news archive, rely on div elements instead of lists or labeled regions.
  • For screen reader users, Books and Reprint PDFs are not reliably accessible.
  • These pages consistently omit a <main> landmark, so the primary document region is not programmatically distinguishable from header/footer.
  • Some support subpages lack <main>, and FAQ/contact groupings are not always exposed as structured lists or named regions.
  • Client-rendered templates are inconsistent: the cart has no headings, and several app views do not expose page structure landmarks programmatically.
Workarounds
  • Identified issues will be remediated in upcoming releases. For immediate support, please contact .
  • For the Frontlist, we are working on modifying the templates to produce accessible PDFs in the future. For the Backlists, we are working on an inhouse tool to convert HTML versions to accessible PDF versions on demand. Until then, we suggest screen reader users use HTML versions where available. Alternatively, you can contact to request individual, remediated PDF versions.
  • Steady improvements on the websites are ensured, and A11Y required changes are the highest priority.

1.3.2 Meaningful Sequence (Level A)

Partially Supports
Support examples
  • Open Access Books published since January 1, 2026 follow a meaningful sequence.
  • We are working to fix the templates.
Does not support or partially supports examples
  • Open Access Books published prior to 2026 and Reprint PDFs have not been optimized for accessibility, so screen readers might not follow a meaningful sequence.
  • Book flyers have not been optimized for accessibility, so screen readers might not follow a meaningful sequence. Videos hosted on YouTube may read unrelated text and links after the video ends.
Notes
  • On all of the MDPI Books webpages, a correct reading sequence can be programmatically determined.
Workarounds
  • For individual remediated Open Access Book and Reprint PDFs, please email .
  • We are actively working on optimizing the flyer template for accessibility. Until then, please email for individual remediated flyers.

1.3.3 Sensory Characteristics (Level A)

Partially Supports
Support examples
  • Open Access Books published as of January 1, 2026 contain alt text that does not rely solely on the sensory characteristics of components to describe them.
Notes
  • The instructions for understanding and operating content do not rely solely on the sensory characteristics of the components.
  • For Open Access Books published before 2026, alt text may not be provided, and we do not change the figure captions provided by authors.
Workarounds

For individual remediated Open Access Books and Reprint PDFs with alt text, please email .

1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports
Notes
  • MDPI Books websites and content do not restrict view and operation to a single display orientation.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Supports
Notes
  • All input fields collecting information can be programmatically determined, including support services such as contact forms and the book proposal submissions form.

1.4.1 Use of Color (Level A)

Partially Supports
Support examples
  • Key book information uses text labels and subject tags with readable text, and does not rely on color alone. Inline summary links use underlines.
  • Support actions use labeled buttons with text, not color-only indicators.
  • Invalid fields use error text, a visible outline, and hint text together. Checked boxes show a checkmark in addition to color changes.
Does not support or partially supports examples
  • Many navigation and footer links rely only on color for identification. Some active states are indicated mainly by color change, for example nav items, breadcrumbs, or sorting order.
  • Support navigation links and the "Forgot Password?" link are only distinguishable as links by color and context.
  • Some controls show selection only through color. Sort buttons, current navigation links, and chosen filters do not always have a second visible sign of state beyond the color change.
Workarounds

Identified issues will be remediated in upcoming releases. For immediate support, please contact .

1.4.2 Audio Control (Level A)

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

1.4.3 Contrast (Minimum) (Level AA)

Partially Supports
Support examples
  • All core product pages and elements have sufficient contrast.
Does not support or partially supports examples
  • Individual, supporting elements, such as the headers in the footer, may have slightly insufficient color contrast.
Workarounds

The identified issues will be remediated in future releases. Until then, please contact for any support needs.

1.4.4 Resize text (Level AA)

Partially Supports
Support examples
  • All core product workflows work correctly when resized up to 200% without loss of content or functionality.
Does not support or partially supports examples
  • The data privacy button may overlap with supporting elements, such as related books, at the bottom of the book pages when resizing to 200%.
Workarounds

The identified issues will be remediated in future releases. Until then, please contact for any support needs.

1.4.5 Images of Text (Level AA)

Supports
Notes
  • There are no instances of images of text on the main MDPI.com/books pages.
  • It is possible for books to contain images of text if submitted by authors.
Workarounds

In case there is an image of text and you require support, please reach out to the corresponding author.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Partially Supports
Support examples
  • Pages use a responsive viewport and mobile-first layout. Filters, menus, and footer content stack on small screens and rearrange on larger ones. About, terms, support, and authorization forms reflow at narrow widths without sideways scrolling, and no wide tables needing both horizontal and vertical scrolling were found in the sample.
  • Support pages drop the desktop sidebar on mobile and show FAQ and contact as stacked buttons, keeping features usable on narrow screens without two-way scrolling.
  • Layouts use fluid width containers and responsive breakpoints. Mobile layouts swap some desktop controls for simpler ones, such as a sort dropdown instead of sort buttons.
Does not support or partially supports examples
  • Long category tags do not wrap on very narrow screens, so they can extend beyond the viewport at 320 pixels wide. A site-wide rule that hides horizontal overflow may clip that text rather than letting it reflow or scroll.
  • Shared components include non-wrapping tag chips and a global horizontal overflow suppression rule, which can cause clipped content on narrow viewports rather than true reflow.
Workarounds

Reflow and wrapping issues will be remediated in upcoming releases. For immediate support, please contact .

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

Partially Supports
Support examples
  • Focus rings use high-contrast teal on white. Text buttons and links are recognizable from their labels, not only from borders. Icon buttons use icons with at least three-to-one contrast on their background.
Does not support or partially supports examples
  • A number of controls and buttons on Books have borders with insufficiently strong color contrasts, making it more difficult for some users to recognize where these controls and buttons begin and end.
Workarounds

Contrast issues will be remediated in upcoming releases. For immediate support, 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. Examples include related book suggestions at the bottom of book pages, or individual footer links.
Workarounds

The identified issues will be remediated in future releases. Until then, please contact for any support needs.

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

Partially Supports
Support examples
  • Users activate menus, filters, and mobile navigation by clicking, not hovering. Hover effects are visual styling only and do not generally show additional content.
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. For example, this may affect the Disclaimer link in the page footer.
Notes
  • There is no core feature or workflow on MDPI.com/books for which content on hover or focus is required, but such content may be used for additional information or insight.
Workarounds

Instances of undismissable hover content will be remediated on the new platform. For immediate support, please contact .

2.1.1 Keyboard (Level A)

Partially Supports
Support examples
  • For Open Access Books published as of January 1, 2026, all functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
  • For all templates and guidelines, all functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Does not support or partially supports examples
  • Open Access Books published prior to 2026 and Reprints are not tagged, so not all functionality of the content is operable through a keyboard interface.
  • The flyers are not yet tagged, so not all functionality is operable through a keyboard interface.
Notes
  • All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Workarounds

For individual screen reader optimized older Open Access Books, Reprint requests, or Flyers, please email and we will send you a tagged version as soon as we can.

2.1.2 No Keyboard Trap (Level A)

Supports
Notes
  • We have not found any keyboard traps anywhere on the MDPI Books web pages and have programmed the website to not contain any. If you do encounter any keyboard trap, please contact us at as soon as possible, so we can fix it.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Not Applicable
Notes
  • Character key shortcuts are not implemented on MDPI Books websites or documents.

2.2.1 Timing Adjustable (Level A)

Not Applicable
Notes
  • Timing is not an essential part of any event or activity on web pages or content related to MDPI Books.

2.2.2 Pause, Stop, Hide (Level A)

Not Applicable
Notes
  • There is no moving, blinking, scrolling, or auto-updating information on web pages or content related to MDPI Books.

2.3.1 Three Flashes or Below Threshold (Level A)

Not Applicable
Notes
  • There is no flashing content on web pages or content related to MDPI Books.

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/books. 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 MDPI.com/books platform. Until then, please contact for any support required.

2.4.2 Page Titled (Level A)

Partially Supports
Support examples
  • All pages on MDPI.com/books, including all individual book and preprint pages, have clear, descriptive titles.
  • PDF file names are always named according to the title of the book or the preprint.
Does not support or partially supports examples
  • When opening a PDF in a browser, the page title may start with a string of random characters, and downloaded PDFs may have this random string of characters as the title.
Workarounds

The PDF name will continue with the name of the book or preprint after the random characters. We will work on solving the issue of file titles in upcoming updates. Until then, please contact for individual PDF files remediated for accessibility.

2.4.3 Focus Order (Level A)

Partially Supports
Support examples
  • All MDPI Books web pages can be navigated sequentially and in a meaningful order.
  • Open Access Books published since January 1, 2026 can be navigated in the correct order by keyboard users.
  • Guidelines and templates can be navigated in the correct order by keyboard users.
Does not support or partially supports examples
  • Open Access Books published prior to 2026 and Reprints have not been optimized for accessibility, so keyboard users may not be able to navigate content in the correct order.
  • Flyers have not yet been optimized for accessibility, so keyboard users may not be able to navigate content in the correct order.
Workarounds

For individual remediated Open Access Book and Reprint PDFs, or Book Flyers, please email .

2.4.5 Multiple Ways (Level AA)

Supports
Support examples
  • Users can find books and reprints in multiple ways (such as search, Library, types, or category filter), providing more than one method to locate any specific content.

2.4.6 Headings and Labels (Level AA)

Does Not Support
Support examples
  • The majority of form elements are labeled correctly and headings are mostly consistent.
Does not support or partially supports examples
  • Some programmatic labels may not convey the control's purpose with sufficient clarity. For example, the programmatic label for buying a specific book does not contain the name of the book or the price, and the field to sign up for the MDPI Books newsletter is only labeled with "Email". Some pages have incorrect heading level orders where heading levels increase by more than one or there is no level-one heading.
  • Book and reprint PDFs are currently not tagged.
Workarounds
  • The identified issues will be remediated in future releases. Until then, please contact for any support needs.
  • We are currently developing internal tools and processes to create properly tagged PDFs for future MDPI Books and Reprints. For older books and reprints, please contact to request individual, remediated PDF versions of any books or reprints.

2.4.7 Focus Visible (Level AA)

Partially Supports
Support examples
  • Open Access Books published since January 1, 2026 have been optimized for accessibility with a visible keyboard focus indicator.
  • Guidelines and templates have been optimized for accessibility with a visible keyboard focus indicator.
Does not support or partially supports examples
  • Open Access Books published prior to 2026 and Reprint PDFs have not been optimized for accessibility, so a keyboard focus indicator may not be visible.
  • Flyers have not yet been optimized for accessibility, so a keyboard focus indicator may not be visible.
Workarounds

For individual remediated Open Access Book and Reprint PDFs, or Book Flyers, please email .

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

Supports
Support examples
  • There is no user interface component that is entirely hidden when it receives keyboard focus on the MDPI Books website.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Partially Supports
Support examples
  • The core user interface uses only single click or tap. Carousels include Previous and Next buttons and clickable slide dots, so users are not limited to swipe gestures.
  • Support and FAQ interfaces use click or tap interactions such as buttons, accordions, and form fields. They do not require swipe or multipoint gestures.
Does not support or partially supports examples
  • On mobile and tablet, the Related Books carousel hides arrow controls and shows them only when more than four items are present, so swiping is often the sole way to move between slides.
Workarounds

For more information or support regarding Related Books, please email .

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 ofthe 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 or image controls, and menu icons) either have no accessible name or use a generic label that does not match the visible text, meaning the "label in name" requirement is not consistently met across all components. Examples include the arrow buttons under the widget on the front page showing featured Open Access Books, or buttons such as the Download PDF button for the flyer on the Publish With Us page.
Workarounds

Instances of missing or inadequate label names will be remediated in upcoming releases. Until then, please contact for further support.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Not Applicable
Notes
  • No specific motion input is required to use any MDPI Books functionality or to navigate the Books pages.

2.5.7 Dragging Movements (Level AA 2.2 only)

Not Applicable
Notes
  • Dragging motions are not required to use any MDPI Books functionality or to navigate the Books pages.

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

Partially Supports
Support examples
  • Target sizes are sufficient throughout main page and core content related to Books.
Does not support or partially supports examples
  • The distance between links in the page footer is insufficient.
Workarounds

Using the keyboard, users can tab between the footer links. Insufficient footer target sizes will be remediated in upcoming releases. Until then, please contact for further support.

3.1.1 Language of Page (Level A)

Partially Supports
Support examples
  • All MDPI.com/books web pages are tagged as English language pages.
  • All non-article PDFs have already been accessibility-tagged.
Does not support or partially supports examples
  • Language identification is missing from PDF versions of open access books, reprints, and promotional flyers.
Workarounds

Accessibility-tagged PDF versions of books and reprints can be requested from .

3.1.2 Language of Parts (Level AA)

Partially Supports
Support examples
  • All MDPI.com/books web pages are entirely in English.
Does not support or partially supports examples
  • Some books and journal articles may have content that includes mixed languages 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 book or reprint, or to .

3.2.1 On Focus (Level A)

Supports
Support examples
  • User interface components receiving focus does not initiate any changes of context.

3.2.2 On Input (Level A)

Supports
Support examples
  • MDPI Books mostly behaves predictably on actions where searches and navigation wait for a deliberate user action. Filter and sort changes refresh the results area in place instead of jumping to a new page or window. On the log-in or authorisation page, email and password fields do not auto-submit; users must actively press Sign In or Create an Account.

3.2.3 Consistent Navigation (Level AA)

Supports
Support examples
  • Navigation elements (such as the global header and footer) appear in consistent locations and order across pages, supporting predictable use.
  • All Books and Reprints follow the same layout and navigation templates.

3.2.4 Consistent Identification (Level AA)

Supports
Support examples
  • Repeated controls (such as search fields, login buttons, or icons) are identified consistently across the platform, promoting recognition.

3.2.6 Consistent Help (Level A 2.2 only)

Supports
Support examples
  • The Support page is consistently available through the page header.

3.3.1 Error Identification (Level A)

Partially Supports
Support examples
  • In forms, any wrong input is visually marked and an explanation of the error is provided underneath the form field in red text.
Does not support or partially supports examples
  • On the payment page, error messages relating to the human verification CAPTCHA as well as errors related to the telephone number in billing information may not be announced fully to screen reader users.
Workarounds

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

3.3.2 Labels or Instructions (Level A)

Supports
Support examples
  • For all pages on MDPI.com/books, forms and controls are labeled correctly to provide instructions and avoid confusion.
Does not support or partially supports examples
  • On payment.mdpi.com there are labels that are not persistently visible when the element is selected.
Workarounds

If any support is required, please reach out to .

3.3.3 Error Suggestion (Level AA)

Supports
Support examples
  • When input errors are detected on MDPI.com/books pages, suggestions for correction are provided. For example, forms provide inline messages suggesting how to correct an error (such as "This field must be a valid email"). 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.

3.3.7 Redundant Entry (Level A 2.2 only)

Supports
Support examples
  • When appropriate and available, information previously entered by the user that is required to be entered again in the same process is auto-populated.

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

Supports
Support examples
  • A cognitive function test is not required to log in to MDPI.com/Books.

4.1.1 Parsing (Level A)

Partially Supports
Support examples
  • Parsing is correct and complete on all MDPI.com/books web pages.
Does not support or partially supports examples
  • Books and Reprints are currently only available as PDF files, which are not reliably tagged for accessibility.
Workarounds
  • We are currently working on HTML versions of Books and Reprints which will be available as alternatives to users relying on screen readers. Additionally, we are working on improving our PDF templates and creation templates to produce accessible PDF versions of Books and Reprints in the future.
  • Until then, you can request individual, remediated PDF versions via .

4.1.2 Name, Role, Value (Level A)

Partially Supports
Support examples
  • Most controls use proper HTML and ARIA. Icons without visible labels, including Search, cart, and the menu button, still expose a name for assistive technology.
  • Dropdown menus and list boxes generally expose proper roles and expanded state. Icons used only for decoration are not announced to screen readers.
  • Product documentation pages (Terms and Conditions, Privacy Policy, Open Access Policy, About pages) are mostly headings, paragraphs, and standard text links. These expose clear link names and expected link roles without custom widgets.
  • Login exposes labeled email and password inputs and a named Login button. Support areas use regular links and search, without custom controls that hide their purpose.
Does not support or partially supports examples
  • Multiple informative buttons are missing accessible names or roles. Expand and collapse states are not always announced correctly sitewide. None of these issues affect core workflows.
  • The footer newsletter signup can expose Submit before the email field finishes loading.
  • Embedded services—Turnstile, Altmetric, and analytics—are partly outside MDPI's control and may not announce updates reliably to screen readers.
Workarounds

All identified instances will be addressed in upcoming updates. Until then, please reach out to to receive support and assistance. Please also let us know any issues you encounter, so we can work toward fixing them as soon as possible.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Does Not Support
Support examples
  • While content loads, users hear a labeled progress announcement on search, filters, and cart pages. Support flows use status-style notifications so messages can be detected by screen readers.
  • Support pages use an info banner exposed as a status region, confirming the design system can announce non-critical updates to screen readers.
Does not support or partially supports examples
  • Status feedback is mostly missing programmatic hooks. Result counts, form errors, cart confirmations, FAQ filtering, and homepage count changes update on screen but are often not announced to assistive technology.
  • FAQ filtering updates visually without a heard status message. Contact and newsletter flows lack alert or live-region containers for success and error feedback in the rendered HTML.
  • Third-party embeds may announce their own state changes. Cart and authentication toasts are not reliably marked up as status or alert messages users can hear.
Workarounds
  • After searches, filters, or cart actions, manually review the updated content region with screen reader reading commands such as "read from cursor" or "virtual buffer review" rather than relying on automatic announcements.
  • After submitting support or newsletter forms, visually confirm confirmation or error text on the page and re-read the form area with assistive technology if no announcement is heard.
  • If CAPTCHA or checkout steps fail silently in a screen reader, check for visible inline error text near the widget or form.
  • For further support, please contact MDPI Books support at .

Section 508

Section 508: Functional Performance Requirements

Section 508: Functional Performance Requirements detail
Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Partially Supports The majority of content and functionality on MDPI.com/books is accessible to users without vision. However, there are WCAG criteria which are only partially fulfilled, which may cause difficulties for some users. In case you require any support, please reach out to .
302.2 With Limited Vision Partially Supports
302.3 Without Perception of Color Partially Supports The majority of content and functionality on MDPI.com/books is accessible to users without perception of color. There are instances of insufficient color contrast, which we will address in upcoming updates. In case you require any support, please reach out to .
302.4 Without Hearing Supports Hearing is not required for any content or functionality on MDPI.com/books.
302.5 With Limited Hearing Supports
302.6 Without Speech Supports Speech is not required for any content or functionality on MDPI.com/books.
302.7 With Limited Manipulation Supports Physical manipulation is not required for any content or functionality on MDPI.com/books.
302.8 With Limited Reach and Strength Supports
302.9 With Limited Language, Cognitive, and Learning Abilities Supports MDPI.com/books features academic content which may be complex in nature. However, the website and functionality are designed to be easy to use. If you require any support, please reach out through the support page or by email to .

Section 508: Software

Section 508: Software detail
Criteria Conformance Level Remarks and Explanations
502 Interoperability with Assistive Technology Supports All MDPI products and services are designed to be fully interoperable with assistive technology. If you encounter any limitations to interoperability with any assistive software or tools you use, please contact us at .
503.2 User Preferences Not Applicable
503.3 Alternative User Interfaces Not Applicable
503.4 User Controls for Captions and Audio Description Partially Supports Synchronized audio is available with user controls for closed captions. Synchronized audio does not contain audio descriptions. We are working to host the videos in our own backend instead of via YouTube, to have more control over improving closed captions functionality on our videos. Until then, please contact us at for any support.

Section 508: Support Documentation and Services

Section 508: Support Documentation and Services 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 Supports
602.4 Alternate Formats for Non-Electronic Support Documentation Not Applicable All support functions are electronic.
603.2 Information on Accessibility and Compatibility Features Supports If you have any additional questions regarding accessibility, not covered on the accessibility page or in the accessibility conformance report, please contact us at or .
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 The majority of content and functionality on MDPI.com/books is accessible to users without vision. However, there are WCAG criteria which are only partially fulfilled, which may cause difficulties for some users. In case you require any support, please reach out to .
4.2.2 Usage with limited vision Partially Supports
4.2.3 Usage without perception of colour Partially Supports The majority of content and functionality on MDPI.com/books is accessible to users without perception of color. There are instances of insufficient color contrast, which we will address in upcoming updates. In case you require any support, please reach out to .
4.2.4 Usage without hearing Supports Hearing is not required for any content or functionality on MDPI.com/books.
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 content or functionality on MDPI.com/books.
4.2.7 Usage with limited manipulation or strength Supports Physical manipulation is not required for any content or functionality on MDPI.com/books.
4.2.8 Usage with limited reach Supports
4.2.9 Minimize photosensitive seizure triggers Supports There is no content on MDPI.com/books that carries an increased likelihood of triggering photosensitive seizures.
4.2.10 Usage with limited cognition, language or learning Supports MDPI.com/books features academic content which may be complex in nature. However, the website and functionality are designed to be easy to use. If you require any support, please reach out through the support page or by email to .
4.2.11 Privacy Supports MDPI's privacy policy is linked in the footer of the Books website. Please visit https://www.mdpi.com/books/about/privacy-policy.

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 Supports MDPI Books does not use any closed functionality software and does not restrict the use of supporting hardware or software.
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 MDPI Books does not use biometric information.
5.4 Preservation of accessibility information during conversion Does Not Support PDF versions of MDPI Books and Reprints are currently not tagged, which can be considered a loss of accessibility information, especially if the source material sent to us was tagged. We are actively working on making our PDF templates and processes more accessible. Until then, please contact to request individual, remediated PDF versions of books or reprints with accessible tagging and alt text.
5.5 Tactilely discernible operable parts Not Applicable MDPI Books is web-based and does not have physical, operable components.
5.6 Locking or toggle controls Not Applicable There are no locking or toggle controls.
5.7 Key repeat Not Applicable There are no key repeat functions.
5.8 Double-strike key acceptance Not Applicable MDPI Books is web-based and does not contain a physical keyboard.
5.9 Simultaneous user actions Not Applicable There are no required 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 MDPI Books does not contain video or audio content.
10.6 Audio description timing Not Applicable MDPI Books does not contain video or audio content.

EN 301 549: Clause 11 - Software

EN 301 549: Clause 11 - Software detail
Criteria Conformance Level Remarks and Explanations
11.5.2.4 Assistive technology Not Applicable
11.5.2.5 Object information Not Applicable
11.5.2.6 Row, column, and headers Not Applicable
11.5.2.7 Values Not Applicable
11.5.2.8 Label relationships Not Applicable
11.5.2.9 Parent-child relationships Not Applicable
11.5.2.10 Text Not Applicable MDPI Books does not provide any standalone software. Users interact with web platforms.
11.5.2.11 List of available actions Not Applicable
11.5.2.12 Execution of available actions Not Applicable
11.5.2.13 Tracking of focus and selection attributes Not Applicable
11.5.2.14 Modification of focus and selection attributes Not Applicable
11.5.2.15 Change notification Not Applicable
11.5.2.16 Modifications of states and properties Not Applicable
11.5.2.17 Modifications of values and text Not Applicable
11.6.1 User control of accessibility features Not Applicable
11.6.2 No disruption of accessibility features Not Applicable
11.7 User preferences Not Applicable
11.8.2 Accessible content creation Not Applicable
11.8.3 Preservation of accessibility information in transformations Not Applicable
11.8.4 Repair assistance Not Applicable
11.8.5 Templates Not Applicable

12: Documentation and Support Services

12: Documentation and Support Services detail
Criteria Conformance Level Remarks and Explanations
12.1.1 Accessibility and compatibility features Supports Documentation on accessibility features, issues, and workarounds is available in the accessibility conformance report. For any additional questions related to accessibility, customers can email the books team at and all users of MDPI products can email .
12.2.2 Information on accessibility and compatibility features Supports The accessibility conformance report is provided in HTML and PDF formats and has been tested for accessibility. For any additional questions related to accessibility, customers can email the books team at and all users of MDPI products can email .
12.2.3 Effective communication Supports Accessibility page in the footer.