Accessibility statement for Orlando website

This statement was last updated in March 2026.

This accessibility statement applies to the Orlando website. This website is managed by Cambridge University Press & Assessment, with technical maintenance of the interface by the Orlando Project team. 

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

  • Change colours, contrast levels and fonts by adjusting browser settings. Different browsers include these options under different menus – they can usually be found under Tools, Settings, Options, Content or Reading View depending on the browser. There are also browser extensions specifically dedicated to changing colours and contrast options, e.g. Change Colors for Google Chrome and Color Changer for Mozilla Firefox.
  • Zoom in up to 200% without the text spilling off the screen for most of the website
  • Navigate most of the website using just a keyboard.
  • Navigate most of the pages in logical reading order with the ability to skip to headings, regions and hyperlinks. There are also multiple ways to navigate the entire site including navigation menus and crumb trails.
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
  • Use text to speech tools to read out website content. Text to speech tools are built into some browsers (e.g. Microsoft Edge) and are available as a plug-in for many others. Your phone, tablet or laptop accessibility settings are also likely to provide text to speech functionality.

We’ve also made the website text as simple as possible to understand.

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, for example:

  • In some areas the tab sequence does not reflect the visual order.
  • Some interactive elements are not accessible via keyboard.
  • Some decorative images have descriptive alt text and linked image alt text doesn’t describe the link purpose.
  • On some pages, the heading structure is not consistent.
  • Some expandable buttons don’t have correct state set.
  • Some buttons/links are lacking descriptive, accessible labels.
  • Some buttons/links are marked up with non-semantic HTML.
  • Some interactive elements are lacking visible focus indicator or have focus indicator with insufficient colour contrast.
  • When text spacing is adjusted, content is clipped, obscured, or lost in some areas.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact us via email: orlando@ualberta.ca.

Where a work is unavailable for purchase in a suitable format, we welcome enquiries from both individuals and institutions to provide one. More information and the Accessibility Request Form can be found here.

We aim to respond to any requests within 5-7 working days. 

Technical information about this website’s accessibility

Compliance status

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard, it was found to be partially compliant with this standard, due to the issues listed below.

Non-accessible content

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

  • The tab sequence is illogical or does not reflect the visual order in some areas.
    This fails WCAG 2.1 success criterion 2.4.3 Focus Order (A)
  • Some interactive elements are not accessible via keyboard.
    This fails WCAG 2.1 success criterion 2.1.1 Keyboard (A)
  • Some decorative images have descriptive alt text.
    This fails WCAG 2.1 success criterion 1.1.1 Non-text Content (A)
  • Linked image alt text does not describe the link purpose in some areas.
    This fails WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context) (A)
  • On some pages, the heading structure is not consistent (e.g. lacking heading level 1, section titles are not marked up as headings, text incorrectly marked up as heading, heading level 2 before heading level 1, skipped heading levels, etc.) 
    This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships (A) & 2.4.6 Headings and Labels (AA)
  • Some expandable buttons don’t have correct state set (via aria-expanded attribute).
    This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value (A)
  • Some buttons/links are lacking descriptive, accessible labels.
    This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value (A) & 2.4.6 Headings and Labels (AA)
  • Some buttons/links are marked up with non-semantic HTML so their role may not be recognised by assistive technologies.
    This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value (A)
  • Some interactive elements are lacking visible focus indicator or have focus indicator with insufficient colour contrast.
    This fails WCAG 2.1 success criterion 2.4.7 Focus Visible (AA) & 1.4.11 Non-text Contrast (AA)
  • When text spacing is adjusted, content is clipped, obscured, or lost in some areas. 
    This fails WCAG 2.1 success criterion 1.4.12 Text Spacing (AA)

We’ve assessed the cost of fixing the above issues. Due to this customized interface being maintained by an academic research project, we believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in September  2026.

Browser and mobile device support 

This site is optimised for modern browsers including Microsoft Edge, Mozilla Firefox, Apple Safari, and Google Chrome. You may experience unexpected behaviour in other browsers. However please note that we no longer support Internet Explorer 11.  

Screen reader compatibility 

This platform has been optimised for the following screen reader and browser combinations: 

Desktop screen readers 

  • VoiceOver with Safari (macOS) 
  • NVDA with Chrome 
  • JAWS with Chrome 
  • Narrator with Edge 

Mobile screen readers 

  • VoiceOver with Safari (iOS) 
  • TalkBack with Chrome (Android) 

Voluntary Product Accessibility Template (VPAT)

The Voluntary Product Accessibility Template (VPAT) is a document which evaluates how accessible a particular product is according to the Section 508 Standards in the US. It is a self-disclosing document produced by the vendor which details each aspect of WCAG 2.1 requirements and how the product supports each criterion. Download VPAT for Orlando (PDF).

How we test this website

This website was last tested on in April 2021 against the WCAG 2.1 AA standard.

The test was carried out by the Digital Accessibility Centre (DAC).