FeedbackFruits Pilot

We are currently reviewing the ways in which learning technologies can help with your peer assessed teaching activities. FeedbackFruits is one example of a technology, used by a number of universities, that works closely with the virtual learning environment to help you run, and your students experience, these valuable teaching activities. We are offering a pilot to trial FeedbackFruits during semester 1 of academic year 2026-27 (AY26/27).

Important Note on Institutional Commitment: 

Unfortunately, we cannot guarantee access to Feedback Fruits beyond semester 1 of AY26/27. However, by taking part in this pilot you will have the opportunity to feed into a larger piece of work considering institutional investment in peer assessment technologies.


Although peer assessment can take many forms, this pilot will focus on three approaches:

  • Peer review: asks students to review, and provide feedback on, assignments that have been submitted by peers, either individually or collectively in groups. Students can more easily engage with a broader range of perspectives on the topic you are teaching whilst developing a deeper understanding of the assessment process.
  • Group member evaluation: enables students who are doing group assignments to evaluate the contribution their peers made towards the final piece of group work. In this way students receive an individual mark, and feedback, derived from the overall group mark and moderated by their peers. This activity can help with some of the more problematic motivational aspects of group work.
  • Group formation: will help teachers to form student groups for teaching activities based on customisable criteria.

If you have questions, please contact LearnFoundations@ed.ac.uk  

Application accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 

This accessibility statement applies to the teacher side of the FeedbackFruits Learn Ultra integration. 

This application is run by the University of Edinburgh. It uses the third-party system FeedbackFruits. FeedbackFruits has been developed by FeedbackFruits, and is available to teaching staff on the Learn Ultra platform’s content market. Once the FeedbackFruits integration has been added to a course, staff members interacting with this integration will be presented with the teacher interface. 

We want as many people as possible to be able to use this application. For example, that means you should be able to: 

  • Navigate most of the application using VoiceOver and TalkBack. 
  • Use the application without encountering any cognitive function tests. 
  • Use the application without encountering any inactivity timeouts. 

We’ve also made the application text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means. 

Customising the application 

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible: 

AbilityNet - My Computer My Way 

With a few simple steps you can customise the appearance of our application using your browser settings to make it easier to read and navigate: 

Additional information on how to customise our application appearance 

If you are a member of University staff or a student, you can use the free SensusAccess accessible document conversion service: 

Information on SensusAccess 

How accessible this application is 

We know some parts of this application are not fully accessible: 

  • Some elements do not meet WCAG 2.2 AA minimum contrast ratio thresholds 
  • The application cannot be magnified up to and including 200% without loss of content 
  • Reflow is not supported up to 400% magnification 
  • User errors are not always identified and described to the user 
  • Some information is conveyed by colour only 
  • Text as an image may be found in the application 
  • There may be flashing, moving, or scrolling content found in the application 
  • Some content cannot be reached by keyboard alone 
  • Keyboard navigation order is sometimes illogical and unintuitive 
  • Some focus indicators are obscured by platform-authored content 
  • Where you have tabbed to my keyboard is not always clear 
  • Tooltips can not all be reached by keyboard or by assistive software 
  • Not all images have alt text 
  • The application is not fully compatible with assistive software such as screen readers 
  • Videos may not have human-corrected transcripts and captions 
  • Videos may not have audio descriptions 
  • Videos may automatically start playing 
  • Link hypertext is not always meaningful 
  • Links may open in a new tab without alerting the user of this 
  • Some links open new tabs or browser windows without warning 
  • Some content can only be accessed using a dragging movement 
  • The application may be unusable in landscape mode 
  • Help is not presented in a consistent location  

Feedback and contact information 

If you need information on this application in a different format, including accessible PDF, large print, audio recording or braille: 

  • Telephone: 0131 651 5151  

British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. 

We’ll consider your request and get back to you in 5 working days. 

Reporting accessibility problems with this application 

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

  • Telephone: 0131 651 5151 

British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. 

