WingsuitSign in

Accessibility statement

Last updated 19 September 2026

This accessibility statement applies to the Wingsuit website at usewingsuit.co.uk and to the Wingsuit app for iOS, iPadOS and Android, which run the same code.

Wingsuit is run by A2x Development Ltd, whose one director is Alex Colville. We want as many people as possible to be able to use it. For example, that means you should be able to:

  • choose a light or dark appearance, both for the app and separately for the board on your own screen, and one of eight colour themes
  • zoom in using your browser or device, and zoom the board itself with its own zoom control
  • navigate everything outside the whiteboard canvas (sign-in, settings, your boards and folders, dialogs) using a keyboard
  • hear the buttons, form fields and dialogs announced by a screen reader, because they are labelled

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 Wingsuit are not fully accessible:

  • what is drawn on a whiteboard (strokes, shapes, text, imported slides) is drawn to a canvas and is not available to a screen reader at all
  • you cannot draw, select or move anything on a board using a keyboard alone; drawing needs a mouse, pen or finger
  • the pages students see through a share or room link have no headings or landmarks to navigate by, and a screen reader will find almost nothing on them
  • PDFs, Word documents and PowerPoint files imported onto a board become pictures of their pages, so their text cannot be read by a screen reader or selected
  • the whiteboard’s floating toolbars do not reflow at high zoom; at about 400% they overlap the board rather than rearranging
  • Wingsuit does not yet respect the “reduce motion” setting on your device, so dialogs, the guided tour and automatic camera movements still animate
  • single letters are used as shortcuts for the drawing tools, and they cannot be turned off or changed

If you use a screen reader and someone has sent you a Wingsuit link, ask them for the material in another format. Teachers can export a board or share the original PDF, Word document or slide deck instead.

Feedback and contact information

If you find any problems not listed on this page, or think Wingsuit is not meeting accessibility requirements, email support@usewingsuit.co.uk. Alex Colville deals with these reports personally.

If you need information on this website in a different format, such as an accessible PDF, large print, easy read, audio recording or braille, email support@usewingsuit.co.uk. We’ll consider your request and get back to you within 10 working days.

Wingsuit is run by one person alongside teaching, so a reply may take longer during term time than in a school holiday.

Enforcement procedure

Wingsuit is a private-sector service. It is not a public sector body, so it is not itself subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, and the Equality and Human Rights Commission’s enforcement of those regulations does not apply to it.

Those regulations do apply to schools and colleges. A school or college that uses Wingsuit and has to publish its own accessibility statement may rely on this page for the Wingsuit part of it, including the non-accessible content listed below.

As a service provider, Wingsuit has duties under the Equality Act 2010, including the duty to make reasonable adjustments. If you are not happy with how we respond to your complaint, you can contact the Equality Advisory and Support Service (EASS), which advises on the Equality Act 2010 and can help you take a complaint further.

Technical information about this website’s accessibility

Wingsuit is committed to making its website and app accessible. It takes the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard as its target, and treats the problems below as work to be done rather than as permanent limitations.

Compliance status

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

That assessment is a self-assessment, and an honest one. No formal accessibility audit has been carried out, by Wingsuit or by anyone else. No conformance has been tested or certified. The statement is based on a review of Wingsuit’s own source code, not on testing with assistive technology, so it is likely that problems exist which this page does not list.

Non-accessible content

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

The whiteboard canvas

  • A board’s contents are drawn to a canvas with no text alternative and no equivalent in the page, so a screen reader announces nothing about what is on the board. This fails WCAG 2.2 success criteria 1.1.1 (non-text content) and 1.3.1 (info and relationships).
  • The canvas cannot be focused with a keyboard, and there is no keyboard way to draw, select, move or delete anything on a board. Panning with the space bar and stepping through slides with the arrow or page keys do work. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).
  • The drawing tools have single-letter shortcuts which cannot be turned off or remapped. They are suppressed while you are typing, but not otherwise. This fails WCAG 2.2 success criterion 2.1.4 (character key shortcuts).
  • The whiteboard fills the window and its toolbars float at fixed positions, so at around 400% zoom, or on a narrow screen, the controls overlap the board instead of reflowing. This fails WCAG 2.2 success criterion 1.4.10 (reflow).

