F1000 (marketing site)
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.
Level A — 31 criteria
- Supports
- 17
- Partially supports
- 12
- Does not support
- 0
- Not applicable
- 2
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 16
- Partially supports
- 7
- Does not support
- 1
- Not applicable
- 0
- Not evaluated
- 0
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 (77)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Issues: • Resources for researchers: graphic for "What is open research?" needs to be marked as decorative. • Remediation Q3 2026. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | There is no audio-only content on the site. There is no video content without an audio track on the site. |
| 1.2.2 | Captions (Prerecorded) | A | Partially Supports | Closed captions are provided for prerecorded audio content. For YouTube embedded content the caption font style can be changed to meet user preferences. Except where the video was specifically created to be an alternative format for text content that already exists on the page, and the video is clearly labelled as such. Issues: • T&F Wistia: captions are not available for content hosted in T&F Wistia. This content will be moved to YouTube, which has the functionality to add captions. Example: Blog - Open data essentials for research managers and administrators: What, why and how of open data. • Remediation Q3 2026. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Partially Supports | Standard, time-stamped transcripts are available for videos watched via YouTube. Timestamps can be toggled on/off. Issues: • T&F Wistia: standard transcripts are not available for content hosted in T&F Wistia. This content will be moved to YouTube. Example: Blog - Open data essentials for research managers and administrators: What, why and how of open data. • Remediation Q4 2026. |
| 1.3.1 | Info and Relationships | A | Partially 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. Issues: • Container element is empty: across three pages there are five empty containers, used to generate blank lines within content blocks. The elements are marked as role="list" which is a parent role. However, they do not contain a required child role group or listitem element. • Remediation Q3 2026. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | The order of content in the website's code mostly 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. Issues: • Secondary navigation menu (Terms, Cookies): when the browser zoom is set to 150%+, this becomes a burger menu. Whilst this can be reached by keyboard, the order of engagement is not a good user experience - Tabbing an excessive number of times to reach the two list items in the expanded menu. The list items cannot be reached using NVDA keyboard shortcuts either, such as 'K' for links. • Remediation Q3 2026. |
| 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 Colour | A | Partially Supports | Colour is not the only visual means of conveying information, indicating and action, prompting a response, or distinguishing a visual element. Issues: • Form field level error messages: no supporting visual indicator, rely on red colour alone to present error information. Contact Us, Open Research Services, and Resources for Researchers. • Top of form error message: no supporting visual indicator, relies on red colour alone to present error information. Resources for Researchers. • Remediation Q2 2026. |
| 1.4.2 | Audio Control | A | Supports | No audio-only or video content plays automatically; whether hosted on YouTube or T&F Wistia. Content can be paused/stopped, volume can be controlled independently from the overall system volume level, playback speed and quality are adjustable. |
| 2.1.1 | Keyboard | A | Supports | All functionality is operable using the keyboard only. There are no specific timings to complete individual keystrokes. Note: • See 1.3.2 Meaningful Sequence. |
| 2.1.2 | No Keyboard Trap | A | Supports | There are no situations where you enter a modal with the keyboard and can’t 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 | Supports | There are no keyboard shortcuts used on this site. |
| 2.2.1 | Timing Adjustable | A | Supports | Where time limits cannot be avoided, they can be: • Turned off before encountering it. • Adjusted before encountering it, to at least ten times the length of the default setting. • Extended, and the user is warned before time expires, and is given at least 20 seconds to extend using a simple action. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Carousel blocks do not scroll automatically – users must use the next/previous buttons to navigate the carousel banners. For most video content, users are directed to the main site think.f1000.com to watch the embedded YouTube video. Webinar videos on this site do not auto-play, and have play/pause/stop functionality. They can be watched via the embedded video, or directly on YouTube. Issues: • Moving patterned background: The background of grey circles moves when scrolling up and down the page – this can affect visual processing, cause cognitive exhaustion, and can affect colour contrast. Examples: Contact Us, Webinars, Publishing Venue, and Open Access. • Remediation Q3 2026. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | There is no flashing content on the site. |
| 2.4.1 | Bypass Blocks | A | Partially 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. Issues: • Footer and Breadcrumb landmarks: there are three landmarks with the same name, "Navigation LM" (breadcrumb, footer links, social media). They need to be uniquely named, so users clearly know what each one is for. • Remediation Q4 2026. Best practice issues: • Page region missing an accessible name: five pages display carousel blocks with the role of "region". Their landmarks are named "Region LM" and have not been assigned accessible names. • Remediation Q4 2026. |
| 2.4.2 | Page Titled | A | Supports | Each page has a unique title element that describes what’s on that page, to lets users know where they are and what type of content to expect. |
| 2.4.3 | Focus Order | A | Partially 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. Issues: • Secondary navigation menu (Terms, Cookies): when the browser zoom is set to 150%+, this becomes a burger menu. Whilst this can be reached by keyboard, the order of engagement is not a good user experience - Tabbing an excessive number of times to reach the two list items in the expanded menu. The list items cannot be reached using NVDA keyboard shortcuts either, such as 'K' for links. • Remediation Q3 2026. • Webinar videos: the Tab Stops to navigate the video listings do not consistently go left to right down the page. Some videos include a Tab Stop on both the video thumbnail and button, others just the button. • Remediation Q2 2026. |
| 2.5.1 | Pointer Gestures | A | Supports | There are no author-created gestures within the web content that require actions to be carried out using a gesture (swiping, pinching, and so on) or drawing. 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 | Supports | 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-GB). |
| 3.2.1 | On Focus | A | Supports | When a user interface component receives focus, it does not initiate unexpected changes. Note: • See 1.4.11 Non-text contrast. |
| 3.2.2 | On Input | A | Supports | There are no unexpected changes of context on user input. |
| 3.2.6 | Consistent Help | A | Partially Supports | The placement of help details and options is consistent across the site and easy to find. Contact details, online contact form, self-help FAQs, chatbots. Issues: • Contact Us: does not provide alternative contact methods (email, phone, chatbot) to meet different user communication needs. • Remediation Q4 2026. |
| 3.3.1 | Error Identification | A | Supports | Errors are automatically detected and clearly indicated and described to the user. Error messages are provided as text and announced for assistive devices. Note: • Forms need to be reviewed and presented consistently across the site. • Error messages are usually displayed inline, below the related field. One form has the error message placement above the field – this may be confusing, as expectation is that it would then relate to the field above, which it doesn’t. Example: Resources for Researchers. See 3.2.4 Consistent Identification for remediation details. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Help is provided to prevent form errors – sometimes the label is enough on its own, elsewhere additional hint text or instructions are provided. Form issues – to be reviewed and forms across the site to be consistent: • Asterisks: where these are provided at form field level, to mark fields that require completion, there is no message at the top of the form to confirm their meaning to users. Examples: Contact Us, Resources for Researchers. • No visual indicator for required fields: announced to screen readers as "required", but have no upfront visual indicator for sighted and low vision users. They only know it's required once an error message appears. Example: Open Research Services. • Remediation Q3 2026. |
| 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 | Partially Supports | All user interface elements and components have the right names, roles, states, properties and values so they’re recognized correctly by assistive technologies. Issues: • Hidden element has focusable content: Three pages contain parts hidden from view for users who rely on assistive technologies like screen readers, but these hidden sections still contain buttons or links that can be selected. This creates confusion because users may encounter interactive elements that seem to appear out of nowhere, disrupting their navigation and making it harder to use the site. 1) Resources for researchers (carousel) 2) F1000 Research (carousel) 3) Article Types (collapse/expand buttons) • Remediation Q2 2026. |
| 1.2.4 | Captions (Live) | AA | Supports | Live webinars are not delivered via the site. Users can sign-up to a monthly newsletter to learn about upcoming events. Live webinars delivered by the service, through Zoom, provide options for manual captioning, automated captions, or using a third-party captioning service. By default, captions can be enabled and viewed by any participant. Read Zoom’s guidance on how to view captions. When using manual captions, they are provided by either the host, co-host, or a panellist. When using automated captions, English is the default language, but you can select other languages. Live webinars delivered by the service, through GoTo Webinar, provide live closed captions via the participant control panel, if the organizer has enabled transcriptions for the session. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Does Not Support | Audio description is not provided for pre- recorded video content. Note: • Review of video content is required to ensure visual content, has all their meaningful visual information available as a separate audio description track (actions, descriptions, and other essential visual information not conveyed through the original audio track). |
| 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. |
| 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. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Some 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. Issues: • Colour contrast does not meet minimum requirement: 11 pages (73 occurrences) with text and background contrast ratio below 4.5:1. The occurrences range from 1.48:1 to 4.36:1. This affects the breadcrumb navigation, links in body copy, carousel call to action buttons, and privacy policy link. • Blog category banners: grey text against a dark multi-colour background. Ratio ranges from 1:1 to 4.4:1. Parts of the text are impossible to read. Examples: Researchers, Research Institutions. • Remediation Q2 2026. |
| 1.4.4 | Resize text | AA | Partially Supports | Text on a 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. Issues: • Secondary navigation menu (Terms, Cookies): when the browser zoom is set to 150%+, this becomes a burger menu. Whilst this can be reached by keyboard, the order of engagement is not a good user experience - Tabbing an excessive number of times to reach the two list items in the expanded menu. The list items cannot be reached using NVDA keyboard shortcuts either, such as 'K' for links. • Remediation Q3 2026. |
| 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). |
| 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. Note: • About Us - Our Story So Far: the carousel block becomes difficult to read when the text is enlarged. See 1.4.10 for details. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Usable components like form fields and buttons, and graphics like pie charts and line graphs, have a minimum contrast ratio of 3:1. Form issues - colours to be reviewed and forms across the site to be consistent: • Subscribe Now button: poor contrast when it receives keyboard focus (dark blue text on dark green). Example: Resources for Researchers. • Remediation Q2 2026. |
| 1.4.12 | Text Spacing | AA | Partially 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. Issues: The following text parameters are to be reviewed and confirm they are met throughout the site: 1) Line height (line spacing) to at least 1.5 times the font size; 2) Spacing following paragraphs to at least 2 times the font size; 3) Letter spacing (tracking) to at least 0.12 times the font size; 4) Word spacing to at least 0.16 times the font size. • Remediation Q3 2026. |
| 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, breadcrumb navigation, 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. |
| 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 | There are no actions that require dragging; such as reordering items. |
| 2.5.8 | Target Size (Minimum) | AA | Partially Supports | Most 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. Issues: • Research Archives: has six buttons that are 22px high. • Remediation Q4 2026. |
| 3.1.2 | Language of Parts | AA | Supports | Any parts of the page that are in a different language to the page itself are marked up with the appropriate lang value, so that assistive technology can detect and announce language changes to users. |
| 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 | Partially Supports | Components that have the same functionality within the site are identified consistently throughout the website (they always look and work the same). Form issues - need to be reviewed and presented consistently across the site. • Error messages are usually displayed inline, below the related field. One form has the error message placement above the field – this may be confusing, as expectation is that it would then relate to the field above, which it doesn’t. Example: Resources for Researchers. • Remediation Q4 2026. |
| 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. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Partially Supports | Important forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending. Forms issues - need to be reviewed and presented consistently across the site. • Subscribe opt-in: users are asked to agree to receiving marketing communications without clear access to the Privacy Policy, which could lead to uninformed consent. Example: Open Research Services, and Resources for Researchers. • Remediation Q2 2026. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Authentication is possible without cognitive challenges. |
| 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. WCAG functional performance criteria: 1.1.1, 1.2.1, 1.2.3, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.2, 2.1.1, 2.1.2, 2.2.1, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.1, 3.3.3, 3.3.4, 4.1.1, 4.1.2. | - | Partially Supports | The site can be perceived, operated, and understood by users without vision. Issues: • Refer to the WCAG table entries for 1.1.1, 1.2.3, 1.2.5, 1.3.1, 1.3.2, 1.4.1, 2.4.1, 2.4.3, 2.4.4, 3.2.4, 3.3.4, 4.1.2. |
| 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. WCAG functional performance criteria: 1.1.1, 1.2.1, 1.2.3, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.3, 1.4.4, 1.4.5, 2.1.1, 2.1.2, 2.2.1, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 4.1.2. | - | Partially Supports | The site can be perceived, operated, and understood, by users with limited vision. Issues: • Refer to the WCAG table entries for 1.1.1, 1.2.3, 1.2.5, 1.3.1, 1.3.2, 1.4.1, 1.4.3, 1.4.4, 2.4.1, 2.4.3, 2.4.4, 3.2.4, 3.3.2, 3.3.4, 4.1.2. |
| 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. WCAG functional performance criteria: 1.4.1, 1.4.3, 3.3.1, 3.3.4. | - | 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, 1.4.3, 3.3.4. |
| 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. WCAG functional performance criteria: 1.1.1, 1.2.1, 1.2.2, 1.2.4, 1.3.3, 3.1.1, 3.1.2, 3.3.4. | - | Partially Supports | The site can be perceived, operated, and understood, by users without hearing. Issues: • Refer to the WCAG table entries for 1.1.1, 1.2.2, 3.3.4. |
| 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. WCAG functional performance criteria: 1.1.1, 1.2.1, 1.2.2, 1.2.4, 1.3.3 1.4.2, 3.1.1, 3.1.2, 3.3.4. | - | Partially Supports | The site can be perceived, operated, and understood, by users with limited hearing. Issues: • Refer to the WCAG table entries for 1.1.1, 1.2.2, 3.3.4. |
| 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. WCAG functional performance criteria: n/a | - | Supports | The site can be perceived, operated, and understood, by users without speech. |
| 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. WCAG functional performance criteria: 2.1.1, 2.2.1, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 3.2.1, 3.2.4, 3.3.3, 3.3.4, 4.1.1, 4.1.2. | - | Partially Supports | The site can be perceived, operated, and understood, by users with limited manipulation. Issues: • Refer to the WCAG table entries for 2.2.2, 2.4.1, 2.4.3, 2.4.4, 3.2.4, 3.3.4, 4.1.2. |
| 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. WCAG functional performance criteria: 2.1.1, 2.2.1, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 3.2.1, 3.2.4, 3.3.3, 3.3.4, 4.1.1, 4.1.2. | - | Partially Supports | The site can be perceived, operated, and understood, by users with limited reach and strength. Issues: • Refer to the WCAG table entries for 2.2.2, 2.4.1, 2.4.3, 2.4.4, 3.2.4, 3.3.4, 4.1.2. |
| 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 | There is no flashing content on the site. |
| 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. WCAG functional performance criteria: 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.2, 1.4.5, 2.1.1, 2.2.1, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 4.1.1, 4.1.2. | - | 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.1.1, 1.2.2, 1.2.3, 1.2.5, 1.3.1, 1.3.2, 1.4.1, 2.2.2, 2.4.1, 2.4.3, 2.4.4, 3.2.4, 3.3.2, 3.3.4, 4.1.2. |
| 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. | - | Partially Supports | Important forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending. Issues: • Refer to the WCAG table entries for 3.3.4. |
| 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. | - | Partially Supports | Display options for captions can be changed by the user to meet their individual requirements. See WCAG 1.2.2 and 1.2.5 for further details. Issues: • Refer to the WCAG table entries for 1.2.2. |
| 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.2, 1.2.3 and 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.2, 1.2.3 and 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.2, 1.2.3 and 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.2, 1.2.3 and 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 How to make your research accessible - Author Services Resources for Researchers | Unlock every aspect of open research |
| 12.2.2 | Information on accessibility and compatibility features Information on the accessibility and compatibility features are provided. | - | Supports | Accessibility Statement How to make your research accessible - Author Services Resources for Researchers | Unlock every aspect of open research |
| 12.2.3 | Effective communication Support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point. | - | Partially Supports | This website contains a consistent header that includes a “Contact us” section. Issues: • Contact Us: does not provide alternative contact methods (email, phone, chatbot) to meet different user communication needs. • Remediation Q4 2026. |
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.