We’ll consider your request and get back to you in 5 working days. 

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 please contact the Equality Advisory and Support Service (EASS) directly: 

Contact details for the Equality Advisory and Support Service (EASS) 

The government has produced information on how to report accessibility issues: 

Reporting an accessibility problem on a public sector website 

Contacting us by phone using British Sign Language 

British Sign Language service 

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week. 

Contact Scotland BSL service details. 

Technical information about this application’s accessibility 

The University of Edinburgh is committed to making its websites and applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance Status 

This application is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances listed below. 

The full guidelines are available at:  

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard 

Non accessible content 

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

Non-compliance with the accessibility regulations 

The following items to not comply with the WCAG 2.2 AA success criteria: 

  • Information, structure, and relationships conveyed through presentation cannot be programmatically determined or are not available in text, e.g. <li> elements that are not contained in <ul> or <ol> tags and certain ARIA roles may not contain particular children 
  • Components do not always receive focus in a logical order 
  • The application is incompatible with landscape orientation at times 
  • Colour is used as the only visual means of conveying information, e.g. grade weighting errors are shown in red 
  • Some elements do not have sufficient contrast ratios 
  • It is not possible to magnify all content to 200% 
  • The application does not reflow up to 400% 
  • Tooltips do not always appear with keyboard navigation or when navigating by assistive software 
  • The application cannot be fully operated with a keyboard 
  • Links are not all formatted with meaningful hypertext 
  • It is not always clear where you have navigated to by keyboard 
  • Focus indicators may be obscured by platform-authored content 
  • Some content requires dragging movements 
  • Links do not alert the user before opening a new tab 
  • Elements, such as error messages, are not consistently identified 
  • Help is not presented in a consistent location 
  • Input errors are not all described to the user in text 
  • Content is not robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies. E.g. there are nested interactive controls, buttons do not have discernible text, from elements do not have labels and ARIA commands may not have an accessible name. 

Students and staff upload content directly into FeedbackFruits and it is not possible to guarantee it is accessible despite guidance being provided. For example: 

  • Not all images may have alternative text / descriptions 
  • Not all media may have human-corrected transcripts, captions, and audio descriptions. 
  • Some text may be as presented as an image.  
  • There may be moving or flashing content the end user cannot pause 
  • Links may not be formatted with meaningful hypertext 

We aim to improve our application's accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our site accessibility.  

We are working towards solving these problems and expect several improvements by July 2027 for those elements within our control. For those elements outwith our control, we will continue to liaise with the supplier to seek a resolution. There are no parts of the application other than content added by users under our control. 

Disproportionate burden 

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix. 

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

At this time we believe no content is outwith the scope of the accessibility regulations. 

What we’re doing to improve accessibility 

We are working towards solving these problems and expect significant improvements by July 2027 for those elements within our control. We will work together with the supplier, FeedbackFruits, to address the accessibility issues highlighted and deliver a solution or suitable workaround. As FeedbackFruits is a third-party system provided by FeedbackFruits, we have no ability to make changes for those issues which relate to the platform itself. 

While we are in the process of resolving these accessibility issues, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this application. 

Preparation of this accessibility statement 

This statement was prepared on 21 July 2026. It was last reviewed on 26 July 2026.

The application was last tested on 14 July 2026. The testing was carried out by the Interactive Content Service within the Information Services Group at the University of Edinburgh using both automated and manual methods. The site was tested on a PC, primarily using Google Chrome alongside Mozilla Firefox and Microsoft Edge. 

Recent world-wide usage levels survey for different screen readers and browsers shows that Chrome, Mozilla Firefox and Microsoft Edge are increasing in popularity and Google Chrome is now the favoured browser for screen readers: 

WebAIM: Screen Reader User Survey 

The aforementioned three browsers have been used in certain questions for reasons of breadth and variety. 

