Introduction
Product Name: Encyclopedia
Report Version: Version 1 – October 2026
VPAT Version: Voluntary Product Accessibility Template® (VPAT®) International Edition Version 2.5Rev
Product Description
MDPI operates Encyclopedia.pub: an open-access scholarly encyclopedia platform providing peer-reviewed scientific entries, videos, images, and insights, with search and browse functionality, and help resources for authors and readers.
Product Scope
This report covers the Encyclopedia platform. This includes all publicly accessible web pages on https://encyclopedia.pub, including entry pages, video pages, image pages, insights articles, search and browse pages, submission forms, help center, and other content available through the platform.
Please see https://www.mdpi.com/accessibility for the Accessibility Conformance Reports for other MDPI products.
Notes
This report covers the Encyclopedia platform. As Encyclopedia continues to evolve, accessibility improvements are incorporated into ongoing platform development to provide a more inclusive experience for all users.
Contact: [email protected]
Evaluation Methods Used
- Audit of representative pages and workflows by Deque.
- Use of browser developer tools and common accessibility heuristics (structure, semantics, keyboard support, color contrast, focus visibility, error handling, and ARIA usage).
- Consideration of expected interoperability with modern screen readers and other assistive technologies based on standard HTML and ARIA patterns.
WCAG Overview
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
- Most core images (such as entry cover images, journal logos and navigation icons) have text alternatives; decorative footer images are marked with empty alt text.
- All entry body images are accompanied by figure captions; alt text is retained if provided by the authors.
- All images on product documentation pages (Help Center, submission guidelines, etc.) have alt text.
- All images on support service pages have alt text.
- Most third-party components (such as the privacy settings button) have accessible names (aria-label="Privacy Settings").
Does not support or partially supports examples
- Some entry cover images in search results have empty alt attributes (alt=""); some icon-only links (favorites, add subject/topic, etc.) lack descriptive text; some article body images (e.g. illustrations in Insights articles) do not provide alt text.
- Most body images do not provide alt text; figure captions, while informative, cannot fully substitute for alt text.
- Some third-party components (such as icon buttons in the rich text editor TinyMCE and carousel indicators) have incomplete accessible names; we cannot guarantee the accessibility standard of third-party components.
Workarounds
- Missing alternative text will be added as soon as possible; for detailed information on body images, please contact the corresponding author.
- If you encounter any issues with third-party software, please contact [email protected].
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Partially Supports
Support examples
- As of 10 July 2026, full transcripts are provided for all new videos on Encyclopedia.
Does not support or partially supports examples
- A significant number of older videos, produced or uploaded before Encyclopedia's accessibility policy was introduced, do not provide a transcript.
Workarounds
In case you need a transcript for a specific video uploaded before July 2026, please contact [email protected] for assistance.
1.2.2 Captions (Prerecorded) (Level A)
Partially Supports
Support examples
- As of 10 July 2026, all new prerecorded videos on Encyclopedia feature open captions.
Does not support or partially supports examples
- A significant number of older videos, produced or uploaded before Encyclopedia's accessibility policy was introduced, do not provide captions.
Workarounds
In case you need captions for a specific video uploaded before July 2026, please contact [email protected] for assistance.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Partially Supports
Support examples
- As of 10 July 2026, full transcripts are provided for all new prerecorded videos on Encyclopedia.
Does not support or partially supports examples
- A separate audio description track is not provided for videos; purely visual information in some videos is conveyed only through the transcript.
Workarounds
For supplementary descriptions of video visuals, please refer to the full transcript; for other needs or for full transcripts of older videos, please contact [email protected] or the corresponding author.
1.2.4 Captions (Live) (Level AA)
Not Applicable
Notes
- There is no live audio or video content on Encyclopedia. Therefore, this criterion is not applicable.
1.2.5 Audio Description (Prerecorded) (Level AA)
Partially Supports
Support examples
- Videos provide a full transcript (Full Transcript) that can serve as a media alternative.
Does not support or partially supports examples
- A separate audio description track is not provided.
Workarounds
Please refer to the full transcript for supplementary information; contact [email protected] if assistance is needed.
1.3.1 Info and Relationships (Level A)
Partially Supports
Support examples
- Tables use correct HTML elements (such as table headers and table rows); the semantic structure of lists and headings is generally correct.
- Semantic tags such as headings and lists on product documentation pages are correct; information and relationships are programmatically determinable.
- Support service pages convey information and relationships through correct semantic structure.
- The semantic structure of most third-party components (such as the rich text editor) is generally correct.
Does not support or partially supports examples
- Some headings are not used according to semantic levels (some use div+styles to simulate headings); the role/relationships of some interactive elements (such as spans acting as buttons) are incomplete.
- The accessibility of some internal semantic elements in third-party components (TinyMCE editor, carousels, etc.) is incomplete.
Notes
- Web versions of Entries and Insights convey semantic structure correctly and are generally accessible. PDF versions are not reliably accessible to all screen readers and do not fully convey semantic structure.
Workarounds
- Identified issues will be remediated as soon as possible; until then, please contact [email protected] for support.
- Screen reader users are advised to use the web versions of Entries and Insights. If individually remediated PDF versions are required, please contact [email protected].
- If you encounter third-party software accessibility issues, please contact [email protected].
1.3.2 Meaningful Sequence (Level A)
Partially Supports
Support examples
- The visual display sequence of page content is consistent with the DOM arrangement sequence, with no logical disorder; text, images, form components and module blocks can all be recognized and read by assistive programs in the intended reading order.
- The content sequence of non-article documents is logically consistent and can be parsed by assistive programs in a normal and orderly manner.
- The arrangement of the support section fulfills accessibility requirements with no deviation in semantic interpretation.
Notes
- Web versions of Entries and Insights preserve meaningful reading sequence and are generally accessible. PDF versions are not reliably accessible to all screen readers and cannot guarantee preservation of meaningful reading sequence.
Workarounds
Screen reader users are advised to use the web versions of Entries and Insights. If individually remediated PDF versions are required, please contact [email protected].
1.3.3 Sensory Characteristics (Level A)
Supports
Support examples
- Any website content with sensory components is accompanied by appropriate descriptive text or a text alternative.
- All operation prompts in the software interface are marked with textual labels and do not rely solely on sensory information such as color, position or icons.
Workarounds
If content relies on sensory characteristics, please contact the corresponding author via page comments or email for alternative descriptions.
1.3.4 Orientation (Level AA 2.1 and 2.2)
Supports
Support examples
- The website is responsive and supports switching between portrait and landscape orientations; display orientation is not forcibly locked, allowing normal reading and operation.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- The website generally uses programmatic attributes (such as HTML autocomplete) to identify the purpose of input fields.
Does not support or partially supports examples
- Some elements in certain forms (such as submission forms and feedback forms) are missing autocomplete attributes.
Workarounds
Identified issues will be remediated as soon as possible; until then, please contact [email protected] for support.
1.4.1 Use of Color (Level A)
Partially Supports
Support examples
- Most information transmission, status indication and operation instructions do not rely solely on color; they are complemented by text, styles and other forms of identification.
- All information in product documents is conveyed through text or other non-color means.
- When a support form input has an error, the input turns red but also displays an error text.
Does not support or partially supports examples
- Some dropdown selection boxes (e.g. subject selection in submission forms) indicate "not selected" state using color/text color only.
Workarounds
Identified issues will be remediated as soon as possible and relevant pages will be updated in accordance with WCAG; until then, please contact [email protected] for support.
1.4.2 Audio Control (Level A)
Supports
Support examples
- All autoplaying videos start muted by default and provide built-in player controls that allow users to unmute, pause, or adjust volume independently of system settings.
1.4.3 Contrast (Minimum) (Level AA)
Does Not Support
Support examples
- The majority of body text and primary content meets the 4.5:1 contrast requirement.
Does not support or partially supports examples
- Multiple text elements across the platform fail the 4.5:1 contrast requirement, major affected component types are: light grey metadata text such as dates, view counts, and testimonial attribution; the "Peer Reviewed" status label; red links and video series titles on light backgrounds; and red text on white buttons.
- Text elements in entry PDFs that use the platform's brand colors are likely to fail the 4.5:1 contrast requirement, consistent with the same issues identified on the website. These include red headings, red links, and light grey metadata text.
- The CAPTCHA element used when subscribing or creating a new account may lack sufficient contrast. Its design is controlled by a third party.
Notes
- Automated testing identified systemic color contrast failures across multiple component types. The platform's brand colors (red, grey, and orange) do not always meet the 4.5:1 requirement when used for text on light backgrounds.
- PDF versions of Entries are generated by the platform and use the same brand color scheme as the website.
- Text in third-party software components is generally readable, but the platform cannot guarantee that all third-party text meets the 4.5:1 contrast requirement, as these components are developed and maintained externally.
Workarounds
- Users who have difficulty reading low-contrast text can use browser zoom or system-level high-contrast modes. For individual assistance, please contact [email protected].
- Users with accessibility requirements are advised to use the web version of the entry. For assistance, please contact [email protected].
- Users who encounter difficulty reading text in third-party components can contact [email protected] for assistance.
1.4.4 Resize text (Level AA)
Does Not Support
Support examples
- The desktop version of the website uses responsive design and allows for zooming and text resizing.
Does not support or partially supports examples
- On mobile devices, the meta viewport setting maximum-scale=1.0 prevents users from zooming text up to 200%. On desktop, zooming may cause floating action buttons to overlap and obscure content.
Notes
- PDF versions of Entries are viewed in PDF readers, which control text resizing independently of web page settings. The viewport meta tag issues on the website do not affect PDF viewing.
- Text resizing in third-party software components such as CAPTCHAs is controlled by the external provider. The platform cannot guarantee that all third-party components support text resizing up to 200%.
Workarounds
- Text can be enlarged using browser zoom on desktop.
- Users on mobile devices can use system-level magnification tools.
- Obscured content may become visible when scrolling.
- For assistance, contact [email protected].
1.4.5 Images of Text (Level AA)
Supports
Support examples
- Images of text are not used to convey information; all text is provided in an accessible text form.
- All text used to convey information in the platform interface is presented as real text that can be resized, recolored, and read by assistive technologies.
Notes
- Encyclopedia uses real text rather than images of text for all platform-controlled interface elements. Images that contain text as part of a larger visual context, such as user-submitted charts or screenshots, are outside the scope of this criterion.
1.4.10 Reflow (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- The website is generally responsive and can be read and operated normally across most viewports.
Does not support or partially supports examples
- The page meta viewport sets maximum-scale=1.0, which disables text scaling and page zooming on mobile, affecting text resizing and reflow.
Workarounds
We are adjusting the viewport setting in accordance with WCAG; until then, text can be enlarged via browser desktop view or assistive technology, or contact [email protected] for help.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- Non-text web elements (icons, graphics, control borders, etc.) meet the required contrast.
- Platform-generated non-text elements, such as UI components in PDFs, meet the 3:1 contrast requirement.
- Most third-party components meet the non-text contrast requirement.
Does not support or partially supports examples
- Some third-party components (such as some icons in the rich text editor) have insufficient contrast; we cannot fully guarantee them.
Notes
- Most non-text elements in content documents meet the 3:1 contrast requirement. However, some user-submitted graphical objects (such as charts or infographics) may not meet the required contrast ratio, as their design is determined by the authors.
Workarounds
- Users who have difficulty perceiving these graphical objects can contact the corresponding author for an alternative description, or contact [email protected] for assistance.
- If you encounter contrast issues with third-party components, please contact [email protected].
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Supports
Support examples
- Content remains readable after adjusting text spacing, without loss of information or functionality.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- Most hover- and focus-triggered content, such as tooltips and dropdown menus, remains visible while hovered over and does not disappear automatically, allowing users enough time to read it.
Does not support or partially supports examples
- Some hover/focus-triggered components cannot be dismissed with the Esc key. These include the profile dropdown menu in the page header, the notification list dropdown in the page header, and tooltips on Entry detail pages. Keyboard users must move the pointer or click elsewhere to close them.
Workarounds
Keyboard users can move focus to another element using the Tab key to continue navigating. If the content remains visible and obstructs other content, users can press Tab or Shift+Tab to shift focus. If support is required, please contact [email protected] for assistance.
2.1.1 Keyboard (Level A)
Partially Supports
Support examples
- Most functionality can be operated by keyboard (navigation, form submission, search, etc.).
- All core content can be navigated by keyboard.
- Core support functions, such as submitting a contact form and navigating the Help Center, are operable using a keyboard alone.
- The main functionality of third-party components can be operated by keyboard.
Does not support or partially supports examples
- Some icon-only links and span-based interactive controls (favorites, add subject, view toggles, etc.) lack accessible names and keyboard operability; some functions in the rich text editor depend on the mouse.
- Some interactive elements in product documentation (such as simulated buttons) have incomplete keyboard operability.
- Some interactive elements in the Help Center, such as expandable FAQ sections or tab controls, cannot be fully operated using a keyboard alone.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
2.1.2 No Keyboard Trap (Level A)
Supports
Support examples
- Focus is not trapped in any component; keyboard can move in and out normally.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Supports
Support examples
- No single-character key shortcuts are used, or mechanisms to turn them off/remap are provided.
2.2.1 Timing Adjustable (Level A)
Does Not Support
Support examples
- Form data is automatically saved during the session. After a timeout, users can restore their previously entered content upon logging back in, preventing data loss.
Does not support or partially supports examples
- Sessions expire 1 hour after login without advance warning and regardless of user activity, and users cannot extend the session. Users may be unexpectedly logged out while working.
Workarounds
Users who are logged out unexpectedly can log back in and will be prompted to restore their previously entered form content. No data is lost. For assistance, please contact [email protected].
2.2.2 Pause, Stop, Hide (Level A)
Partially Supports
Support examples
- For the majority of playing or moving content, user-controlled play/pause is provided.
Does not support or partially supports examples
- Carousels on the homepage and some recommended videos auto-play/auto-rotate, and pause/stop/hide mechanisms are incomplete.
Workarounds
Identified issues will be remediated as soon as possible; until then, use the controls on the page or contact the office to pause auto-playing content.
2.3.1 Three Flashes or Below Threshold (Level A)
Not Applicable
Notes
- The platform does not generate or embed flashing content in its own interface or system components. User-submitted content, such as images or videos, is outside the platform's direct control.
Workarounds
If you encounter a flashing element in user-submitted content, please contact the corresponding author or [email protected].
2.4.1 Bypass Blocks (Level A)
Does Not Support
Does not support or partially supports examples
- The page does not provide a clear "skip to main content" mechanism, so repeated navigation blocks cannot be easily bypassed.
Workarounds
We are evaluating and adding skip links; until then, use browser or assistive technology shortcuts to jump, or contact [email protected] for support.
2.4.2 Page Titled (Level A)
Partially Supports
Support examples
- Each page has a descriptive title that clearly identifies the page topic.
Notes
- Web versions of Entries have clear and descriptive page titles. Page titles in PDF versions are not reliably accessible to all screen readers, and the PDF title may not be correctly conveyed.
Workarounds
Screen reader users are advised to use the web versions of Entries and Insights. If individually remediated PDF versions are required, please contact [email protected].
2.4.3 Focus Order (Level A)
Supports
Support examples
- The focus movement order follows the reading and operation logic and is consistent with the visual order of content.
2.4.4 Link Purpose (In Context) (Level A)
Partially Supports
Support examples
- The text of most links clearly indicates their purpose.
Does not support or partially supports examples
- Some icon-only links (favorites, add subject, view toggle icons, etc.) lack accessible names, making link purpose unclear.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
2.4.5 Multiple Ways (Level AA)
Supports
Support examples
- The website provides multiple ways to locate content, such as search, breadcrumb navigation, and category directories.
2.4.6 Headings and Labels (Level AA)
Partially Supports
Support examples
- Most section headings and form labels, such as those on the About page and Help Center, clearly describe the content or purpose of their sections and controls.
Does not support or partially supports examples
- On several pages, visual headings are marked up as <div> elements with CSS styles rather than semantic heading tags. For example, the main page title on the Insights page, the book titles on the Reprints page, and the section titles on the About page. Additionally, some form fields, such as the pagination input on the Search and Insights pages, and the subject selection dropdowns on the Entry and Video submission pages, lack visible labels and rely on placeholders or ARIA attributes only.
Workarounds
Users who have difficulty navigating by headings can use the site search or content filters to find information. For form fields without visible labels, users can refer to the surrounding context or contact [email protected] for assistance.
2.4.7 Focus Visible (Level AA)
Partially Supports
Support examples
- Most elements have a visible focus indicator when focused.
Does not support or partially supports examples
- The focus indicator of some third-party components (such as the rich text editor and carousels) is not obvious.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
Partially Supports
Support examples
- Most focused elements are visible.
Does not support or partially supports examples
- Some fixed floating elements (such as notification icons and feedback buttons) may obscure focused content.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Not Applicable
Notes
- Encyclopedia does not require any multipoint or path-based gestures.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Supports
Support examples
- Pointer operations provide a cancellation mechanism; actions are not triggered accidentally.
2.5.3 Label in Name (Level A 2.1 and 2.2)
Supports
Support examples
- Accessible names include the visible label text.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Not Applicable
Notes
- Encyclopedia does not feature any functionality operated by device motion or user motion.
2.5.7 Dragging Movements (Level AA 2.2 only)
Supports
Support examples
- Where dragging operations exist, alternative operation methods are provided.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
Supports
Support examples
- Clickable targets meet the minimum size requirement (or have sufficient spacing).
3.1.1 Language of Page (Level A)
Partially Supports
Support examples
- Pages declare the correct lang attribute (en).
Notes
- Web versions of Entries are correctly tagged with the English language attribute. PDF versions do not reliably declare the language attribute, which may affect screen reader pronunciation.
Workarounds
Screen reader users are advised to use the web versions of Entries and Insights. If individually remediated PDF versions are required, please contact [email protected].
3.1.2 Language of Parts (Level AA)
Partially Supports
Support examples
- Different language fragments of Encyclopedia web pages are correctly marked.
Does not support or partially supports examples
- Language fragments within user-authored content may not be reliably marked with their correct language attribute, especially in PDF versions where the platform has limited control over author-submitted markup. This can cause screen readers to use incorrect pronunciation rules.
Notes
- Web versions of Entries are marked up with correct language attributes. However, language changes within user-authored content (such as foreign-language quotes or terms) may not always be marked, as the platform cannot guarantee the markup quality of author-submitted material.
Workarounds
Screen reader users are advised to use the web version of the entry, which has better language markup support. If a user encounters pronunciation issues in a specific entry, please contact the author or [email protected] for assistance.
3.2.1 On Focus (Level A)
Supports
Support examples
- Focusing an element does not cause unexpected changes in context.
3.2.2 On Input (Level A)
Partially Supports
Support examples
- Most inputs do not cause unexpected changes in context.
Does not support or partially supports examples
- Some dropdown selections (such as subject filters) change page content immediately on input, which may cause context changes.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
3.2.3 Consistent Navigation (Level AA)
Supports
Support examples
- Navigation structure is consistent across pages; repeated components appear in the same order.
3.2.4 Consistent Identification (Level AA)
Partially Supports
Support examples
- Most repeated functional components are identified consistently.
Does not support or partially supports examples
- Some icon buttons (such as view toggles and favorites) lack consistent labels across pages.
Workarounds
Identified issues will be remediated as soon as possible; please contact [email protected] for support.
3.2.6 Consistent Help (Level A 2.2 only)
Supports
Support examples
- The website provides consistent and easily discoverable help entry points (Help Center, feedback button, contact information).
3.3.1 Error Identification (Level A)
Partially Supports
Support examples
- For most forms, when an input error is detected, the erroneous field is visually marked and a text error message is displayed next to it, allowing users to identify and correct the error.
- All input errors in support forms are visually marked and described in text, allowing users to identify and correct errors.
Does not support or partially supports examples
- On the Entry, Video, and Image submission forms, error messages for the contributors field and the subject selection dropdown are not programmatically associated with the corresponding input fields (for example, via aria-describedby), and the error text is not specific enough to describe the issue. Screen reader users may not be aware that an error has occurred or may not know how to correct it.
Workarounds
Users who encounter difficulty identifying or understanding form errors can contact [email protected] for assistance.
3.3.2 Labels or Instructions (Level A)
Partially Supports
Support examples
- Most input fields, such as those in the contact form and user profile, have clear and persistent visible labels (for example, "Email", "First Name", "Last Name").
Does not support or partially supports examples
- Some input fields rely only on placeholders or ARIA attributes rather than persistent visible labels. For example, the pagination input on the Search and Insights pages has no visible label, and the subject selection dropdowns on the Entry and Video submission forms lack associated visible labels.
Workarounds
Users who have difficulty identifying the purpose of these fields can refer to the surrounding context or contact [email protected] for assistance.
3.3.3 Error Suggestion (Level AA)
Supports
Support examples
- Appropriate error suggestions and error prevention mechanisms are provided to reduce input errors.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Supports
Support examples
- The Entry and Video submission forms provide a review step before final submission, allowing users to check and correct their information. Users can also edit or withdraw their submissions after posting.
3.3.7 Redundant Entry (Level A 2.2 only)
Supports
Support examples
- Form data is automatically saved during the submission process. When users return to a form after a session timeout, they are offered the option to restore their previously entered content, eliminating the need to re-enter the same information.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
Supports
Support examples
- The authentication process does not rely solely on a single cognitive function verification method.
4.1.2 Name, Role, Value (Level A)
Partially Supports
Support examples
- Most interactive components have correct names, roles and values.
- Links on product documentation pages (About, Terms and Conditions, Privacy Policy, Advisory Board) have clear text names. Form controls on the Contact and Partner pages, including input fields, buttons, and dropdowns, have visible labels and accessible names that are exposed to assistive technologies.
Does not support or partially supports examples
- Some span-based buttons and icon-only links lack accessible names; the role and state information of some custom controls is incomplete.
Notes
- Web versions of Entries expose names, roles, and values to assistive technologies more reliably than PDF versions. PDF versions do not reliably convey this programmatic information.
Workarounds
- Identified issues will be remediated as soon as possible; please contact [email protected] for support.
- Screen reader users are advised to use the web versions of Entries and Insights. If individually remediated PDF versions are required, please contact [email protected].
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Does Not Support
Does not support or partially supports examples
- Some dynamically updated status messages on the page (such as search result updates and notification counts) are not programmatically exposed to assistive technology via role="status" or aria-live.
- Some status messages in third-party components are not programmatically exposed.
Workarounds
We are improving the accessible notification mechanism for status messages; until then, please contact [email protected] for real-time status prompts.
Section 508: Functional performance criteria
Section 508: Functional performance criteria detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 302.1 Without Vision |
Partially Supports |
The majority of features and content on Encyclopedia is accessible to users without vision. Some icons and images lack text alternatives, affecting usage without vision. Missing alternative text will be added as soon as possible; please contact [email protected] for any support. |
| 302.2 With Limited Vision |
Partially Supports |
The website supports text scaling and high contrast. Viewport zoom is disabled on mobile, and some visual information has insufficient contrast. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 302.3 Without Perception of Color |
Partially Supports |
Most information does not rely solely on color. Some dropdowns use color to distinguish state. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 302.4 Without Hearing |
Supports |
Videos provide captions and transcripts. |
| 302.5 With Limited Hearing |
Supports |
Videos provide captions and transcripts. |
| 302.6 Without Speech |
Supports |
Encyclopedia does not require vocal capabilities for operation. |
| 302.7 With Limited Manipulation |
Supports |
The website supports keyboard operation, reducing reliance on fine manipulation. Some icon-only controls and the third-party editor are not friendly to users with limited manipulation abilities. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 302.8 With Limited Reach and Strength |
Supports |
The responsive layout adapts to different screen sizes and touch ranges. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
Content is well organized, with help and feedback channels provided. |
Section 508: Support Documentation
Section 508: Support Documentation detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 602.2 Accessibility and Compatibility Features |
Supports |
This report describes the accessibility and compatibility features supported by the product. |
| 602.3 Electronic Support Documentation |
Supports |
This ACR is designed to be accessible and is publicly available in HTML and PDF formats on https://www.mdpi.com/accessibility. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation |
Supports |
This ACR is designed to be accessible and is publicly available in HTML and PDF formats on https://www.mdpi.com/accessibility. If additional alternate formats or accessibility accommodations are required, please contact us at [email protected]. We are committed to supporting your accessibility needs as best we can. |
Section 508: Support Services
Section 508: Support Services detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 603.2 Information on Accessibility and Compatibility Features |
Supports |
This Accessibility Conformance Report lists accessibility features and potential issues and workarounds. It is publicly available on https://www.mdpi.com/accessibility. Further support and a direct channel of communication for accessibility issues is provided through [email protected]. |
| 603.3 Accommodation of Communication Needs |
Supports |
Support services provide alternative channels for accessibility communication needs. |
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 features and content on Encyclopedia is accessible to users without vision. Some icons and images lack text alternatives, affecting usage without vision. Missing alternative text will be added as soon as possible; please contact [email protected] for support. |
| 4.2.2 Usage with limited vision |
Partially Supports |
The website supports text scaling and high contrast. Viewport zoom is disabled on mobile, and some visual information has insufficient contrast. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 4.2.3 Usage without perception of colour |
Partially Supports |
Most information does not rely solely on color. Some dropdowns use color to distinguish state. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 4.2.4 Usage without hearing |
Supports |
Videos provide captions and transcripts. |
| 4.2.5 Usage with limited hearing |
Supports |
Videos provide captions and transcripts. |
| 4.2.6 Usage with no or limited vocal capability |
Supports |
Encyclopedia does not require vocal capabilities for operation. |
| 4.2.7 Usage with limited manipulation or strength |
Partially Supports |
The website supports keyboard operation, reducing reliance on fine manipulation. The responsive layout adapts to different screen sizes and touch ranges. Some icon-only controls and the third-party editor are not friendly to users with limited manipulation abilities. Identified issues will be remediated as soon as possible; please contact [email protected] for any support. |
| 4.2.8 Usage with limited reach |
Supports |
The responsive layout adapts to different screen sizes. |
| 4.2.9 Minimize photosensitive seizure triggers |
Supports |
No content prone to triggering photosensitive seizures is provided. |
| 4.2.10 Usage with limited cognition, language or learning |
Supports |
Content is well organized, with help and feedback channels provided. |
| 4.2.11 Privacy |
Supports |
Privacy settings and cookie consent mechanisms are provided. |
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 |
The product has no closed functionality (does not block assistive technology). |
| 5.2 Activation of accessibility features |
Not Applicable |
Encyclopedia aims to be accessible, but does not have any accessibility features that can be activated individually. |
| 5.3 Biometrics |
Not Applicable |
|
| 5.4 Preservation of accessibility information during conversion |
Not Applicable |
|
| 5.5 Operable parts |
Not Applicable |
Encyclopedia does not have any manually operable parts. |
| 5.6 Locking or toggle controls |
Not Applicable |
|
| 5.7 Key repeat |
Not Applicable |
|
| 5.8 Double-strike key acceptance |
Not Applicable |
|
| 5.9 Simultaneous user actions |
Not Applicable |
|
EN 301 549: Clause 7 - ICT with Video Capabilities
EN 301 549: Clause 7 - ICT with Video Capabilities detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 7.1.1 Captioning playback |
Partially Supports |
The video player supports caption playback. The caption controls of some third-party video players are incomplete. If you encounter difficulties related to this feature, please contact [email protected] for support. |
| 7.1.2 Captioning synchronization |
Partially Supports |
Video captions are generally synchronized. The captions of some videos have slight synchronization deviations. If you encounter difficulties related to this feature, please contact [email protected] for support. |
| 7.1.3 Preservation of captioning |
Supports |
Captions are preserved during video conversion/transmission. |
| 7.1.4 Captions characteristics |
Partially Supports |
Caption display is clear in most cases. The display characteristics (color, font size) of some video captions cannot be customized. If you encounter difficulties related to this feature, please contact [email protected] for support. |
| 7.1.5 Spoken subtitles |
Not Applicable |
Displayed captions are usually not programmatically determinable and therefore not available to be spoken by supporting technology. Note that Encyclopedia generally does not feature video content with interlingual subtitles where the caption language differs from the main audio. |
| 7.2.1 Audio description playback |
Does Not Support |
The video player does not support audio description playback. Please refer to the full transcript of the video as an alternative. |
| 7.2.2 Audio description synchronization |
Does Not Support |
No audio description track or synchronization is provided. For supplementary descriptions of video visuals, please refer to the full transcript; for other needs please contact the corresponding author or [email protected]. |
| 7.2.3 Preservation of audio description |
Supports |
Audio description is preserved during video conversion. |
| 7.3 User controls for captions and audio description |
Does Not Support |
Videos on Encyclopedia use hard-coded subtitles that are part of the video image and cannot be turned on or off. No toggleable caption tracks or audio description controls are provided. |
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 |
Partially Supports |
Platform-selected embedded players generally position captions to avoid obscuring relevant visual content. For user-uploaded videos displayed via third-party iframe embeds, Encyclopedia cannot control or verify caption positioning, as this is determined by the external player or the uploader. Users who encounter captions that obscure relevant content are advised to contact the user who uploaded the video or [email protected] for assistance. |
| 10.6 Audio description timing |
Not Applicable |
Encyclopedia does not provide separate audio descriptions for video content. Since no audio descriptions are present, the timing requirement for audio descriptions does not apply. |
EN 301 549: Clause 12 - Documentation and Support Services
EN 301 549: Clause 12 - Documentation and Support Services detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 12.1.1 Accessibility and compatibility features |
Supports |
This report serves as the accessibility and compatibility features statement, publicly available on the accessibility page of MDPI: https://www.mdpi.com/accessibility. |
| 12.2.2 Information on accessibility and compatibility features |
Supports |
Please contact us at [email protected] for further information on any accessibility and compatibility features, or refer to https://www.mdpi.com/accessibility for MDPI's accessibility policies. |
| 12.2.3 Effective communication |
Supports |
Our support services are committed to accommodate any individual communication needs to the best of their abilities. Please contact us through [email protected] and we will support you as best we can. |