Introduction
Product Name: SciProfiles
Report Version: Version 1 – October 2026
VPAT Version: Voluntary Product Accessibility Template® (VPAT®) International Edition Version 2.5Rev
Product Description
SciProfiles is an open-access scholarly social network platform providing researcher profiles, publication lists, research networks, and collaboration features, with search and browse functionality, and help resources for researchers and readers.
Product Scope
This report covers the SciProfiles platform, including all publicly accessible pages on sciprofiles.com, such as profile pages, feed pages, search pages, messaging and notification pages, as well as other content provided by the platform.
To view accessibility compliance reports for other MDPI products, please visit https://www.mdpi.com/accessibility.
Notes
This report covers the SciProfiles platform. As SciProfiles continues to evolve, accessibility improvements are incorporated into ongoing platform development to provide a more inclusive experience for all users.
The "Publication" cards on the webpage contain PDF download links; these links are retrieved via the Scilit API and sourced from data crawled from over 30,000 publishers. They are considered outside the scope of this accessibility compliance assessment. For information on accessibility of the publication PDFs, please consult the respective publishers' accessibility compliance reports or contact them directly.
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
- Alt texts are added for most core images such as SciProfiles logos.
Does not support or partially supports examples
- Some images may have redundant roles or over-specified alt text.
Workarounds
In subsequent versions, an inspection tool will be used to detect and remove redundant role attributes from the image.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Not Applicable
Notes
- SciProfiles does not contain prerecorded audio-only or video-only media. All audio or video media are videos synchronized with audio tracks, and are evaluated under 1.2.2, 1.2.3, and 1.2.5.
1.2.2 Captions (Prerecorded) (Level A)
Does Not Support
Does not support or partially supports examples
- Videos in the list of posts on profile pages generally do not have subtitles.
Notes
- Captions are supported by the third-party platform (Cloudflare Stream) but are currently not enabled for existing media.
Workarounds
Please contact the posters of videos for additional information or scripts. If that is not possible or feasible, please contact us at [email protected] so we can provide support.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Does Not Support
Does not support or partially supports examples
- Videos with audio tracks on SciProfiles generally lack audio descriptions and equivalent media alternatives.
Workarounds
Please contact the posters of videos for audio tracks or media alternatives. If that is not possible or feasible, please contact us at [email protected] so we can provide support.
1.2.4 Captions (Live) (Level AA)
Not Applicable
Notes
- There is no live video or audio content on SciProfiles.
1.2.5 Audio Description (Prerecorded) (Level AA)
Does Not Support
Does not support or partially supports examples
- Videos with audio tracks on SciProfiles generally lack audio descriptions.
Workarounds
Please contact the posters of videos for audio tracks or media alternatives. If that is not possible or feasible, please contact us at [email protected] so we can provide support.
1.3.1 Info and Relationships (Level A)
Partially Supports
Support examples
- In most cases, information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Does not support or partially supports examples
- The footer navigation section was not constructed using list tags, and category names were not marked with specific tags.
- The "profile" page contains multiple `<nav>` tags—specifically, the header navigation at the top and the sub-page navigation below; the internal navigation tags lack `role` attributes and do not use `aria-label` to distinguish between them.
Workarounds
We will fix these issues in a future version. If this criterion causes issues for you, please contact us at [email protected] so we can provide support.
1.3.2 Meaningful Sequence (Level A)
Supports
Support examples
- The rendered tag structure aligns with the natural reading order.
1.3.3 Sensory Characteristics (Level A)
Supports
Support examples
- Information on SciProfiles does not rely solely on sensory characteristics. All images, icons, and navigation elements are accompanied by corresponding text.
- Any website content with sensory components is accompanied by appropriate descriptive text or a text alternative.
- Support services consist primarily of text content, with a few icon buttons that already have text descriptions configured.
1.3.4 Orientation (Level AA 2.1 and 2.2)
Does Not Support
Notes
- SciProfiles does support landscape layout or interaction design.
Workarounds
If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
Does Not Support
Support examples
- Standard input fields collecting user information include appropriate autocomplete attributes (e.g., name, email).
- On the contact page all input fields use the correct autocomplete attributes, allowing you to use the contact form to request support with other parts of the SciProfiles website.
Does not support or partially supports examples
- Most input fields in add publication forms, add institution forms, and user information forms are missing autocomplete attributes.
Notes
- The website uses HTML autocomplete attributes to programmatically identify the purpose of some input fields. However, most forms do not include these attributes, so the purpose of many input fields cannot be programmatically determined.
Workarounds
If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
1.4.1 Use of Color (Level A)
Supports
Support examples
- All links are underlined; there are no other states requiring color differentiation.
1.4.2 Audio Control (Level A)
Supports
Support examples
- Only posts from official accounts feature videos with audio; there is no auto-play function, and the player utilizes a third-party Cloudflare service, allowing users to pause playback via the controls.
1.4.3 Contrast (Minimum) (Level AA)
Partially Supports
Support examples
- The majority of SciProfiles website and content meets minimum contrast requirements.
- All Help Center content meets the minimum text contrast requirements.
Does not support or partially supports examples
- Some secondary text elements, disabled text, and subtle link text on profile-related pages do not meet the required minimum contrast ratio. This includes the profile status placeholder text, profile completion messages, and secondary information links.
- When the default profile picture background color is yellow or orange, it's hard to see clearly.
- The text for the ORCID tooltip at the top of the profile page is light green, which users might find difficult to read.
Workarounds
- Users may rely on browser or operating-system contrast/accessibility settings where available.
- If this criterion causes issues for you, please contact us at [email protected] so we can provide support.
1.4.4 Resize text (Level AA)
Partially Supports
Support examples
- The majority of text on SciProfiles can be resized to 200% without loss of content or functionality.
Does not support or partially supports examples
- The text in the search bar may become truncated on higher zoom.
Workarounds
The search function works correctly, even though its descriptive text is partially cut off. If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
1.4.5 Images of Text (Level AA)
Partially Supports
Support examples
- In most cases, text is presented as actual text rather than images of text.
- Images in the Help Center were illustrative content rather than images used to replace textual information, such as screenshots showing where to find a particular button.
Does not support or partially supports examples
- Logos such as university or journal logos may present written university and journal names as images.
Workarounds
If you have any questions about university or journal logos, please contact us at [email protected] so we can provide support.
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.
- Content and pages reflow normally across different 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
- The vast majority of buttons and input fields meet the contrast requirements.
Does not support or partially supports examples
- Certain elements in the layout lack contrast. For example, on the profile publications pages, disabled options within the "Publication" filter menu may be difficult to distinguish for some users. Additionally, the default avatar lacks sufficient contrast against the yellow background, making it hard to see clearly. On the "Posts" sub-page of the "My Profiles" section, when the "Send Post" button is disabled, the color of the button blends too closely with the text, making it difficult to distinguish between them.
Workarounds
These issues will be fixed in subsequent versions. Until then, please contact us at [email protected] so we can provide support.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- Most tested web pages support increased text spacing without loss of content or functionality.
- Help Center content remains readable and functional when text spacing is increased.
Does not support or partially supports examples
- Some post content on profile pages may be clipped when increased text spacing is applied.
Workarounds
If this criterion causes issues for you, please contact us at [email protected] so we can provide support.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- Hover-triggered content remains visible when the pointer moves over it and does not disappear automatically while being interacted with.
Does not support or partially supports examples
- Some tooltip content cannot be dismissed using the Escape key without moving the pointer or focus.
Workarounds
- Moving the pointer away from the triggering element dismisses the tooltip.
- If this criterion causes issues for you, please contact us at [email protected] so we can provide support.
2.1.1 Keyboard (Level A)
Does Not Support
Support examples
- Main navigation, links, buttons, and most standard interactive controls can be accessed and operated using the keyboard.
Does not support or partially supports examples
- Some interactive elements cannot be accessed or operated via keyboard navigation. Identified issues include: The clickable "hero cards" on the homepage are skipped during Tab navigation; The "Log In" link in the sign-up modal cannot receive keyboard focus; The "Following," "Followers," and "Co-authors" controls in the "My Feed" section are skipped during keyboard navigation; The emoji options in the post editor cannot be accessed via the Tab key; The "Show more" control within the "Search Publications" feature is skipped during Tab navigation. Publication cards, PDF buttons, and "expand author info" buttons cannot receive focus.
- In the help center, the tabs cannot be selected through keyboard navigation.
Workarounds
We will fix the identified issues in an upcoming release. In the meantime, if you rely on keyboard navigation, please contact us at [email protected] so we can provide support.
2.1.2 No Keyboard Trap (Level A)
Partially Supports
Support examples
- In most cases, keyboard focus can enter and leave dialogs, popovers, menus, and other interactive components without becoming trapped. Dialogs can be exited using keyboard-accessible controls such as Cancel or the Escape key.
Does not support or partially supports examples
- On the "My Feed" page, once the filter type dropdown selector (located below the post input box) gains focus, the focus cannot be moved away from it.
Workarounds
If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Supports
Support examples
- No single-character keyboard shortcuts that trigger functionality were identified.
2.2.1 Timing Adjustable (Level A)
Not Applicable
Notes
- There are no instances of time limits anywhere on SciProfiles.
2.2.2 Pause, Stop, Hide (Level A)
Not Applicable
Notes
- No automatically moving, blinking, scrolling, or auto-updating content requiring pause, stop, or hide controls was identified. Carousel components require user interaction to navigate, rather than activating automatically.
2.3.1 Three Flashes or Below Threshold (Level A)
Not Applicable
Notes
- There are no instances of flashing content anywhere on SciProfiles.
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 SciProfiles. Keyboard and assistive technology users may need to navigate through repeated navigation content before reaching the main content.
Workarounds
If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
2.4.2 Page Titled (Level A)
Supports
Support examples
- SciProfiles pages provide meaningful page titles that identify the current page.
- User guidance content, such as profile completion guidance, is presented within pages that provide descriptive titles.
2.4.3 Focus Order (Level A)
Partially Supports
Support examples
- Main SciProfiles content follows a logical DOM order that matches the visual layout.
- Support pages present interactive elements in an order that follows the visual and logical sequence of the page.
Does not support or partially supports examples
- On the profile page, when a user clicks a tab in the dropdown menu (located next to the share button), the element receives focus twice.
Notes
- Product documents are static text documents with no focusable components.
Workarounds
If this criteria causes issues for you, please contact us at [email protected] so we can provide support.
2.4.4 Link Purpose (In Context) (Level A)
Partially Supports
Support examples
- The majority of links on SciProfile can be identified through a descriptive link text or from the link text together with its programmatically determined link context.
- Help center links and FAQ entries have descriptive text that identifies their purpose.
Does not support or partially supports examples
- The "Read more" link on the blog hero card does not include the article title in its link text, so the purpose is only clear from the adjacent heading.
Workarounds
In subsequent versions, the "Read more" link text will include the article title (e.g. "Read more about {article title}").
2.4.5 Multiple Ways (Level AA)
Supports
Support examples
- Users can reach content in more than one way: through the global navigation menu, the site-wide search, and direct links from the feed and profile pages.
- Help center content can be reached through the help center navigation as well as the site-wide search.
2.4.6 Headings and Labels (Level AA)
Partially Supports
Support examples
- Major content sections use descriptive headings and labels.
- Help center topics and FAQ sections use descriptive headings and labels that describe their content.
Does not support or partially supports examples
- Some section titles, such as the footer column titles ("Information", "Support", "MDPI Initiatives") and page titles like "Account Settings" and "Search Results", are styled with plain paragraph or div elements instead of proper heading markup.
Workarounds
In subsequent versions, visually styled titles will be converted to proper heading elements (h1-h6) so that headings describe topic and purpose programmatically.
2.4.7 Focus Visible (Level AA)
Does Not Support
Support examples
- All native interactive elements such as links, inputs, and buttons show a focus indicator.
- All focusable elements on support pages display a visible focus indicator when receiving keyboard focus.
Does not support or partially supports examples
- For many modal pop-ups, the close button does not display a border when focused via the Tab key. The focus indicator is generally a blue outline, which makes it insufficiently visible on blue backgrounds or around blue buttons, such as the "Join Now" buttons on the landing page, or the "Message" and "Follow" buttons on scholar profiles. Additionally, the focus indicator can be difficult to see when focusing on the tabs in scholar profiles.
Workarounds
We will fix the identified issues in subsequent versions. If this criterion causes issues for you, please contact us at [email protected] so we can provide support directly.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
Supports
Support examples
- Keyboard focus remains visible and is not completely obscured by fixed elements.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Supports
Support examples
- All functionality can be operated with single pointer actions; no multipoint or path-based gestures are required.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Supports
Support examples
- Interactive elements are activated on the up-event; users can cancel activation by moving the pointer away before release, and there are no functions that trigger on down-event only.
2.5.3 Label in Name (Level A 2.1 and 2.2)
Supports
Support examples
- Form inputs and text buttons expose their visible labels in the accessible name.
- All visible labels of controls on support pages match their accessible names.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Not Applicable
Notes
- No SciProfiles functionality requires device motion or user motion; all features are operable through standard pointer and keyboard inputs.
2.5.7 Dragging Movements (Level AA 2.2 only)
Not Applicable
Notes
- No SciProfiles functionality requires dragging movements; all operable elements support single-pointer activation.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
Partially Supports
Support examples
- Primary buttons and navigation targets meet the 24x24 CSS px minimum target size.
Does not support or partially supports examples
- Some icon-only controls are rendered at exactly 24x24 px with tightly spaced adjacent targets, making them difficult to activate for users with limited motor control.
Workarounds
In subsequent versions, the size and spacing of small icon targets will be increased beyond the minimum where feasible.
3.1.1 Language of Page (Level A)
Supports
Support examples
- The language of each page is programmatically declared on the html element (lang attribute); no missing-language issues.
- Product documentation is written in English and the language is identifiable in the document.
3.1.2 Language of Parts (Level AA)
Supports
Support examples
- All product documentation is written in a single language (English).
- All support content is provided in a single language, so no language-of-parts exceptions apply.
Notes
- Page content is generally in English. It is possible that technical terms or given names may be in different languages, or that certain quotations in user-uploaded content are not in English. In most cases, the meaning will either be explained in the surrounding content, or it will be evident to readers with appropriate background knowledge.
Workarounds
In case there are non-English terms that are not sufficiently explained in user-generated content, please contact the content's author. For further support, please contact us at [email protected].
3.2.1 On Focus (Level A)
Supports
Support examples
- Receiving focus does not trigger unexpected context changes; no pop-ups, submissions, or navigation occur when components receive focus.
3.2.2 On Input (Level A)
Supports
Support examples
- Changing input values does not automatically cause context changes; forms are only submitted through explicit user action such as clicking the submit button.
3.2.3 Consistent Navigation (Level AA)
Supports
Support examples
- Navigation menus, header and footer links are presented in a consistent relative order and appearance across all pages of the site.
- Navigation within the help center is consistent across all support pages.
3.2.4 Consistent Identification (Level AA)
Supports
Support examples
- Repeated elements are identified consistently. Examples include navigation buttons using consistent labels.
3.2.6 Consistent Help (Level A 2.2 only)
Partially Supports
Support examples
- The Feedback button is consistently positioned relative to other page content across all pages. The Support column links are consistently ordered on pages that include a footer.
Does not support or partially supports examples
- Registration, setup, and email verification pages lack a footer and therefore do not include the Support column links, so help mechanisms are not fully consistent across all pages.
Workarounds
Users who need assistance on pages without a footer can access the Help Center directly at https://sciprofiles.com/help-center or contact us at [email protected]. Terms & Conditions, Community Guidelines, Privacy Policy, and Disclaimer are also available directly on the website.
3.3.1 Error Identification (Level A)
Supports
Support examples
- In all cases where form validation fails, specific error messages will be displayed via a toast notification or directly below the individual field.
3.3.2 Labels or Instructions (Level A)
Supports
Support examples
- Every input field has a visible label or instruction, and labels are correctly associated with their fields.
3.3.3 Error Suggestion (Level AA)
Supports
Support examples
- Forms provide clear validation messages and guidance to help users identify and correct input errors before submission.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Partially Supports
Support examples
- The account closure process provides users with information about the consequences of closing their account and allows users to cancel before submitting the request.
Does not support or partially supports examples
- The account closure action is completed immediately after submission without an additional confirmation step or review before the account is closed.
Workarounds
If an account is closed accidentally, please contact SciProfiles Support at [email protected] to request assistance with account status.
3.3.7 Redundant Entry (Level A 2.2 only)
Supports
Support examples
- The platform reuses existing user information where available and does not require users to repeatedly enter the same information during common workflows.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
Supports
Support examples
- The authentication process supports accessible methods including standard username/password authentication, browser-assisted autofill, and ORCID single sign-on. The registration process provides password requirements and clear validation messages to help users complete authentication successfully.
4.1.2 Name, Role, Value (Level A)
Does Not Support
Support examples
- Most interactive components use standard HTML controls and accessibility attributes to expose their names, roles, and states.
Does not support or partially supports examples
- Some interactive components on SciProfiles do not expose sufficient accessibility information. Examples include icon-only buttons in the post editor (such as emoji and link buttons), so users composing or editing a post may not be able to identify the toolbar buttons via screen reader, and action buttons on post/profile cards in the feed, so users interacting with posts may encounter unlabeled controls when liking, commenting, bookmarking, or opening the "more" menu.
- The message and notification icons in the header lack accessibility labels.
Workarounds
Identified issues will be fixed in upcoming releases. Until then, please contact SciProfiles Support at [email protected] for assistance.
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Partially Supports
Support examples
- Form validation results and operation feedback (e.g., submission success or failure) are presented visually on the page.
Does not support or partially supports examples
- Status messages such as toast notifications and form submission results are not consistently exposed to assistive technologies; they do not use role="status", role="alert" or aria-live regions, so screen reader users may miss them.
Workarounds
- In subsequent versions, status messages will be implemented with appropriate ARIA live regions (role="status" / aria-live="polite") so that they are announced by assistive technologies.
- Until then, please contact us at [email protected] to provide individual support.
Section 508: Functional performance criteria
Section 508: Functional performance criteria detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 302.1 Without Vision |
Partially Supports |
Main workflows such as registration, login, search, browse profiles and publications, submit work, etc. are completable with a screen reader, but screen reader users may encounter icon-only buttons announced without context (see 2.5.3). Native links, form inputs and text buttons expose correct accessible names. Icon-only buttons (like/comment/bookmark, more menu) lack accessible names (see 2.5.3). Please contact us for support at [email protected]. |
| 302.2 With Limited Vision |
Partially Supports |
A user with limited vision (who relies on magnification, high contrast or keyboard navigation) can complete the main workflows. Related criteria do not prevent workflow completion; however, focus visibility affects keyboard navigation: clickable cards implemented as div/img elements and some icon-only buttons do not consistently show a visible focus indicator, so a low-vision keyboard user may lose track of focus position. Core tasks remain completable via native focusable elements inside these components. |
| 302.3 Without Perception of Color |
Supports |
Information and status are conveyed by text/icons in addition to colour throughout the main workflows. |
| 302.4 Without Hearing |
Partially Supports |
A user without hearing can complete the main workflows (register/login, search, browse, submit), none of which require audio. However, multimedia content is currently not accessible without hearing: embedded videos do not yet have captions enabled, so video content cannot be perceived. Captions (AI-generated or uploaded WebVTT) are being rolled out for all videos; until then, transcripts are available on request via [email protected]. |
| 302.5 With Limited Hearing |
Partially Supports |
All main workflows are completable without audio, but video content is not yet fully accessible because captions are not enabled for existing media. |
| 302.6 Without Speech |
Supports |
Speech or vocal capabilities are not required for any workflows on SciProfiles. |
| 302.7 With Limited Manipulation |
Partially Supports |
A user with limited manipulation (e.g. unable to use a mouse precisely) who operates the site by keyboard can complete the main workflows. The main content is keyboard operable and follows a logical focus order. But the website is not optimized for full keyboard use. Some clickable cards implemented as div/img with a click handler are not keyboard-focusable themselves (their inner stretched links are), some dropdown components have a nested focus order, and focus is not always easily visible. Missing by-pass blocks may also make full keyboard usage more cumbersome. We will work on fixing the identified issues in upcoming releases. Until then, please contact us at [email protected] for support. |
| 302.8 With Limited Reach and Strength |
Partially Supports |
A user with limited reach or strength (e.g. unable to use a mouse precisely) who operates the site by keyboard can complete the main workflows. The main content is keyboard operable and follows a logical focus order. But the website is not optimized for full keyboard use. Some clickable cards implemented as div/img with a click handler are not keyboard-focusable themselves (their inner stretched links are), some dropdown components have a nested focus order, and focus is not always easily visible. Missing by-pass blocks may also make full keyboard usage more cumbersome. SciProfiles does not have any physical components that need manipulation or strength beyond mouse and keyboard usage. We will work on fixing the identified issues in upcoming releases. Until then, please contact us at [email protected] for support. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
Consistent layout, descriptive headings and labels, and link text support users with cognitive or learning limitations. |
Section 508: Support Documentation
Section 508: Support Documentation detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 602.2 Accessibility and Compatibility Features |
Does Not Support |
The product documentation does not currently document the accessibility and compatibility features of the platform. In subsequent versions, an accessibility statement describing the platform's accessibility and compatibility features will be published and referenced in the product documentation. Until then, please refer to this Accessibility report or contact us at [email protected] for individual support. |
| 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 which is linked in the SciProfiles page footer. Further support and a direct channel of communication for accessibility issues is provided through [email protected]. |
| 603.3 Accommodation of Communication Needs |
Supports |
Support is provided through the help center and email at [email protected], where we will do our best to accommodate any user's individual communication requirements. |
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 |
Main workflows such as registration, login, search, browse profiles and publications, submit work, etc. are completable with a screen reader, but screen reader users may encounter icon-only buttons announced without context (see 2.5.3). Native links, form inputs and text buttons expose correct accessible names. Icon-only buttons (like/comment/bookmark, more menu) lack accessible names (see 2.5.3). Please contact us for support at [email protected]. |
| 4.2.2 Usage with limited vision |
Partially Supports |
A user with limited vision (who relies on magnification, high contrast or keyboard navigation) can complete the main workflows. Related criteria do not prevent workflow completion; however, focus visibility affects keyboard navigation: clickable cards implemented as div/img elements and some icon-only buttons do not consistently show a visible focus indicator, so a low-vision keyboard user may lose track of focus position. Core tasks remain completable via native focusable elements inside these components. |
| 4.2.3 Usage without perception of colour |
Supports |
Information and status are conveyed by text/icons in addition to colour throughout the main workflows. |
| 4.2.4 Usage without hearing |
Partially Supports |
A user without hearing can complete the main workflows (register/login, search, browse, submit), none of which require audio. However, multimedia content is currently not accessible without hearing: embedded videos do not yet have captions enabled, so video content cannot be perceived. Captions (AI-generated or uploaded WebVTT) are being rolled out for all
videos; until then, transcripts are available on request via [email protected]. |
| 4.2.5 Usage with limited hearing |
Partially Supports |
All main workflows are completable without audio, but video content is not yet fully accessible because captions are not enabled for existing media. |
| 4.2.6 Usage with no or limited vocal capability |
Supports |
Speech or vocal capabilities are not required for any workflows on SciProfiles. |
| 4.2.7 Usage with limited manipulation or strength |
Partially Supports |
A user with limited manipulation or strength (e.g. unable to use a mouse precisely) who operates the site by keyboard can complete the main workflows. The main content is keyboard operable and follows a logical focus order. But the website is not optimized for full keyboard use. Some clickable cards implemented as div/img with a click handler are not keyboard-focusable themselves (their inner stretched links are), some dropdown components have a nested focus order, and focus is not always easily visible. Missing bypass blocks may also make full keyboard usage more cumbersome.
SciProfiles does not have any physical components that need manipulation or strength beyond mouse and keyboard usage. We will work on fixing the identified issues in upcoming releases. Until then, please contact us at [email protected] for support. |
| 4.2.8 Usage with limited reach |
Partially Supports |
A user with limited reach (e.g. unable to use a mouse precisely) who operates the site by keyboard can complete the main workflows. The main content is keyboard operable and follows a logical focus order. But the website is not optimized for full keyboard use. Some clickable cards implemented as div/img with a click handler are not keyboard-focusable themselves (their inner stretched links are), some dropdown components have a nested focus order, and focus is not always easily visible. Missing bypass blocks may also make full keyboard usage more cumbersome. We will work on fixing the identified issues in upcoming releases. Until then, please contact us at [email protected] for support. |
| 4.2.9 Minimize photosensitive seizure triggers |
Supports |
SciProfiles does not feature any flashing or blinking content; only subtle loading-skeleton opacity animations below seizure thresholds. |
| 4.2.10 Usage with limited cognition, language or learning |
Supports |
Consistent layout, descriptive headings labels, and link text support users with cognitive or learning limitations. |
| 4.2.11 Privacy |
Supports |
All SciProfiles accessibility features work without any identifiable actions or surrendering personal data or disability-related information. |
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 |
SciProfiles does not feature any Closed Functionality software features. |
| 5.2 Activation of accessibility features |
Not Applicable |
SciProfiles does not feature any accessibility features that require activation. |
| 5.3 Biometrics |
Not Applicable |
|
| 5.4 Preservation of accessibility information during conversion |
Not Applicable |
|
| 5.5 Operable parts |
Not Applicable |
SciProfiles does not feature any physical components that can be operated by users. |
| 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 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 |
Captions are currently not enabled for existing media, so caption positioning cannot be used or verified by end users. However, the embedded video player (Cloudflare Stream) supports WebVTT captions, which allow caption positioning to be controlled. Captions will be included in future releases. In the meantime, users can request a transcript by contacting us at [email protected] — the SciProfiles team will coordinate with the authors to provide it. |
EN 301 549: Clause 12 - Documentation and Support Services
EN 301 549: Clause 12 - Documentation and Support Services detail
| Criteria |
Conformance Level |
Remarks and Explanations |
| 12.1.1 Accessibility and compatibility features |
Supports |
This accessibility conformance report lists and explains accessibility features and measures provided by SciProfiles. It is available from https://www.mdpi.com/accessibility which is linked in the SciProfiles page footer. In case you have any questions or feedback, please don't hesitate to contact us at [email protected] or [email protected]. |
| 12.2.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]. |
| 12.2.3 Effective communication |
Supports |
Support is provided through the help center and email at [email protected], where we will do our best to accommodate any user's individual communication requirements. |