We ran automated testing using AXE (Google Chrome extension) and then manual testing that included: 

  • Spell check functionality; 
  • Scaling using different resolutions and reflow; 
  • Options to customise the interface (magnification, font, background colour, etc); 
  • Keyboard navigation and keyboard traps; 
  • Data validation; 
  • Warning of links opening in new tab or window; 
  • Information conveyed in the colour or sound only; 
  • Flashing, moving or scrolling text; 
  • Use with screen reading software (for example JAWS); 
  • Assistive software (TextHelp Read and Write, Windows Magnifier, ZoomText, Dragon Naturally Speaking, TalkBack and VoiceOver); 
  • Tooltips and text alternatives for any non-text content; 
  • Time limits; 
  • Compatibility with mobile accessibility functionality (Android and iOS); 
  • Any drag functionality and alternatives; 
  • Consistent help function; 
  • No need to re-enter data already submitted; 
  • Any cognitive tests. 


Application accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to the student side of the FeedbackFruits Learn Ultra integration.  

This application is run by the University of Edinburgh. It uses the third-party system FeedbackFruits. FeedbackFruits has been developed by FeedbackFruits, and is available to teaching staff on the Learn Ultra platform’s content market. Once the FeedbackFruits integration has been added to a course, students interacting with this integration will be presented with the student interface. 

We want as many people as possible to be able to use this application. For example, that means you should be able to: 

  • navigate most of the application using keyboard only  
  • navigate most of the application using speech recognition software e.g. Dragon  
  • use the application without encountering any cognitive function tests  
  • use the application without encountering any inactivity time outs.

We’ve also made the application text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means. 

Customising the Application

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:  

AbilityNet - My Computer My Way 

With a few simple steps you can customise the appearance of the application using your browser settings to make it easier to read and navigate: 

Additional information on how to customise our website appearance 

If you are a member of University staff or a student, you can use the free SensusAccess accessible document conversion service: 

Information on SensusAccess 

How accessible this application is 

We know some parts of this application are not fully accessible: 

  • Some elements do not meet WCAG 2.2 AA minimum contrast ratio thresholds  
  • The application is not fully compatible with assistive software such as screen readers 
  • Some information may be conveyed by colour only e.g. links  
  • Link hypertext is not always meaningful  
  • Not all images have alt text  
  • Not all videos have human corrected transcripts and human corrected captions  
  • Not all videos have audio description  
  • Some heading are not formatted correctly and some heading levels may be skipped  
  • Text as an image may be found in the application  
  • There may be flashing, moving or scrolling content found in the application  
  • It can be difficult to tell where you have navigated to by keyboard 
  • Focus indicators may be obscured by platform-authored content 
  • Videos may automatically start playing 
  • Several elements may not be consistently identified 
  • Error suggestions may not be given to aid users in resolving data validation errors 
  • Reflow is not supported up to 400% magnification 
  • The application cannot be magnified higher than up to 200% without elements disappearing 
  • The application may be unusable on mobile, especially on landscape or on smaller screens 
  • Links may open in a new tab or window without alerting the user of this 
  • Non-text content may be missing text alternatives.

Feedback and contact information 

If you need information on this application in a different format, including accessible PDF, large print, audio recording or braille: 

  • Telephone: 0131 651 5151  
  • British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. 

We’ll consider your request and get back to you within 5 working days. 

Reporting accessibility problems with this application

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

  • Telephone: 0131 651 5151  
  • British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service. 

We’ll consider your request and get back to you within 5 working days. 

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 please contact the Equality Advisory and Support Service (EASS) directly: 

Contact details for the Equality Advisory and Support Service (EASS) 

The government has produced information on how to report accessibility issues: 

Reporting an accessibility problem on a public sector website 

Contacting us by phone using British Sign Language 

British Sign Language service 

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week. 

Contact Scotland BSL service details. 

Technical information about this application’s accessibility 

The University of Edinburgh is committed to making its websites and applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance Status 

This application is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances listed below. 

The full guidelines are available at: 

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard 

Non-accessible content 

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

