Last Updated 01/07/22This accessibility statement applies to the myday platform including web and mobile experiences. The platform is developed by Collabco Ltd, and we want everyone who uses it to feel welcome, and find the experience rewarding.myday is designed to be fully customisable, giving organisations and end users the ability to tailor it to their needs. We work to ensure that myday meets all of the functional requirements outlined in WCAG 2.1 Level AA out of the box. For example, that means you should be able to:change colours, contrast levels and fonts utilising an external accessibility tool zoom in up to 200% without the text spilling off the screennavigate most of the platform using just a keyboardlisten to most of the platform using a screen reader We strongly advise that any changes that are made by our customers should follow the Web Content Accessibility Guidelines (WCAG) 2.1 when customising any instance of myday. This will ensure that your version of the platform remains as inclusive as possible.How accessible this platform isWe know some parts of this platform are not fully accessible:Any media or embedded content that is provided to myday end users via a third party e.g. YouTube, Vimeo, external websites etc. We cannot control the accessibility of features or content that an organisation chooses to supply to their end users that has not been created by Collabco.Analytics dashboards are rendered using Microsoft Power BI which has accessibility issues beyond our control. This is only available for administrators and not applicable to all users. Functionality with known accessibility issues that are yet to be addressed, and which are detailed in our accessibility roadmap below e.g. some administration areas and less frequently used features.Customer ResponsibilityCaptions (Live), Audio Description (Pre-recorded) & Audio ControlThe customer is responsible for providing accessible alternatives to any media or embedded content that is provided to myday end users via a third party e.g. YouTube, Vimeo, external websites etc. We cannot control the accessibility of features or content that an organisation chooses to supply to their end users that has not been created by Collabco.Contrast (Minimum) & Non-text Contrastmyday is designed with WCAG 2.1 accessibility standards being adhered to and is supplied with WCAG 2.1 compliant colour combinations. myday is a customisable platform which may be changed by both administrators and end users. We advise that good judgement is used when selecting colour combinations.Images of Textmyday is a customisable platform, as such the content can be modified in an instance by any user with the appropriate administration rights. We ask any users that have the ability to add or edit such content to use good judgement. Please avoid using text as an image to convey information other than where it is essential to the image e.g. brand logos etc.Feedback and contact informationIf you need information on this platform and the accessibility contact us viaSupport Desk - https://collabco-jira.atlassian.net/servicedesk/customer/portalsPhone -  0800 048 9515Email - info@collabco.comReporting accessibility problemsWe’re always looking to improve the accessibility of myday. If you find any problems that are not listed on this page, or think we’re not meeting accessibility requirements, contact us through the support desk.Enforcement procedureThe Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).Technical information about this platform’s accessibilityCollabco Ltd is committed to making its platform accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.Compliance statusThis platform is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.Non-accessible contentThe content listed below is non-accessible for the following reasons.Non-compliance with the accessibility regulationsAppsThe following ‘apps’ have not currently been reviewed and therefore are likely to be only partially compliant to WCAG 2.1 success criterion. Evasys LabStatsLibraryStudent Information DeskMy BookmarksHelpdeskI Want ToMy AlertsWe plan to review and resolve these as part of rolling accessibility enhancements, as detailed further down in the statement. AdministrationThe following myday administration areas have not currently been reviewed and therefore are likely to be only partially compliant to WCAG 2.1 success criterion.Dashboard settingsTile settingsApp settingsThemes & BrandingTranslationsLanding page rulesCMS AdministrationWe plan to review and resolve these as part of rolling accessibility enhancements, as detailed further down in the statement. OtherThe date picker is partially compliant to WCAG2.1 success criterion, We plan to review and resolve these as part of rolling accessibility enhancements, as detailed further down in the statement. Findings from auditBetween the dates of 27th July - 7th August 2020, we commissioned an external audit. A number of issues were identified by the audit that pose a disproportionate burden and will be identified in the next section of this statement. The details of the individual issues can be found in the full accessibility test report. DIG AA - Collabco myday (Full report).pdfApproach to review and rectificationFrom January 2021 we have commenced a new approach to accessibility enhancements; breaking the platform into sections (listed below), and addressing multiple accessibility issues identified in the audit in one area at a time.This means that a whole section of the platform can be reviewed against multiple accessibility criteria, rather than addressing one issue across multiple areas of the myday. Therefore compliance to the accessibility guidelines can be maximised in the priority platform areas first.To ensure the areas of myday that are most likely to be used by persons with accessibility needs are addressed first, we are prioritising our most heavily utilised functionality for review.The list of platform areas will be continued to be worked on until all have been reviewed. Improvements will be released monthly and will be accompanied by release notes. This statement will be revised as the area has been addressed in order to make clear the areas of the platform that have been reviewed inline with the below checklist. Please note areas that are not listed in the Non-compliance with the accessibility regulations section above will have already had significant improvement as part of the releases that took place in 2020 as detailed in the Accessibility Roadmap. Platform AreasPlatform AreaReviewed and Rectified1Top Bar & Side Bar25/03/20212Dashboard - Settings, Layout, Personalise29/04/202127/05/20213Mobile App4Calendar App & Tile27/05/20215Courses App & Tile29/07/20216Banner App & Tile7Newsroom App & Tile8Mail App & Tile9Content App & Tile10Tasks App & Tile29/10/202111Maps App & Tile12Attendance Capture App & Tile13Attendance & Attendance 2 App & Tile14Balance App & Tile15Student Information App & Tile16Library App & Tile17PC Availability App & Tile18Labstats App & Tile19Facebook App & Tile20Twitter App & Tile21Static App & Tile22Gmail App & Tile23My Bookmarks App & Tile24People App & Tile25People Search App & Tile26Primo Search App & Tile27EvaSys App & Tile28Helpdesk App & Tile29I Want To App & Tile30SID Critical FAQ App & Tile31Student Information Desk App & Tile32UniWellBeing App & Tile33Video App & Tile34Feedback35My Alerts App (Bradford specific)36Content Management Admin Areas37User Management38Identity Management App & Tile39Azure AD Sync40OAuth Management41Look & Feel42Data43Landing Page rules44Adhoc Alerts45Links46Translations47Media48FeaturesChecklist Below is the detail of the checklist that we will be using in each area of the platform that is reviewed. PerceivableInformation and user interface components must be presentable to users in ways they can perceive.[1] - Non-text content must have alternatives (https://www.w3.org/WAI/WCAG21/Techniques/general/G94.html)(For our purposes, crossover with colour must have alternatives [1.4.1]). Having alternatives for text ensures that all users can access content. Historically areas in myday, have used different colours to represent a state such as success, warning and erroneous. This could be seen in areas such as admin feedback and newsroom manage subscriptions. Here we must provide alternatives. Approaches include:Using aria-labels to provide more contextUsing aria-labelledby and aria-describedbyProviding alt tags for images were needed (icons within myday are hidden to screen-readers by default as they do not provide any useful information and are used for decorative purposes).Using badges for items which would only be displayed using colourmyday example: Newsroom subscriptions page using a yellow corner to indicate mandatory feeds. Button with recycle bin in mail app, has no aria-label to indicate it means delete as icons aren't seen by a screen reader[2] Colour contrast of text (4.5 : 1) and components / ui elements (3:1) must be WCAG compliant.myday example: Colour contrast of progress and graph element with the attendance tile must have correct colour compliance.myday example: Administration > Dashboard > Dashboard settings. UI elements (buttons) must have a colour contrast of 3:1.OperableUser interface components and navigation must be operable.[3] - Content that should be keyboard accessible… must be keyboard accessible and focus should be visible. Within areas of myday, we use components such as uib-dropdowns which have the built in ability for this to be added. Other areas may be out of scope such as allowing users to move tiles with arrows keys.myday example: Course dropdown in the attendance2 app. A user should be able to use arrow keys[4] - No keyboard traps. Ensure users cannot be trapped within content.myday example: When using modals (example create a content page), a user could become trapped trying to exit an input field as pressing esc also closes the modal[5] - Bypass blocksA mechanism is available to bypass blocks of content that are repeated on multiple Web pages.Approaches include:Having links to ‘Skip to Main content’.Use aria landmarks with the code to group elementsProviding meaningful headers on different sections of different pages.Items such as bypass blocks will be much easier to achieve if code is semantically correct and follows best practices of code implementation. This point is further aided by pages having a familiar layout which has a logical focus order.myday example: Skip to main content and skip sidebar have been implemented.UnderstandableInformation and the operation of the user interface must be understandable.[6] - Input assistance. Under this point there a few things to be aware of:Error identification (error messages must be clear and be easily relatable to input fields which have an error)Labels or instructions (Input fields must have relatable labels and instructions)Error suggestionInput assistance will be also be easier to achieve with semantically correct code and correct decisions being made in terms of what input is being used. Inputs used should always be appropriate for the input type. i.e. type=”number” for a number.myday example: Input validation messages in mail app not being relatable to fields easilyRobustContent must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies[7] - Code is semantically correct and has correct regions, roles and names. We should not be using things like paragraphs for headers of pages, if a layout looks like it contains a list, it should be marked up as a list.myday example: Paragraphs being used as headers previously in User Management app[8] - Status messagesMessages, errors and warnings appearing in toast messages must be read out to a screen reader without requiring focus by a user.myday example: Toast messages with errors when submitting formsBy changing the approach we can focus on one area at a time and make that compliant, this way a release will be easier to describe, easier for you, our customers, to understand and mean that we can focus on the most used areas of the platform first.Disproportionate burdenmyday Legacy Control PanelOur strategy is to replace the functionality in the Control Panel with new admin apps provided through the dashboard platform.myday Legacy Platform "(V2)"Our strategy is to move customers to the new myday platform.Items identified in AuditIssueNotesDIG003: Link images do not describe the destination page (High) 17Due to disproportionate cost/Outside of our control - component provided by TPDIG003: Link images do not describe the destination page Outside of our control - component provided by TPDIG104: Video with an audio track does not have an audio description (High) 22Outside of our control - component provided by TPDIG1701: There is an unpredictable change of context when a component receives focusOutside of our control - component provided by TPDIG2103: A non-essential path-based gesture must be used to interact with a featureOutside of our control - component provided by TPDIG233: Tabular data does not read correctlyOutside of our control - component provided by TPDIG501: User need a specific sensory ability to interact with content Outside of our control - component provided by TPDIG804: Content is causing a keyboard trap (Critical) 118When relating this to PowerBI we deem this Outside of our control - component provided by TPDIG810: Keyboard shortcuts cannot be remapped (High) 122Outside of our control - component provided by TPWe have assessed the cost of fixing the above issues. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment in 12 months.What we’re doing to improve accessibilityOur accessibility roadmap alongside this statement shows how and when we plan to improve accessibility on myday.Preparation of this accessibility statementThis statement was prepared on 17 August 2020. It was last reviewed on 10 March 2021The platform was last tested on 11th August. The test was carried out by Dig Inclusion.You can read the full accessibility test report DIG AA - Collabco myday (Full report).pdf