Pages students see

  • A share link, room link or live session page is a full-screen board with no main landmark and, except on a room page, no heading. There is nothing for a screen reader or keyboard user to navigate. This fails WCAG 2.2 success criteria 1.3.1 (info and relationships) and 2.4.1 (bypass blocks).
  • Whether the viewer is connected is shown by a coloured dot. The dot is labelled, but the change is not announced, so a screen reader user is not told when the connection drops. This fails WCAG 2.2 success criteria 1.4.1 (use of colour) and 4.1.3 (status messages).

Imported documents and images

  • A PDF, Word or PowerPoint file imported onto a board is turned into a picture of each page. The text layer is discarded, so the words on a page or slide are images of text that cannot be read by a screen reader, selected or resized independently. This fails WCAG 2.2 success criteria 1.1.1 (non-text content) and 1.4.5 (images of text).
  • Images placed on a board carry no description, and there is nowhere for a teacher to add one. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

Navigation and page structure

  • There is no “skip to main content” link, and the sidebar of tool links is repeated before the content of every page. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).
  • In the signed-in app the content area is a plain container rather than a main landmark, and the two navigation regions are not labelled. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
  • The whiteboard editor has no page heading; the board’s name is an editable field. This fails WCAG 2.2 success criterion 2.4.6 (headings and labels).

Colour, contrast and motion

  • Secondary text is shown in a muted grey which has not been measured against its background and may fall below the required contrast ratio in light mode. This may fail WCAG 2.2 success criterion 1.4.3 (contrast (minimum)). It will be measured and corrected at the next review.
  • Dark mode on the board swaps light and dark and keeps every colour's hue, so red ink is still red to anyone viewing in dark mode, but the contrast of a colour against the dark paper has not been measured and a vivid colour a teacher chose may sit below the required ratio. This may fail WCAG 2.2 success criterion 1.4.11 (non-text contrast).
  • Wingsuit does not check the “reduce motion” setting. Dialogs and menus animate as they open, the guided tour moves between steps, and the board camera animates when it moves itself. This fails WCAG 2.2 success criterion 2.3.3 (animation from interactions), which is a AAA criterion Wingsuit intends to meet, and the automatic camera movement may also fail 2.2.2 (pause, stop, hide).

What is accessible

For completeness, the review also confirmed that sign-in and sign-up fields have real labels and autocomplete hints; that icon-only buttons in the toolbar, the tool options and the app shell carry accessible names; that every dialog has a title, traps focus and closes with Escape; that focus is visibly indicated throughout; that the page language and per-page titles are set; and that nothing in Wingsuit prevents you from zooming with your browser or device.

What we’re doing to improve accessibility

The problems above are listed roughly in the order they will be worked on. Giving the student-facing pages proper structure, honouring the reduce-motion setting, adding a skip link and measuring the text contrast are small changes and come first. Descriptions for images and a keyboard path into the canvas are larger pieces of work with no date yet.

Wingsuit has no separate accessibility roadmap; this page is it, and it is updated when something is fixed.

Preparation of this accessibility statement

This statement was prepared on 19 September 2026. It was last reviewed on 19 September 2026.

Wingsuit was last assessed on 19 September 2026 against the WCAG 2.2 AA standard. The assessment was carried out by Alex Colville, the company’s director, by reviewing the source code of the website and app: the whiteboard canvas and its toolbars, the pages students see, the sign-in forms, the colour and theming system, and how PDFs and slide decks are imported. It was not an audit: no automated testing tool was used, no pages were tested with a screen reader or other assistive technology, and no third party was involved.

There is no test report to publish. This statement will be reviewed at least once a year, and sooner if Wingsuit changes substantially. The next review is due in September 2027. Related pages: the safeguarding statement and the rest of the compliance documents.