Non-compliance with the accessibility regulations 

The following items do not comply with the WCAG 2.2 AA success criteria: 

  • Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text e.g. <ul> and <ol> do not only directly contain <li>, <script> or <template> elements. 
  • The application is incompatible with small mobile device screens, and landscape orientation at times. 
  • Information may be conveyed by colour only, e.g. with non-underlined links. 
  • Some elements do not have sufficient colour contrast. 
  • Text cannot always be resized up to 200% without loss of content or functionality. 
  • The application does not reflow up to 400%. 
  • Links are not all formatted with meaningful hypertext. 
  • Heading styles may not be fully accessible 
  • It is not always clear where you have navigated to by keyboard. 
  • Focus indicators may be obscured by platform-authored content. 
  • Certain links open in a new tab without alerting the user of this. 
  • Elements, e.g. error messages, buttons, are not consistently identified. 
  • Error messages appear as inaccessible pop-ups. 
  • Appropriate error-correction suggestions may not be given. 
  • Content is not robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies e.g. there are nested interactive controls and ARIA commands may not have an accessible name. 

Students and staff upload content directly into FeedbackFruits and it is not possible to guarantee it is accessible despite guidance being provided. For example: 

  • Not all images may have alternative text/descriptions.  
  • Not all media may have human-corrected transcripts, human-corrected captions and audio descriptions.  
  • Some text may be as presented as an image.  
  • There may be moving content the end user cannot pause.  
  • Not all links will have a clear purpose.  
  • Heading levels may be missed.  

We aim to improve the accessibility of our websites and applications on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our site accessibility.  

We are working towards solving these problems and expect several improvements by July 2027 for those elements within our control. For those elements outwith our control we will continue to liaise with the supplier to seek resolution. There are no parts of the application other than content added under our control 

Disproportionate burden 

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix. 

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

At this time we believe no content is outwith the scope of the accessibility regulations. 

What we’re doing to improve accessibility 

We are working towards solving these problems and expect significant improvements by July 2027 for those elements within our control. We will work with the supplier, FeedbackFruits, to address the accessibility issues highlighted and deliver a solution or suitable workaround. As FeedbackFruits is a third-party system provided by FeedbackFruits, we have no ability to make changes for those issues which relate to the platform itself. 

While we are in the process of resolving these accessibility issues we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this application. 

Preparation of this accessibility statement

This statement was prepared on 15 July 2026. It was last reviewed on 20 July 2026. 

The application was last tested on 13 July 2026. The testing was carried out by the Interactive Content Service within the Information Services Group at the University of Edinburgh using both automated and manual methods. The site was tested on a PC, primarily using Google Chrome alongside Mozilla Firefox and Microsoft Edge. 

A recent worldwide usage levels survey for different screen readers and browsers shows that Chrome, Mozilla Firefox and Microsoft Edge are increasing in popularity and Google Chrome is now the favoured browser for screen readers: 

WebAIM: Screen Reader User Survey 

The aforementioned three browsers have been used in certain questions for reasons of breadth and variety. 

We ran automated testing using AXE browser extension (for Google Chrome) and then manual testing that included: 

  • Spell check functionality 
  • Scaling using different resolutions and reflow 
  • Options to customise the interface (magnification, font, background colour, etc) 
  • Keyboard navigation and keyboard traps 
  • Data validation 
  • Warning of links opening in new tab or window 
  • Information conveyed in the colour or sound only 
  • Flashing, moving or scrolling text 
  • Use with screen reading software (for example JAWS) 
  • Assistive software (TextHelp Read and Write, Windows Magnifier, ZoomText, Dragon Naturally Speaking, TalkBack and VoiceOver) 
  • Tooltips and text alternatives for any non-text content 
  • Time limits 
  • Compatibility with mobile accessibility functionality (Android and iOS) 
  • Any drag functionality and alternatives 
  • Consistent help function 
  • No need to re-enter data already submitted 
  • Any cognitive tests. 


This article was published on