This browser is too old for this site. Some pages may not work. Update your phone, or try a different device.

Accessibility

Accessibility statement

How well the Assembly website and app meet WCAG 2.2 level AA, what does not work yet, and how to report a problem.

What this statement covers

The public website at www.helloassembly.com, and the Assembly app that parents, carers and school staff sign in to.

We are working towards WCAG 2.2 level AA, and that is the standard we are held to. We also use a newer contrast method, APCA, as a design aid. We make no claim to meet APCA.

Not covered here

  • Prototypes and design tools we publish as demonstrations. We do not offer them as a service.

Browsers we support

Assembly works on:

  • iPhone and iPad with iOS 15.4 or later
  • Safari 15.4 or later on a Mac
  • Chrome or Edge version 109 or later
  • Firefox version 113 or later
  • Samsung Internet version 21 or later

On an older browser, some pages may not work. Many older browsers also show a note at the top of the page, but not all of them do. If you can, update your device. On an iPhone or iPad, every browser works the same way as Safari, so a different browser will not help. Try a different device.

How compliant we are

This website and app are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed below. 22 of the 55 level A and AA criteria are not fully met. The WCAG A and AA page sets them out one by one.

Each criterion also says whether a test protects it from breaking. For 22 of the 55, that test has to pass before any change can go in, and 16 of those are criteria we fully meet. Another 21 have an automated test that cannot stop a change going in. On the website, that change then goes live. On the app, some of those tests run again once the change is in, and a failure stops it reaching the live app unless we override it and record why.

Before 9 August 2026 our statement said a test protected both groups. That was wrong for the second group.

Content that is not accessible

We know of 2 problems today, affecting 2 of the 55 criteria. Each says what you would notice, why it happens, how we found it and what we will do.

Assembly app: 1 known problem

  1. NC-6, fails 4.1.3 Status Messages

    When Assembly replies in chat, a separate short notice says 'Assembly has replied.' It tells you a reply has arrived even if your screen reader mishandles the reply itself. Until 28 September 2026 this notice, and the 'Thinking' notice, were never spoken, because of how they were added to the page; that is now fixed. The NVDA screen reader has been recorded speaking both, but no person has listened, and VoiceOver and JAWS are not yet checked.

    Why:
    Replies appear a few words at a time, so we ask screen readers to wait and read the finished reply once. Screen readers handle that request differently. The separate notice does not rely on it, but only real screen readers can show that it is heard.
    How we found it:
    Our own code review on 8 August 2026 found the chat said nothing to screen readers. We added announcements on 15 August 2026, and the separate notice on 16 August 2026. On 27 August 2026 an AI agent ran VoiceOver over the questionnaire's help chat, and the result was unclear, because the way the test listened may have drowned the notice out. On 28 September 2026 an AI agent read NVDA's own record of what it said while pressing nothing, which cannot drown anything out: neither notice was spoken. We fixed the cause the same day, and on the next run NVDA spoke both notices on both chat screens.
    What we will do:
    Check both chat screens with VoiceOver and JAWS, and have a person listen to what NVDA was recorded saying. This is the only step left.

Public website: 1 known problem

  1. NC-4, fails 1.4.10 Reflow

    Our pages fit a 320 pixel wide screen without scrolling sideways, and a check measures that. An AI agent also judged whether the narrow layouts are easy to use, and the three rough edges it found have all been dealt with. No person has yet done the same check on a real phone.

    Why:
    Whether a narrow layout is easy to use takes judgement, which no automated check makes. The AI agent found nothing that made a page unusable, so this is partly met, not failed. It stays that way until a person checks on a real phone. This entry does not cover the signed-in app.
    How we found it:
    Our own review on 8 August 2026, the first time either product was loaded at 320 pixels. On 15 August 2026 we added the check for sideways scrolling. On 16 August 2026 an AI agent named three rough edges, and by 27 August 2026 all three had been dealt with.
    What we will do:
    A person will repeat the check on a real phone, in light and dark mode, with menus and tabs opened.

Criteria nobody has assessed yet: 0 of 55

None. Every one of the 55 criteria has a recorded status.

Reporting an accessibility problem

If you find a problem that is not listed here, or you need something from the website or the app in a different format, email info@helloassembly.com. Tell us the page or screen, what you were trying to do and what happened. We aim to reply within 5 working days.

We treat accessibility problems as bugs. If you report one we have not listed, we will add it to this page with our plan to fix it.

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. Assembly is a private company, so those regulations do not apply to us directly. We hold ourselves to the same standard, which is why this statement follows their model.

As a service provider we are covered by the Equality Act 2010. If you contact us about an accessibility problem and you are not happy with our reply, contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com. In Northern Ireland, contact the Equality Commission for Northern Ireland (ECNI) at equalityni.org.

Preparation of this statement

This statement was prepared on and last reviewed on . The website and app were last tested on . The testing was carried out by Assembly, in house. The How we test page explains how.

More detail

The rest of our accessibility pages, some of which used to be part of this one:

The full record is also available as a data file (JSON).