Accessibility Statement

1. Our commitment

Effective Clerking is used by clerks, governors and trustees, some of whom are disabled. We want the Service to work for all of them.

We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA.

2. Where we stand

Not yet assessed — we have built to WCAG 2.2 AA principles but have not yet completed a formal assessment. We plan to complete one by 01/09/2027

3. What we have built in

Colour is never the only way meaning is conveyed. Every status badge carries an icon and a text label as well as a colour, and every school colour tag carries the school’s name.

The colour palette was chosen using a colour-blindness distance validator against both light and dark backgrounds, rather than picked by eye.

Light and dark modes are both designed deliberately, not generated by inverting one from the other.

A table or list view is available everywhere a card or board view is offered.

Touch targets on small screens are at least 44 by 44 pixels.

Forms use visible labels, not placeholder text alone.

The interface is designed to work with keyboard navigation and screen readers.

Text can be resized without loss of content or function.

4. Known issues

We spot-checked the landing page, sign-in page and sign-up flow on 07/09/2026 using an automated accessibility-tree pass (form fields correctly labelled, interactive elements have accessible names, heading structure present) and did not find an issue to record here. This is a spot-check, not the formal assessment described above, and it covered only a handful of pages — the table below will be completed properly as part of that assessment.

5. Content we cannot control

Documents you produce using the Service — minutes, agendas, invoices — take their accessibility partly from what you write. We format headings and structure properly in generated PDFs and Word files, but the accessibility of your own wording, tables and attachments is yours.

If you need to produce documents to a particular accessibility standard for publication on a school website, tell us at support@effectiveclerking.co.uk and we will help where we can.

6. Where the legal duty sits

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 place duties on public sector bodies, including schools in respect of essential online administrative functions. They do not place duties directly on us as a supplier.

We publish this statement so our customers can meet their own duties, including the reasonable adjustments duty under the Equality Act 2010, and so their procurement teams have the information they need.

7. Tell us about a problem

If you find something you cannot use, please tell us at support@effectiveclerking.co.uk. Include the page or feature, what you were trying to do, and any assistive technology you were using.

We will acknowledge within 5 working days and tell you what we can do and by when. If a fix will take time, we will offer an alternative way to do what you needed.

8. Enforcement

If you are unhappy with our response you can contact us again at support@effectiveclerking.co.uk and we will escalate under our Complaints Procedure.

Where the accessibility of a public sector body’s own website or application is in question, the Equality and Human Rights Commission is responsible for enforcing the 2018 Regulations in England, Scotland and Wales, and the Equality Commission for Northern Ireland in Northern Ireland.

9. How this statement was prepared

This statement was prepared on 01/09/2026. The Service was last spot-checked on 07/09/2026, using an automated accessibility-tree pass over the landing, sign-in and sign-up pages. This is not the formal WCAG 2.2 AA assessment described in section 2, which is still pending.

We review this statement at least annually and whenever we make a significant change to the interface.