XClose

Accessibility

Menu

MyAppraisal accessibility statement

This accessibility statement applies to MyAppraisal.

MyAppraisal (https://ucl.csod.com/) is run by UCL and supplied by Cornerstone. We want as many people as possible to be able to use this website, which means that you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate the website using just a keyboard
  • navigate the website using speech recognition software
  • listen to most of the website using a screen reader

There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible. You can see a full list of issues we currently know about in the non-accessible content section of this statement:

  • Some elements are not keyboard accessible 
  • Some elements do not receive focus visibility 
  • There is no skip to content function 
  • Some images do not have meaningful alternative text 
  • Some pages do not have sufficient colour contrast 
  • Some elements do not have accessible names 
  • Links are not always clearly described 

Feedback and contact information

Please raise a MyServices ticket via MyServices if you have a MyAppraisal accessibility query including:

  • If you are experiencing issues with accessing information or using the website
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made. 

When you contact the MyAppraisal Team, there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline an potential timescales by which you can expect a reply.

We aim to respond to all contacts within 3-5 working days.

Reporting accessibility problems with this website

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.2 AA standards.

We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we're not meeting accessibility requirements, please contact us.

Read tips on contacting organisation about inaccessible websites.

Enforcement procedure

The 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 website's accessibility 

University College London is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Learning Management and Core Desktop App

The alt text for the 'Cornerstone' logo image in the Learning List is incorrectly announced as a "Logo" image on the 'Administration' page. This fails WCAG 1.1.1 Non-Text Content (A).

The alt text for the Cornerstone logo in the core app is incorrectly set to "logo redirecting to homepage" on the 'User' page. This fails WCAG 1.1.1 Non-Text Content (A).

The visually emphasized headings text 'Subject' available under the 'Tab bar' options in the Learning List is not defined under the heading tag. This fails WCAG 1.3.1 Info and Relationships (A).

The screen reader does not announce the visible labels of the "Parent", "Owner", and "Upload files" controls in the core app. This fails WCAG 1.3.1 Info and Relationships (A).

The focus moves to multiple blank elements after the 'Add Approver' button in the Learning List; upon pressing the arrow keys focus shifts to several blank elements and announces them as blank. This fails WCAG 1.3.2 Meaningful Sequence (A).

The use of colour alone indicates that "Terms, Privacy, and Cookies" are links, making it difficult to distinguish from regular text. This fails WCAG 1.4.1 Use of Colour (A).

The interactable 'Show me' button available just beside the 'BROWSE BY SUBJECT' button in the Learning List is not keyboard focusable, as they didn't appear upon keyboard focus and hence are not accessible. This fails WCAG 2.1.1 Keyboard (A).

The popup icon buttons beside the "Approver" and "Manager" controls in the core app are not focusable using the keyboard. This fails WCAG 2.1.1 Keyboard (A).

When the user tries to navigate forward from the comments edit field in the Learning List using the tab key, the keyboard focus is getting trapped the focus just remains and navigates in the edit field. This fails WCAG 2.1.2 No Keyboard Trap (A).

No descriptive title has been defined for all the web pages in the core app. This fails WCAG 2.4.2 Page Titled (A).

When navigating inside the 'Navigation Menu' section in the Learning List, the keyboard focus moves separately to the profile photo and the profile name link. This fails WCAG 2.4.3 Focus Order (A).

When the user closes the Cart panel in the core app, the focus is shifted to the top of the page instead of the triggered 'Cart' button. This fails WCAG 2.4.3 Focus Order (A).

When the focus is on the ‘Download CSV Template’ button in the Learning List, the visible label ‘Download CSV Template’ does not match the programmatic name. The screen reader announces it as ‘Download-sample-template’ button. This fails WCAG 2.5.3 Label in Name (A).

Errors related to incorrect date entries are not identified or displayed for the calendar field in the Learning List. This fails WCAG 3.3.1 Error Identification (A).

No visible label is provided for the 'Options' dropdown in the Learning List, leaving users without clear guidance on its purpose or function (especially after it's filled). This fails WCAG 3.3.2 Labels or Instructions (A).

JAWS announce the 'Previous' and 'Next' page as 'link' in the Learning List, lacking any descriptive text or label. This fails WCAG 4.1.2 Name, Role, Value (A).

The screen reader announces the "Add condition button" for both the "Delete User" and "Edit User" icon buttons in the core app, which is incorrect and misleading. This fails WCAG 4.1.2 Name, Role, Value (A).

The auto-complete attribute is not defined for the user-specific input field present on the 'Credit Card' page in the Learning List. This fails WCAG 1.3.5 Identify Input Purpose (AA).

The colour contrast ratio of the Green 'Approved' check box text in the Learning List does not have the minimum requirement. This fails WCAG 1.4.3 Contrast (Minimum) (A).

The blue link text "Privacy & Cookies" and "Terms" fails the minimum colour contrast requirements. This fails WCAG 1.4.3 Contrast (Minimum) (A).

When the browser is set to a zoom level of 200% in the Learning List, the page layout changes, and the 'Assign' button gets cut off. This prevents users from being able to interact with the 'Assign' button. This fails WCAG 1.4.4 Resize Text (AA).

When text is resized to 200%, the Cart Panel content in the core app is overlapped, due to this the users would not be able to access the content. This fails WCAG 1.4.4 Resize Text (AA).

When the page is resized to 320px width in the Learning List, the page does not reflow as expected, instead a horizontal scroll bar appears and users must scroll right to view the entire content of the page. This fails WCAG 1.4.10 Reflow (AA).

When the browser width is set to 320px, all the contents of the Cart Panel in the core app are overlapping with each other and controls like "USD" the currency button, and the "X" close button are truncated. This fails WCAG 1.4.10 Reflow (AA).

The contrast ratio of the focus outline for the 'Search Suggestions' list in the Learning List fails the minimum colour contrast requirement. This fails WCAG 1.4.11 Non-Text Contrast (AA).

The Close (X) button colour in the core app fails the minimum colour contrast requirements. This fails WCAG 1.4.11 Non-Text Contrast (AA).

When the user navigates to the 'Show Active Traders Control' button in the Learning List, the screen reader announces a 'Show Controls' button which does not provide sufficient context about the button. This fails WCAG 2.4.6 Headings and Labels (AA).

The "Search" button in the core app has a non-descriptive label. Upon focus, it is announced simply as "Search" by the screen reader, without indicating its specific function of searching for users. This fails WCAG 2.4.6 Headings and Labels (AA).

When the focus moves to the interactive controls in the Learning List, the focus outline for the multiple controls on the page are not visible to the users. This fails WCAG 2.4.7 Focus Visible (AA).

Users can only re-arrange the tiles by dragging them in the Learning List. This method is not accessible to users who rely on keyboard navigation or assistive technologies. This fails WCAG 2.5.7 Dragging Movements (AA).

The Search, Review offer letter, Review requisition request in the Universal Profile each perform a different function, but they are identified with same icons and have different accessible names thus leading to confusion for users relying on screen readers or other assistive technologies on the UP 8 and UP 9 merged page. This fails WCAG 3.2.4 Consistent Identification (AA).

After activating the search button in the Learning List, a loading icon or process visually appears, but JAWS does not announce the loading animation that appears on the screen. This fails WCAG 4.1.3 Status Messages (AA).

When the cart button is activated in the core app, there is no announcement of the loading status. This fails WCAG 4.1.3 Status Messages (AA).

Learning Management Android and iOS versions

Android

In the Playlist screen, the decorative image is focused and announced beside Sam Smith text. This fails WCAG 1.1.1 Non-text Content (A).

In the Home screen, the alt text is not descriptive for the ‘Cornerstone logo image’. This fails WCAG 1.1.1 Non-text Content (A).

There are several instances where the headings are not properly implemented in My Learning:  'My learning' visually looks like a heading, however it is not announced as such. This fails WCAG 1.3.1 Info and Relationships (A).

Complete information of the checklists present is not announced in the ‘Manage Checklists’ screen. This fails WCAG 1.3.1 Info and Relationships (A).

When the user navigates to the ‘Scan QR Code’ screen - The QR code is not focused by the screen reader. This fails WCAG 1.3.2 Meaningful Sequence (A).

Hidden content is focused and announced in the ‘Scan QR Code’ screen. This fails WCAG 1.3.2 Meaningful Sequence (A).

Colour is the only way to identify the selected tab of the app located at the bottom of the Home screen. This fails WCAG 1.4.1 Use of Colour (A).

The 'Read More' button on the 'Playlist' screen is not focusable or announced by TalkBack. Users relying on swipe navigation cannot access this button, making it inaccessible. This fails WCAG 2.1.1 Keyboard (A).

Incorrect focus order after Dropdown button in the ‘Search’ screen. This fails WCAG 2.4.3 Focus Order (A).

No permanent visible label is provided for the 'Search Learning' edit field in the ‘Search’ screen. This fails WCAG 3.3.2 Labels or Instructions (A).

Incorrect label is announced for the Back button in the ‘Search’ screen. This fails WCAG 4.1.2 Name, Role, Value (A).

The dialog role is not announced for the 'Sort By' popup on the 'My Learning' screen. TalkBack fails to announce any role for this popup. This fails WCAG 4.1.2 Name, Role, Value (A).

The users can access the app only in portrait mode as the app is not adapted to the Landscape view. This fails WCAG 1.3.4 Orientation (AA).

The red selected tab text 'Search' fails colour contrast in the ‘Search’ screen. This fails WCAG 1.4.3 Contrast (Minimum) (A).

Grey placeholder text 'Search learning' fails colour contrast ratio. This fails WCAG 1.4.3 Contrast (Minimum) (A).

The text in the Tab Bar and on-screen text (e.g., ‘Nothing here yet, try searching for learning terms’) does not resize when the user adjusts the text size settings on their Android device. This fails WCAG 1.4.4 Resize Text (AA).

The off-state toggle switch fails to meet the minimum colour contrast ratio requirements. This fails WCAG 1.4.11 Non-text Contrast (AA).

The grey border outline fails the colour contrast ratio in the ‘Scan QR Code’ screen. 

Loading status is not announced when the user activates the toggle switch on the Filters screen. This fails WCAG 4.1.3 Status Messages (AA).

iOS

Descriptive accessible name is not announced for the Profile image in the ‘Scan QR Code’ screen. This fails WCAG 1.1.1 Non-text Content (A).

The label 'Show only mobile Training' is not associated with the toggle button in the Settings screen. This fails WCAG 1.3.1 Info and Relationships (A).

The Interactive elements  Approve, Deny, Training requires approval...' buttons are not focused using swipe gestures in the ‘Notifications’ screen. This fails WCAG 2.1.1 Keyboard (A).

When the user navigates the Duration dialog, Focus is trapped in between the Close button and Duration heading in the ‘Search’ screen. This fails WCAG 2.1.2 No Keyboard Trap (A).

After activating the  'X' close button in the ‘Filter by training type’ pop-up the focus does not return to the triggered element in the  ‘My Learning’ screen. This fails WCAG 2.4.3 Focus Order (A).

Visual label does not match the programmatic name of the 'Goals’ control in the Home screen. This fails WCAG 2.5.3 Label in Name (A).

Role and selected state is not announced for the controls 'Active learning', 'Completed learning', and 'Archived learning' in the 'Filter by training status' popup. This fails WCAG 4.1.2 Name, Role, Value (A).

App content view is limited to one orientation in portrait mode, content view does not adjust to landscape mode after orientation change. This fails WCAG 1.3.4 Orientation (AA).

Orange text over white background fails the contrast ratio in the ‘Home’ screen. This fails WCAG 1.4.3 Contrast (Minimum) (A).

Some text does not resize when larger text is selected in the ‘Home’ screen. This fails WCAG 1.4.4 Resize Text (AA).

The grey ! icon button over white background fails contrast ratio in the ‘Downloads’ screen. This fails WCAG 1.4.11 Non-text Contrast (AA).

The multiple '...' button associated with the courses announces the same identical accessible name and without any reference context in the ‘Home’ screen. This fails WCAG 2.4.6 Headings and Labels (AA).

Search suggestions are not announced by the VoiceOver upon appearing in the ‘Search’ screen. This fails WCAG 4.1.3 Status Messages (AA).

When the User focuses on any one of the invalid QR codes, an error message 'No Cornerstone QR code detected' appears and is not announced in the ‘Scan QR Code’ screen. This fails WCAG 4.1.3 Status Messages (AA).

Cornerstone Elevate

At some instances the decorative image is focused and announced in the Admin Home Page Customization in the Performance EPM. This fails WCAG 1.1.1 Non-text Content (A).

The informative Resume image in the Applicant Profile does not have an alt attribute defined, resulting in screen readers not being able to describe the image to users. This fails WCAG 1.1.1 Non-text Content (A).

There are several instances in the Performance EPM where the table headers are not accessible for screen reader users and Unnecessary nested table rows are defined for cells in the User Competency Assessment Task Instructions page. This fails WCAG 1.3.1 Info and Relationships (A).

There are some instances where the visual table is not implemented with table semantics in the CareerSiteAdmin4 page of the career sites. This fails WCAG 1.3.1 Info and Relationships (A).

Visually appearing headings are not defined as such across the website for recruiting requirements and sourcing. This fails WCAG 1.3.1 Info and Relationships (A).

Multiple hidden elements (empty or non-visible elements) in the career sites are announced by screen readers when navigating using arrow keys in the Responsive CareerSite 4 - Change User Photo page. This fails WCAG 1.3.2 Meaningful Sequence (A).

There are some instances where the multiple hidden links and content are focused and announced in the table across the website for recruiting requirements and sourcing. This fails WCAG 1.3.2 Meaningful Sequence (A).

Errors are identified by colour only for the Add objective on the DevPlan-Development Plan>Create plan page in the Performance EPM. This fails WCAG 1.4.1 Use of Colour (A).

Colour is the only way to identify Share your CV link on the ‘View positions on a career site’ page of the career sites. This fails WCAG 1.4.1 Use of Colour (A).

There are some instances where the tooltip "?" is not keyboard focusable in the Requisition Requests page of the website for recruiting requirements and sourcing. This fails WCAG 2.1.1 Keyboard (A).

The back to top button is not focusable during KN navigation of the career sites. This fails WCAG 2.1.1 Keyboard (A).

When attempting to navigate the table using the Tab key in the website for recruitment requirements and sourcing, the keyboard focus becomes trapped or loops. Checkboxes such as 'Empower,' 'Great People,' 'Great Benefits,' and 'CSOD - My Career Site - Grow' are not accessible via the Tab key in the Edit postings page. This fails WCAG 2.1.2 No Keyboard Trap (A).

The success toast message disappears automatically in the DevPlan3-Development Plan>Create plan in the Performance EPM. This fails WCAG 2.2.1 Timing Adjustable (A).

In some instances, the "Skip to Main Content" link is missing on the View positions on the career sites. This fails WCAG 2.4.1 Bypass Blocks (A).

The page titles for some pages are not descriptive in the website for recruiting requirements and sourcing. It doesn't describe the purpose of the page. This fails WCAG 2.4.2 Page Titled (A).

Incorrect page title defined for the Competency Assessment Summary page in the Performance EPM. This fails WCAG 2.4.2 Page Titled (A).

Incorrect focus order after activating the calendar button in the Performance EPM, the keyboard focus is incorrectly shifted to the previous month button within the calendar. This fails WCAG 2.4.3 Focus Order (A).

There are some instances where the rating star function is not focusable or operable with a keyboard in the website for recruiting requirements and sourcing. This fails WCAG 2.4.3 Focus Order (A).

There are some instances that the focus order is incorrect after activating any controls across the career sites. This fails WCAG 2.4.3 Focus Order (A).

There are some instances where the visual label does not match with the programmatic label for the controls across the website in the Performance EPM. This fails WCAG 2.5.3 Label in Name (A).

The 'Search' button accessible name in the Performance EPM is announced as 'Please select search' which does not match the visible label in the DevPlan5 - Development Approval View page. This fails WCAG 2.5.3 Label in Name (A).

When the user submits the form with an empty field in the Performance EPM, the error message is available but is not descriptively announced in the DevPlan3 - Development Plan > Create plan. This fails WCAG 3.3.1 Error Identification (A).

There are some instances where the visual indication is not provided for the required field in the onboarding site. This fails WCAG 3.3.2 Labels or Instructions (A).

Visible label is not defined for 'Add Action Item' dropdown for the Configure an App in the career sites. This fails WCAG 3.3.2 Labels or Instructions (A).

The View link in all the Competency Assessments Tasks are announced with incorrect role as '<Task name>, View, button' in the Performance EPM. This fails WCAG 4.1.2 Name, Role, Value (A).

There are some instances in the Performance EPM where the incorrect accessible name is announced for the dropdowns in the website. This fails WCAG 4.1.2 Name, Role, Value (A).

The accessible label is not defined for the Search field in the CareerSiteAdmin4 page in the career sites. This fails WCAG 4.1.2 Name, Role, Value (A).

In some instances of career sites the autocomplete attribute is not defined for fields across the website. This fails WCAG 1.3.5 Identify Input Purpose (AA).

Auto complete attribute is set as false for all the input fields present on the 'Create a profile' page in the career sites. This fails WCAG 1.3.5 Identify Input Purpose (AA).

The yellow text 0% and orange text 30% fails contrast requirement with white background in Goals1 - My Goals page of the Performance EPM. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

When the 'Show me' button is hovered in the website for recruiting requirements and sourcing, the white text over grey background fails colour contrast. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

When the page is zoomed to 200% in the Performance EPM, the ‘Refer Jobs' tab content gets truncated due to this the users would not be able to access the content. This fails WCAG 1.4.4 Resize Text (AA).

When the page is zoomed to 200% in the website for recruiting requirements and sourcing, the user has to scroll both horizontally and vertically to access the entire content in many pages. This fails WCAG 1.4.4 Resize Text (AA).

The page content is not redistributed correctly to 320 x 256 px in the website for recruiting requirements and sourcing. The controls such as ‘13 Candidates’, ‘2 New submission’, ‘1 Background check’, etc. located below heading ‘Candidates’ are not available page zoom across multiple pages in the website. This fails WCAG 1.4.10 Reflow (AA).

When the page is resized to 320px width in the career sites, the 'Cancel' and 'Submit' buttons require two-dimensional scrolling to be accessed when the reflow is applied in Responsive CareerSite 11 - Launch Form page. This fails WCAG 1.4.10 Reflow (AA).

Green 'chevron right tick' button fails contrast ratio with white background in DevPlan5 - Development Approval View page in the Performance EPM. This fails WCAG 1.4.11 Non-text Contrast (AA).

Multiple button controls fail to contrast with the respective backgrounds in the Performance EPM website. This fails WCAG 1.4.11 Non-text Contrast (AA).

Black focus indicator fails to contrast with the blue background over the search button in the Admin Home Page Customization page of the Performance EPM website. This fails WCAG 1.4.11 Non-text Contrast (AA).

In some instances, when text spacing is applied, the content overlaps across multiple pages on the website for recruitment requirements and sourcing. This fails WCAG 1.4.12 Text Spacing (AA).

In some instances the tooltip content for Referral email button and warning content are not available for keyboard users in the website for recruitment requirements and sourcing. This fails WCAG 1.4.13 Content on Hover or Focus (AA).

Multiple button controls are announced without any context in the Performance EPM website. This fails WCAG 2.4.6 Headings and Labels (AA).

Non-descriptive names are announced for '<' and '>' buttons in the Create Onboarding Workflow page of the website for recruitment requirements and sourcing. This fails WCAG 2.4.6 Headings and Labels (AA).

Focus indicator is not visible for the multiple controls across the Performance EPM website. This fails WCAG 2.4.7 Focus Visible (AA).

Focus outline partially visible on the Email control in the Applicant Profile page of the website for recruitment requirements and sourcing. This fails WCAG 2.4.7 Focus Visible (AA).

Multiple '+' or '-' buttons does not have enough target size in the Enable/Disable Settings page of the career sites. This fails WCAG 2.5.8 Target Size (Minimum) (AA).

The language of parts is not identified for non-English content. For instance, the label of the checkbox '會計師-中文(req134)' is not announced by the screen reader in the Candidates page of the website for recruiting requirements and sourcing. This fails WCAG 3.1.2 Language of Parts (AA).

The loading status that appears when the "Save as draft" button is activated is not announced by JAWS in the Performance EPM. This fails WCAG 4.1.3 Status Messages (AA).

When the user enters some value in the ‘Search requisition’ edit field Presence and number of search results is not announced by JAWS in the website for recruitment requirements and sourcing. This fails WCAG 4.1.3 Status Messages (AA).

In some instances the error messages are not announced when displayed on the page across the website for reporting. This fails WCAG 4.1.3 Status Messages (AA).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

If you are unable to complete the MyAppraisal user journey, whether as an appraisee or appraiser, we have ensured that there is an alternative route to submitting appraisal information in the form of a Microsoft Word document. When you contact us we will send you a Microsoft Word document alternative that can be completed via email fully supported by the MyAppraisal team.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

This section covers issues that we do not need to fix right now. The law calls these exemptions.

Third-party content

Our websites may contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:

  • links to non-UCL websites
  • content/functionality on our website
  • content hosted on other websites, such as social media sites.

To help accessibility compliance across the sector, University College London supports searchBOX, a centralised, independent directory of third-party accessibility information. 

searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem. 

Users can access third-party accessibility statements using the free searchBOX Finder service. 

University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory. 

Our testing processes

We tested the website using a combination of manual and automated checks alongside reference to the accessibility audit report provided by the Digital Accessibility Centre (DAC) and the VPATs provided by Cornerstone.  If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the website owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated. 

Preparation of this accessibility statement

This statement was prepared on 25 January 2024. It was last reviewed on 10 February 2025.
This application was last tested on 23 December 2024. The test was carried out by Cornerstone and UCL.

What we’re doing to improve accessibility

University College London (UCL) are working closely with Cornerstone to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes.

If you are unable to complete the MyAppraisal user journey, whether as an appraisee or appraiser, we have ensured that there is an alternative route to submitting appraisal information in the form of a Microsoft Word document. When you contact us we will send you a Microsoft Word document alternative that can be completed via email fully supported by the MyAppraisal team.