Editor Resources
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 — 32 criteria
- Supports
- 17
- Partially supports
- 11
- Does not support
- 0
- Not applicable
- 4
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 14
- Partially supports
- 8
- Does not support
- 1
- Not applicable
- 0
- Not evaluated
- 1
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)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | All non-text content, on Editor Resources, that is presented to the user has a text alternative that serves the equivalent purpose. Third party issues - Go To Stage: • There is button below the video that receives keyboard focus and mouse hover focus, but has no visual or accessible label. When selected, it opens the “Register to watch now” form. Example: Your Account video. • To be raised with the vendor Q1 2026. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | There is no audio-only content, or video content without an audio track, on the site. |
| 1.2.2 | Captions (Prerecorded) | A | Partially Supports | Closed Captions are provided for all content hosted in YouTube. The captions can be customized to adjust text and background color, font type and size. Issues: • Captions are not available for content hosted on Go To Stage. • To be raised with the vendor Q1 2026. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Partially Supports | Videos hosted on YouTube offer an auto- generated standard timestamped transcript; the text being announced is presented in bold text with a light grey highlight. This has a contrast ratio of 15.55:1. Video training resources hosted on Go To Stage have a standard timestamped transcript; the text being announced is presented in bold text with a bright blue highlight. This has a contrast ratio of 5.52:1. Issues: • Audio description tracks and/or descriptive transcripts are not available. Further review of the content is required to confirm which videos would require this addition. • Review requirements Q1 2026. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Information, structure and relationships between content that is visual can be programmatically determined via HTML or ARIA; or are available by text. Issues: • 11 occurrences of the role=”listitem” for the “Join our team of academic editors” link is not inside the required context. Example: Events. • Remediation Q4 2025. |
| 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. Note: • External link icon incorrectly used – some go to internal site destinations, and some external links don’t have the icon at all (see 2.4.4 Link Purpose – in context). |
| 1.4.1 | Use of Color | A | Supports | Color is not the only visual means of conveying information, indicating and action, prompting a response, or distinguishing a visual element. |
| 1.4.2 | Audio Control | A | Supports | Videos hosted on YouTube do not automatically play. There is functionality to play/pause, adjust volume with option to mute, adjust playback speed and quality, view full-screen or picture-in- picture - which can both be closed by keyboard. Video training resources hosted on Go To Stage starts to play automatically upon completing the “Register to Watch Now” form. There is functionality to play/pause, adjust volume with option to mute, view full-screen or picture-in- picture - which can both be closed by keyboard. |
| 2.1.1 | Keyboard | A | Supports | All functionality is operable using the keyboard only. There are no specific timings to complete individual keystrokes. |
| 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 | Not Applicable | There are no keyboard shortcuts used throughout the site. |
| 2.2.1 | Timing Adjustable | A | Supports | There is no time limits set throughout the site. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | There is no moving, blinking, or scrolling information that (1) starts automatically (2) lasts more than five seconds (3) is presented alongside other content. There is no auto-updating information that (1) starts automatically (2) is presented alongside other content. |
| 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: • The Peer support zone page has two pieces of text that are not included in an ARIA landmark. • 11 pages need manually checking to confirm that the landmarks have unique names to differentiate them. Example: the Editor toolkit has four landmarks called “navigation”. • Remediation Q4 2025. |
| 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 | 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 | Partially Supports | A link’s destination is clear from either the link text itself or the surrounding sentence context. Issues: • 12 occurrences of links missing a text alternative. This affects the Home icon on the top navigation bar, and one image. Examples of both can be found on The benefits of joining a T&F journal as an Editor or Board member. • Four pages have two or more links in the same context that have the exact same link text. These need to be manually checked to confirm they go to the same destination. • External link icon incorrectly used – some go to internal site destinations, and some external links don’t have the icon at all. Example page: Policies & Guidelines (Accessibility, and Article types). • “Training for researchers” link is broken on the How to page. • Remediation Q4 2025. |
| 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 or drawing. This does not affect gestures built into device operating systems such as iOS and Android, or assistive technology. |
| 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 | Partially 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. Issues: • Home link has an icon of a house, and an accessible name of “home”. However, NVDA screen reader is not announcing “home”, it announces “editor resources dot taylor & franc”. • Remediation Q4 2025. |
| 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. 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. |
| 3.2.2 | On Input | A | Partially Supports | The Contact Us form, hosted on Author Services, includes a “I have a question about “ field, which requires users to select a topic from the drop-down. Once the topic is selected the form will dynamically show/hide fields. The changes are predictable, and relate to the user’s selection. Focus remains in the “I have a question about” field. Any data entered into other fields remains in place. Issues: • Users are not informed that selecting a topic from the “I have a question about “ drop-down will change the available fields. This should be included in text near the drop-down. • ARIA live regions should be used to announce changes to screen reader users. • Remediation Q4 2025. |
| 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 Us link in persistent top navigation bar. The page provides an email address for reviewer-related queries. Links are provided to externally hosted online contact forms for submission queries, and partnership enquiries. Editor Toolkit can be found under “The editor’s role”. How To guides are under “Welcome to T&F”. Issues: • The Contact Us page does not provide a telephone number. • The Contact Us page does not provide a link to frequently asked questions or Help Centre. • Training resources are found under Events – this is confusing. Recommend amending to “Events & Training” • Remediation Q1 2026. |
| 3.3.1 | Error Identification | A | Partially Supports | There are no forms on the Editor Resources Site, however users are directed to forms on other T&F websites, or third-party sites such as GoTo Webinar, GoTo Stage, and Zoom. The Contact Us form, hosted on Author Services, provides error messages upon submitting the form. They are in red text and announced to screen readers. Issues: • The contact us form has fields marked with an asterisk to indicate they must be completed, and are announced as “star edit required” to a screen reader. But there is no visual message at the start of the form to confirm that this symbol signifies a required field entry. • Remediation Q4 2025. |
| 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. |
| 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: • Two Categories buttons missing a text alternative. They appear to be blank generic buttons, which have remained focusable. This is occurring on two pages: 1. Engaged research and publication in the humanities 2. Peer support zone • Remediation Q4 2025. Note: • 12 occurrences of links missing a text alternative (see 2.4.4 Link Purpose in context). |
| 1.2.4 | Captions (Live) | AA | Supports | Live webinars delivered 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 panelist. When using automated captions, English is the default language, but you can select other languages. Live webinars delivered through GoTo Webinar, provide live closed captions via the participant control panel, as long as the organizer has enabled transcriptions for the session. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Evaluated | The dedicated audio description track narrates important visual elements that are not conveyed in the main audio track. This includes actions and movements, scene changes, on-screen text not read aloud, non-verbal expressions/gestures, visual context necessary for understanding. Issues: • Review of content is required to confirm which videos require the addition of audio description. • Review requirements Q1 2026. |
| 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 | There are no forms on the Editor Resources Site, however users are directed to forms on other T&F websites, or third-party sites such as GoTo Webinar, GoTo Stage, and Zoom. The purpose of their 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 | The visual presentation of body text and images of text has a ratio of at least 4.5:1. Large-scale text and images of large-scale text have a ratio of at least 3:1. Text that is part of a logo or brand name has no minimum contrast requirement. Issues - 70 occurrences of contrast not meeting the minimum ratio: • Editor details: white text on teal (448391). Ratio 4.28:1. Example: Editorial Advisory Board. • Lightbulb banner: teal text (35616A) on orange (F19500). Ratio 2.94:1. Example: Ethics for journal editors. • Journal and date information: light grey text (95989A) on white. Ratio 2.9:1. Example: Engaged research. • Reset filters link: teal text (448391) on white. Ratio 4.28:1. Example: Join our team. • Remediation Q4 2025. |
| 1.4.4 | Resize text | AA | 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. |
| 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 | Partially Supports | Content throughout the site is reflowable and responsive, remaining readable and usable without requiring horizontal scrolling for text or controls. Issues: • The social media banner (right-hand side) does not move as you either scroll or tab through the page. The Facebook icon remains visible, and as you Tab through the banner a screen reader announces “Facebook”, “X”, etc. But as it doesn’t move with the page, you cannot see the visual focus indicator on the other social media links within the banner. The focus indicator reappears once it reaches the first link in the main landmark. • Remediation Q1 2026. |
| 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. Issues: • Page number buttons: Active - white text on teal (539EAF). Ratio 3.05:1. Inactive - teal (448391). Ratio 4.28:1. Example: Peer support zone • Remediation Q4 2025. |
| 1.4.12 | Text Spacing | AA | Does Not Support | 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 are not 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. • Remediation Q1 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 breadcrumb links, on-page links, a site-wide search, and consistent footer links. |
| 2.4.6 | Headings and Labels | AA | Partially 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. Issues: • Five pages have one or more heading levels skipped. 1. Ethics for journal editors 2. Engaged research and publication in the humanities 3. The benefits of joining a T&F journal as an Editor or Board member 4. Editor toolkit 5. How to • Two pages have content missing after headings. 1. Events 2. Ethics for journal editors • Remediation Q4 2025. |
| 2.4.7 | Focus Visible | AA | Partially 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. Our training resource videos are hosted on Go To Stage. Their Register to Watch Form has visible focus. Field borders are blue when in focus for editing, they turn red if an error has been made. Issues: • 11 pages need manual checking to confirm that the “Skip to main content” link has a visible focus indicator - initial checks confirm this is in place. • Remediation Q1 2026. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | Most content receiving Keyboard focus is always at least partially visible on the user’s browser window, ensuring it is not completely hidden by other content such as sticky headers, footers, or modals. Issues: • The social media banner (right-hand side) does not move as you either scroll or tab through the page, causing the focus indicator to completely disappear from view when tabbing through the social media icons beyond Facebook. This makes it impossible for sighted keyboard users to track their position on the page. • Remediation Q1 2026. |
| 2.5.7 | Dragging Movements | AA | Supports | There is no author-created functionality within web content that requires dragging movements (such as drag-and-drop, sliders, custom scrollbars, sortable lists, or canvas drawing). This does not affect dragging movements built into device operating systems such as iOS and Android, assistive technologies, or browsers. |
| 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 | There are no parts of the page that are in a different language to the page itself. |
| 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 | There are no forms on the Editor Resources Site, however users are directed to forms on other T&F websites, or third-party sites such as GoTo Webinar, GoTo Stage, and Zoom. The forms checked provide 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 | Supports | There are no forms on the Editor Resources Site, however users are directed to forms on other T&F websites, or third-party sites such as GoTo Webinar, GoTo Stage, and Zoom. Form fields can be checked and edited before submission. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Partially Supports | The Contact Us form, via Author Services, has CAPTCHA puzzles. These can be completed with a visual or audio puzzle. Issues: • The audio CAPTCHA puzzle is not easy to understand, speech can be unclear. Is CAPTCHA needed? • Remediation Q4 2025. |
| 4.1.3 | Status Messages | AA | Partially Supports | Status messages like form errors, success pop-ups, and cookie policy acceptance, are communicated to assistive technologies, such as screen readers. Third party issues - Go To Stage • Error messages on forms are not announced by a screen reader. • To be raised with the vendor and remediation timescales confirmed Q1 2026. |
| 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: 1.1.1, 1.2.3, 1.3.1, 2.4.1, 2.4.4, 2.4.6, 3.2.2, 3.3.1, 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: 1.1.1, 1.2.3, 1.3.1, 1.4.3, 2.4.4, 2.4.6, 2.4.7, 3.2.2, 3.3.1, 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 color. Issues: • Refer to the WCAG table entries: 1.4.3, 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. 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: 1.1.1, 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. 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: 1.1.1, 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. 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: 2.4.1, 2.4.4, 2.4.6, 2.4.7, 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: 2.4.1, 2.4.4, 2.4.6, 2.4.7, 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. WCAG functional performance criteria: 2.3.1. | - | 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. 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: 1.1.1, 1.2.2, 1.2.3, 1.3.1, 2.4.1, 2.4.4, 2.4.6, 2.4.7, 3.2.2, 3.3.1, 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. WCAG functional performance criteria: 3.3.4. | - | 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. WCAG functional performance criteria: 1.2.2, 1.2.4. | - | 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: 1.2.2. |
| 7.1.2 | Captioning synchronization The mechanism to display captions preserves synchronization between the audio and the corresponding captions as follows. WCAG functional performance criteria: 1.2.2, 1.2.4. | - | 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: 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 above. |
| 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. | - | Not Evaluated | Further testing required to confirm that display options for captions can be changed by the user to meet their individual requirements. |
| 7.1.5 | Spoken subtitles Video with synchronized audio, has a mode of operation to provide a spoken output of the captions. WCAG: 1.2.1, 1.2.3, 1.2.5. | - | Partially Supports | Issues: • Refer to the WCAG table entries: 1.2.3. |
| 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. WCAG: 1.2.1, 1.2.3, 1.2.5. | - | Partially Supports | Issues: • Refer to the WCAG table entries: 1.2.3. |
| 7.2.2 | Audio description synchronization Synchronization between the audio/visual content and the corresponding audio description is preserved. WCAG: 1.2.1, 1.2.3, 1.2.5. | - | Partially Supports | Issues: • Refer to the WCAG table entries: 1.2.3. |
| 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. WCAG: 1.2.1, 1.2.3, 1.2.5. | - | Partially Supports | Issues: • Refer to the WCAG table entries: 1.2.3. |
| 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 Centre Frequently Asked Questions (via the Author Services site) |
| 12.2.2 | Information on accessibility and compatibility features Information on the accessibility and compatibility features are provided. | - | Supports | Accessibility statement How To Centre • Frequently Asked Questions (via the Author Services site) |
| 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 top navigation that includes a “Contact us” link the directs users to the Contact us (via the Author Services site) Issues: • Contact Us only offers an online form, there is no direct email or phone number provided to meet different communication needs. |
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.