ACR Index Accessibility Conformance Reports for software

Dove Medical Press

Accessibility Conformance Report published by Taylor Francis

Conformance by level

Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.

Source: View the original report published by Taylor Francis.

These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.

All reported criteria (78)

Conformance as stated by Taylor Francis in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A Supports Non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Images that were previously implemented as background images on span/div elements have been converted into img elements with appropriate alt attributes, ensuring they are accessible to screen readers.
1.2.1 Audio-only and Video-only (Prerecorded) A Supports Audio-only podcast content on the site has transcripts available in PDF format. These transcripts provide a text equivalent of the spoken audio and primarily reflect spoken dialogue, including speaker identification where applicable. Relevant non-speech elements are included where they convey meaning. If the PDF is not yet accessible, users may contact us to request PDF remediation or an alternative format transcript. Remediation will be provided within a reasonable timeframe. The website doesn't feature any video content without a speech-audio track.
1.2.2 Captions (Prerecorded) A Partially Supports Video abstracts are hosted on YouTube and include closed captions, which can be enabled or disabled by the user. These captions provide a text representation of spoken audio. Captions are primarily generated via YouTube and may not consistently include speaker identification or non-speech elements (e.g. sound effects), and may not fully capture all relevant audio content. A full audit of legacy video content has not been undertaken. Where captions do not meet accessibility requirements, please contact us to request remediation of the content.
1.2.3 Audio Description or Media Alternative (Prerecorded) A Partially Supports Since March 2026, transcripts have been collected from authors for all video abstracts and are made available alongside the video content. These transcripts include spoken dialogue and, where applicable, speaker identification. Non- speech elements are included where they convey meaning. Transcripts provided are standard (spoken content only) and reflect what is heard in the media. They do not systematically include descriptions of visual-only information unless it is conveyed through the audio. For content published prior to March 2026, transcripts may not be consistently available or fully accessible. Users may contact us to request accessible transcripts, and remediation will be provided within a reasonable timeframe.
1.3.1 Info and Relationships A Supports When information is presented visually (like headings, lists, tables, or emphasized text), the same organization and relationships are built into the website's code (HTML or ARIA). This ensures everyone, including people using screen readers or other assistive technologies, can understand how information is organized and related.
1.3.2 Meaningful Sequence A Supports The order of content in the website's code matches the logical reading order that users expect. This ensures that when people use screen readers, text-only browsers, or customize how a page appears (like enlarging text), the information still makes sense in the order it's presented.
1.3.3 Sensory Characteristics A Supports Instructions for understanding and operating content does not solely rely on characteristics such as size, visual location, orientation, sound, or shape.
1.4.1 Use of Color A Supports Colour is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Secondary visual indicators have been added to form error messages to help users identify them as errors.
1.4.2 Audio Control A Supports No audio on the site plays automatically. There is a mechanism to pause or stop the audio; or volume can be controlled independently from the overall system volume level.
2.1.1 Keyboard A Supports All functionality is operable using the keyboard only. There are no specific timings to complete individual keystrokes. Elements on the “Article Collection” page that were not previously focusable have been updated to support keyboard focus, ensuring full operability using a keyboard only.
2.1.2 No Keyboard Trap A Supports There are no situations where you enter a modal with the keyboard and cannot get back to where you were. Users are advised of the exit method where it is not a standard exit method (Arrow, Tab, Esc).
2.1.4 Character Key Shortcuts A Not Applicable There are no keyboard shortcuts utilised on this site.
2.2.1 Timing Adjustable A Not Applicable There are no time limits on the site.
2.2.2 Pause, Stop, Hide A Supports The news ticker automatically scrolls content every four seconds, which may make it difficult for users to read or interact with the information before it changes. To address this, a pause control has been provided, allowing users to stop the movement so the content remains static and fully readable.
2.3.1 Three Flashes or Below Threshold A Not Applicable There is no flashing content on the site.
2.4.1 Bypass Blocks A Supports The first clickable item on the page is a “skip to main content link” moving focus directly to the main content. Landmarks define core parts of the page to support quick navigation with assistive technologies. The three navigation landmarks are uniquely named (Main Navigation, Navigation, Footer Navigation).
2.4.2 Page Titled A Supports Each page has a unique title element that describes what is on that page, to let users know where they are and what type of content to expect.
2.4.3 Focus Order A Supports Focusable elements receive focus in an order that preserves meaning and operability. When a keyboard user tabs through a page, the order goes from top to bottom and left to right, as you would read the page.
2.4.4 Link Purpose (In Context) A Supports A link’s destination is clear from either the link text itself or the surrounding sentence context.
2.5.1 Pointer Gestures A Not Applicable There are no author-created gestures within the web content that requires actions to be carried out using a gesture (swiping, pinching, and so on) or drawing, which can also be done with a button. This does not affect gestures built into device operating systems such as iOS and Android, assistive technology, or browsers.
2.5.2 Pointer Cancellation A Supports Functions that use a single pointer are completed when the user releases the pointer. For example, pressing a button, is triggered on mouse-up.
2.5.3 Label in Name A Supports User interface components with labels that include text or images of text, have a corresponding accessible name that begins with the text that is presented visually.
2.5.4 Motion Actuation A Not Applicable There is no reliance on author-created gestures within the web content that requires device motion, like shaking or tilting, to carry out an action. Such as shake to refresh, tilt controls for games, gesture recognition through camera. This does not affect motion features built into device operating systems such as iOS and Android, assistive technologies, or browsers.
3.1.1 Language of Page A Supports The page language is identified using the lang attribute in the HTML element (en); English non-region specific.
3.2.1 On Focus A Supports When a user interface component receives focus, it does not initiate unexpected changes.
3.2.2 On Input A Partially Supports For the most part, there are no unexpected changes of context on user input. Issues: • Submission process: several checkboxes and buttons may trigger an unexpected page refresh or redirect. • Contact us form: Users are required to select the enquiry type from a drop-down menu. Once the type is selected the form will dynamically show/hide fields. Users are not informed that selecting either the type will change the available fields. • Remediation 15 June 2026.
3.2.6 Consistent Help A Supports The placement of help details and options is consistent across the site and easy to find. There is a "contact us" link in the persistent footer, this takes the user to the "make an enquiry" online form. Mailing addresses, phone numbers and an email address are available on the "our locations” tab.
3.3.1 Error Identification A Supports Errors are presented once the users submits the form - they do not appear as the error is made, or when the field is exited. Upon form submission, errors are presented at the top of the form, and are announced to the screen reader, for example, "Alert: email is a required field". Error messages are linked to the relative form field and adequately identifies, describes, or navigates users to the fields to correct.
3.3.2 Labels or Instructions A Supports Help is provided to prevent form errors – sometimes the label is enough on its own, elsewhere additional hint text or instructions are provided. Required fields are consistently indicated, with an explanation provided at the start of forms to clarify that an asterisk (*) denotes mandatory input. Field labels have been refined to improve clarity (e.g., "Institution type" instead of "Institution", and "Enquiry type" instead of "Type"), and actions have been made more descriptive (e.g., "Register" instead of "Finish"), ensuring users better understand both the purpose of fields and how to complete the forms successfully.
3.3.7 Redundant Entry A Supports Forms do not ask users to enter the same information more than once in a single session; unless the information is essential, no longer valid, or for security purposes.
4.1.1 Parsing A Not Applicable Note: this criterion has been removed from WCAG 2.2. HTML and browsers have improved at handling coding errors. And, assistive technology no longer parses the code directly, but now relies on the browser to do it, making this guideline outdated. Most issues it covered will now fall under WCAG 1.3.1 Info and Relationships or WCAG 4.1.2 Name, Role, Value criteria.
4.1.2 Name, Role, Value A Supports User interface elements and components have the right names, roles, states, properties and values so they are recognized correctly by assistive technologies.
1.2.4 Captions (Live) AA Not Applicable No live video or audio, such as webinars or podcasts, are hosted on or delivered via the site.
1.2.5 Audio Description (Prerecorded) AA Does Not Support Issues: • No video content currently includes a separate audio description track for actions, descriptions, and other essential visual information that is not conveyed through the original audio track. • Remediation 17 April 2027 Note: • See 1.2.3 for information about text transcripts.
1.3.4 Orientation AA Supports The content of the site does not restrict its view and operation to a single-display orientation (portrait / landscape), unless a specific display orientation is essential. When rotating a device from portrait to landscape the site remains readable and usable. The grey tag box has been updated to ensure that long text wraps correctly within the screen boundaries on smaller displays. This prevents content from overflowing off-screen and ensures all text remains accessible when viewing article pages or search results on smartphones.
1.3.5 Identify Input Purpose AA Supports The purpose of form fields can be identified by the browser, so that auto-complete suggestions can be offered, making it easier to fill out forms and reduce the need for manual typing. Added appropriate auto-complete attributes to the fields collecting user data during enquiry, registration, authentication and submission processes.
1.4.3 Contrast (Minimum) AA Supports The visual presentation of body text and images of text has a contrast ratio of at least 4.5:1. Large-scale text and images of large-scale text have a contrast ratio of at least 3:1. Text that is part of a logo or brand name has no minimum contrast requirement. Burger menu, error text and "pay text" have been adjusted to meet the contrast requirement. The "Submit your manuscript" has been adjusted to provide sufficient contrast against the background. Error message text colours have been updated to ensure adequate contrast on white backgrounds. The "Pay" text colour has also been revised to improve contrast against its background.
1.4.4 Resize text AA Supports Text on the web page can be resized up to 200% without distorting the layout, without loss of content or functionality, except for captions and images of text. This allows users who need larger text to read comfortably without the need for additional assistive tools like screen magnifiers. Modals have been updated to contain all interactable elements inside regardless of the screen size or browser scale.
1.4.5 Images of Text AA Supports Text is used to convey information, rather than images of text, except where: • The image of text can be visually customized by the user requirements. • A particular presentation of text is essential to the information being conveyed (such as text that is part of a logo or brand name). All non-"img" elements with image backgrounds have been adjusted for screen readers.
1.4.10 Reflow AA Supports Content throughout the site is reflowable and responsive, remaining readable and usable without requiring horizontal scrolling for text or controls. The grey tag box is updated to ensure the text wraps within the screen and is not falling off on smaller displays. The CSS has been adjusted to force the containers to wrap their content when possible. The grey tag box has been updated to ensure that long text wraps correctly within the screen boundaries on smaller displays. This prevents content from overflowing off-screen and ensures all text remains accessible when viewing article pages or search results on smartphones. Content boxes across the website have been updated to be fully responsive, eliminating the need for horizontal scrolling on smaller screens or when browser zoom is increased.
1.4.11 Non-text Contrast AA Supports All components like form fields and buttons, and graphics like pie charts and line graphs, have a minimum contrast ratio of 3:1. All publicly navigable forms and generic styling of the input fields have been adjusted to mitigate the contrast issues. Form field borders across Submit Manuscript, Login/Register, and Contact Us have been updated to increase contrast against both form backgrounds and page backgrounds.
1.4.12 Text Spacing AA Supports Users can increase letter, word, line, and paragraph spacing without cutting off content or breaking functionality. Ensuring users can make the text more readable while keeping the original page design and layout intact. The following are all supported for text throughout the website: • Line height (line spacing) to at least 1.5 times the font size; • Spacing following paragraphs to at least 2 times the font size; • Letter spacing (tracking) to at least 0.12 times the font size; • Word spacing to at least 0.16 times the font size. Text spacing across the majority of the website has been updated to meet minimum readability requirements. Content now reflows correctly when spacing adjustments are applied, ensuring text remains fully visible on screen.
1.4.13 Content on Hover or Focus AA Supports When new content appears, which has been triggered by hover or keyboard focus, such as tooltips, sub-menus, or pop- up, users are able to: • Dismiss it. • Interact with it, without it disappearing. • Have enough time to read or engage with it.
2.4.5 Multiple Ways AA Supports Header navigation is not the only way to get around a website; there are other ways, such as on-page links, a site- wide search, and consistent footer links
2.4.6 Headings and Labels AA Supports Headings are descriptive and effectively summarize sections of content. Form labels clearly describe what information is required. Buttons inform the user what will happen when they’re pressed.
2.4.7 Focus Visible AA Supports There is visible keyboard focus styling to indicate which element you’re currently focused on. This may take different forms, such as to visually change the button, place a cursor bar in the text field, our outline the element. The focus style of some buttons has been adjusted to increase the contrast.
2.4.11 Focus Not Obscured (Minimum) AA Supports All content receiving Keyboard focus is always at least partially visible on the user’s browser window, ensuring it is completely hidden by other content such as sticky headers, footers, or modals.
2.5.7 Dragging Movements AA Supports Any action requiring dragging, such as reordering items, is also possible using buttons or other non-drag methods. The drag-and-drop functionality of the file uploader is optional, and an equivalent non-drag method (file selection button) is provided. The uploader can be fully operated using keyboard interaction.
2.5.8 Target Size (Minimum) AA Supports Clickable elements, such as buttons, links, and icons, are at least 24 × 24 pixels in size. Interactive elements in line with text, such as sentences or paragraphs, are an exception, since the line height limits the size.
3.1.2 Language of Parts AA Supports All page content is in English and the correct language attributes applied in the HTML. There are no parts of the page that are in a different language to the page itself. The casing is fixed in all error messages present on the website - they now appear in sentence case (no longer ALL CAPS).
3.2.3 Consistent Navigation AA Supports Navigation is consistent from page to page, ensuring familiar features like menus, search bars, and skip-to-content buttons stay in the same place as they visit different pages across the site
3.2.4 Consistent Identification AA Supports Components that have the same functionality within the site are identified consistently throughout the website (they always look and work the same)
3.3.3 Error Suggestion AA Supports Helpful suggestions are provided to help users correct errors, and identify required fields that were not completed. This helps prevent incorrect data being submitted, users abandoning the form due to confusion and frustration about the information/format required. Validation error messages now appear next to the corresponding fields on the public forms.
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports Important forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending.
3.3.8 Accessible Authentication (Minimum) AA Supports Where reCAPTCHA puzzles are presented, there is an audio alternative authentication method in place.
4.1.3 Status Messages AA Supports Status messages like form errors, success pop-ups, and cookie policy acceptance, are communicated to assistive technologies, such as screen readers.
4.2.1 Usage without vision Where a visual mode of operation is provided, there is at least one mode of operation that does not require user vision. - Partially Supports The site can be perceived, operated, and understood by users without vision. Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5, 3.2.2, and 3.3.1.
4.2.2 Usage with limited vision Where a visual mode of operation is provided, there is at least one mode of operation that enables users to make use of limited vision. - Partially Supports The site can be perceived, operated, and understood, by users with limited vision. Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5, 3.2.2, and 3.3.1.
4.2.3 Usage without perception of colour Where a visual mode of operation is provided, there is at least one visual mode of operation that does not require user perception of colour. - Partially Supports The site can be perceived, operated, and understood, by users without perception of colour. Issues: • Refer to the WCAG table entries for 1.4.1, 3.3.1.
4.2.4 Usage without hearing Where there is an audible mode of operation, there is at least one mode of operation that does not require user hearing. - Partially Supports The site can be perceived, operated, and understood, by users without hearing. Issues: • Refer to the WCAG table entries for 1.2.2.
4.2.5 Usage with limited hearing Where there is an audible mode of operation, there is at least one mode of operation that enables uses to make use of limited hearing. - Partially Supports The site can be perceived, operated, and understood, by users with limited hearing. Issues: • Refer to the WCAG table entries for 1.2.2,
4.2.6 Usage with no or limited vocal capability Where speech or other vocal prompt is used for input, control, or operation, there is at least one mode of operation that does not require user speech. - Supports The site can be perceived, operated, and understood, by users with limited or no vocal capacity.
4.2.7 Usage with limited manipulation or strength Where a manual mode of operation is provided, there is at least one mode of operation that does not require fine motor control or simultaneous manual operations. - Supports The site can be perceived, operated, and understood, by users with limited manipulation or strength.
4.2.8 Usage with limited reach Where a manual mode of operation is provided, there is at least one mode of operation that is operable with limited reach and limited strength. - Supports The site can be perceived, operated, and understood, by users with limited reach and strength.
4.2.9 Minimize photosensitive seizure triggers Where there are visual modes of operation, there is at least one mode of operation that minimizes the potential for triggering photosensitive seizures. - Supports Flashing content does not exceed three flashes per second.
4.2.10 Usage with limited cognition, language or learning There are features that make the site simpler and easier to use by individuals with limited cognitive, language, and learning abilities. - Partially Supports The site can be perceived, operated, and understood, by users with limited cognitive, language, and learning abilities. Issues: • Refer to the WCAG table entries for 1.2.2, 1.2.3, 1.2.5, 3.2.2, and 3.3.1.
4.2.11 Privacy The privacy of users is maintained when using accessibility features, and to the same level of privacy experienced by other users. - Supports Important forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending.
7.1.1 Captioning playback Where videos have synchronized audio, they are able to display captions. Where closed captions are provided, the user is able to choose to display these. - Partially Supports Captions are provided for all prerecorded audio content. Where audio is a media alternative for text, it is clearly labelled as such. Issues: • Refer to the WCAG table entries for 1.2.2,
7.1.2 Captioning synchronization The mechanism to display captions preserves synchronization between the audio and the corresponding captions as follows. - Partially Supports Captions are provided within 100 milliseconds of the time stamp. Live captions within 100 milliseconds of the availability of the caption to the player. Issues: • Refer to the WCAG table entries for 1.2.2.
7.1.3 Preservation of captioning Where video with synchronized audio is transmitted, converted or recorded, the caption data is preserved to ensure it can be displayed as per 7.1.1 and 7.1.2. - Partially Supports As per 7.1.1 and 7.1.2
7.1.4 Captions characteristics The user can adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters. - Supports When videos are played in YouTube, the display options for captions can be changed by the user to meet their individual requirements. This includes font and background colours, font style, and size.
7.1.5 Spoken subtitles Video with synchronized audio, has a mode of operation to provide a spoken output of the captions. - Partially Supports Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5.
7.2.1 Audio description playback Video with synchronized audio, has a mechanism to select and play available audio description to the default audio channel. Where technologies do not have explicit and separate mechanisms for audio description, users can select and play several audio tracks. - Partially Supports Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5.
7.2.2 Audio description synchronization Synchronization between the audio/visual content and the corresponding audio description is preserved. - Partially Supports Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5.
7.2.3 Preservation of audio description Where video with synchronized audio is transmitted, converted or recorded, the audio description data is preserved to ensure it can be played as per 7.2.1 and 7.2.2. - Partially Supports Issues: • Refer to the WCAG table entries for 1.2.3, 1.2.5.
12.1.1 Accessibility and compatibility features Documentation lists and explains how to use the accessibility and compatibility features; includes guidance for features that are built- in features, and compatible with assistive technologies. - Supports Accessibility Statement for Dove Medical Press Contact Dove Medical Press Guidance for Editors Guidance for Authors
12.2.2 Information on accessibility and compatibility features Information on the accessibility and compatibility features are provided. - Supports Accessibility Statement for Dove Medical Press Contact Dove Medical Press Guidance for Editors Guidance for Authors
12.2.3 Effective communication Support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point. - Supports There is a "contact us" link in the persistent footer, this takes the user to the "make an enquiry" online form. Mailing addresses, phone numbers and an email address are available on the "our locations” tab.

Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.

Get told when this changes

This report is dated Not stated. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.

Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.