Accessibility Information

We are constantly working to make this site as accessible and usable as possible. We are committed to making this site accessible to all users, including users who may be blind, partially sighted, or have a physical disability. All pages are created with accessibility in mind and we have done this by adhering sensibly and practically to the guidelines of the World Wide Web Consortium's Web Accessibility Initiative (WAI) and Web Content Accessibility Guidelines 2.1 (WCAG). We aim to meet the WCAG 2.1 Level AA success criteria across our products and will continue to improve accessibility over time.

This site also uses the recommended markup for WAI Accessible Rich Internet Applications (ARIA), to allow ARIA-enabled Assistive Technologies (AT) to better interact with each page.

How the site is built for accessibility

Layout

The site uses Cascading Style Sheets (CSS) to control the presentation and the layout. This means screen reader users can use navigation keys to move around the site more easily. As a result, screen reader users can use the screen reader's navigation keys to move around the site. Menus are grouped together in a logical and consistent fashion. Users can quickly use the "Skip to main content" link to get to the main content of the page.

Content

The content has been written and formatted to make it accessible. For example:

  • Headings are used to highlight sections of text
  • Links use meaningful text
  • Forms can be navigated using the tab key
  • Fieldsets and Legends are used to group related elements on a form
  • Status messages and alerts use the appropriate ARIA role so that you know about important changes
  • When entering information about yourself on a form, we use standard autocomplete tokens to indicate the purpose of each field
  • Access Keys can be used to access common features
  • Significant images have alternative text so if you can't see the image you can still understand what it contains
  • ARIA landmark roles are used to identify the key areas (landmarks) on the page to ARIA-enabled Assistive Technologies

Operation

The site is designed to be used either with a mouse and keyboard, or just with a keyboard. Keyboard users can use the tab key to move around the links, forms and buttons on each page.

The site can also be navigated with the keyboard using the following Access keys and Shortcut keys.

Access keys

Access keys are additional keyboard controls for people who have difficulty in using a mouse or other pointer-device. The following access keys are available on this site:

  • s - Skip to the main content
  • 2 - What's New in this community (when viewing a community page)
  • 4 - Search in this community (when viewing a community page)
  • 8 - Terms and Conditions, includes disclaimer and copyright statement
  • 9 - Feedback

We also support the following access keys specific to this site:

  • m - Community homepage
  • c - Skip to the Actions menu for this page (when present)
  • n - Create a new item in current view (eg. item in a folder, entry in a database, event in a calendar)
  • x - Log out

At the time of writing the following browsers support access keys:

  • Windows: In Edge, Chrome and Opera, hold down the ALT key and press the access key (e.g. ALT+s). In Firefox, hold down both Shift and the ALT key and press the access key (e.g. Shift+ALT+s).
  • Mac: In Safari, Chrome and Firefox, hold down the Control (CTRL) key and the Option key and press the access key (e.g. CTRL+Option+s). In Opera, hold down both the Control (CTRL) key and the ALT key and press the access key (e.g. CTRL+ALT+s).

Shortcut keys

On form pages that include the Rich Text editor use the following keyboard shortcuts:

  • ALT+F9 - Focus / jump to the menu bar
  • ALT+F10 - Focus / jump to the toolbar
  • ALT+F11 - Focus / jump to the element path
  • ESC - Close menu / submenu / dialog (also gets you back to the editor area)
  • Tab/Arrow - Navigate left / right through the menu / toolbar

On form pages that include a sortable list, use the TAB key to select a list item then use the following keyboard shortcuts:

  • SHIFT+↑ - Move the item up
  • SHIFT+↓ - Move the item down
  • SHIFT+Home - Move the item to the top of the list
  • SHIFT+End - Move the item to the end of the list
  • ENTER - Move the item to the connected list if there is one

JavaScript

The site makes use of JavaScript to enhance the usability and provide some additional functionality in the user interface. Where browsers or Assistive Technologies (AT) are not able to support JavaScript, the core functionality will still be available but some more advanced functionality may not.

We recommend enabling JavaScript for this site for improved functionality; for example, JavaScript users will receive in-place warnings and alerts about errors on forms before submitting details to the site, whereas without JavaScript these errors will be reported by a separate page.

Browser plugins

No browser plugins are required to access or modify any content on the site.

Optional downloads

Documents on this site may use the PDF (Adobe Acrobat) file format for the publication of large and complex documents. To view and print PDF files, you must have Adobe® Acrobat® Reader installed: Download Adobe® Acrobat® Reader software from the Adobe site.

Alternatively, documents may also be published in Microsoft Word format. To view Microsoft Word files, you must either have Microsoft Word installed on your device or use Office 365 to view the document in your browser or install a Word mobile app on your phone or tablet.

Known issues

We aim to make Kahootz accessible and to meet WCAG 2.2 Level AA. However, we are aware that some parts of the site are not yet fully accessible.

All products

  • Some form field borders do not meet minimum contrast requirements. This may make it harder for some users to identify input fields. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast).

Kahootz Consult

  • The “Show: Open | Closed | All” filter is not marked up as a single related control. This may make it harder for assistive technologies to interpret. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  • Some form fields on Register and Login pages do not include programmatic input purposes. This may reduce the effectiveness of autofill and assistive technology support. This fails WCAG 2.1 success criterion 1.3.5 (Identify Input Purpose).

Further help and information

You can get help with the accessibility features built into common desktop computers, laptops, tablets and smartphones by reading My Computer My Way.

Feedback

If you have any problems using this site with the keyboard or your Assistive Technology, e.g. screen reader, screen magnifier, text to speech, speech recognition, etc., please contact us and we'll do our best to help.

Please note: for advice on what information to include when you contact us, we recommend you read Contacting Organizations about Inaccessible Websites.

Last updated

This accessibility statement was updated on 26 February 2026