Accessibility Statement

Tamil Special Children UK wants everyone to be able to use our websites, whatever their ability or technology. This statement covers:

• our main website, tamilspecialchildren.org.uk
• our bookings website, tickets.tamilspecialchildren.org.uk (event tickets, registrations and interest forms)

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

How accessible our websites are

Our websites are partly compliant with WCAG 2.2 Level AA. Most pages work well with a keyboard, screen readers and zoom, but some parts do not yet meet the standard. These are listed under “Known issues” below.

You should be able to:

• use a keyboard to reach every page, menu, form and photo gallery
• see where you are on the page, with a clear focus outline
• skip straight to the main content with a “Skip to main content” link
• zoom up to 400% and read pages on a small screen without scrolling sideways
• turn off most animation by setting “reduce motion” on your device
• use a screen reader with headings, labelled forms and labelled buttons

Known issues

We know about the following problems and are working to fix them.

Main website

• Our older newsletters and the volunteer handbook are PDFs that are not fully accessible. Most pictures in them have no text description, and the 2022 newsletter has no structure for screen readers. You can ask for any of them in another format (see below).
• On phones, the newsletter and handbook previews can only be zoomed with a pinch. You can use the “Download PDF” link to open them in your own reader instead.
• Photos in the event galleries have short descriptions such as “Photo 3 of 61 from Charity Walk”, not a full description of each picture.
• Videos are hosted on YouTube. Captions depend on YouTube and may be automatic.

Bookings website

• Several pages share the same page title, so the event name is not always announced when a page opens.
• When a booking form is closed, its fields can still be reached with the keyboard even though they cannot be used.
• On booking forms, the pay or confirm button stays greyed out until everything is filled in, without saying what is missing. Some messages that appear while you fill in the form are not read out by screen readers.
• On the interest and workshop forms, errors are not always read out, and some fields for children’s names and ages rely on placeholder text instead of a label.
• A few small labels, such as the “Paid Event” badge, do not have enough colour contrast.
• Tamil text on the summer interest form is not marked as Tamil, so screen readers may read it with an English voice.
• The site has a security check that can sometimes block automated tools and older assistive browsers. If it stops you booking, contact us and we will book for you.
• Card payments are taken on a page run by Stripe, which we do not control.

Other formats and help with booking

If you need anything on our websites in a different format, such as an accessible PDF, plain text, large print or a Word document, or you would like us to make a booking for you, please get in touch. Tell us what you need and how we can reach you.

Contact us and feedback

If you find a problem that is not listed here, or you need help, you can contact us by:

• email: contact@tamilspecialchildren.org.uk
• the contact form on our Get Involved page
• a direct message to us on Instagram or Facebook

We will reply within 5 working days. If you ask for something in a different format, we will tell you how long it will take, and aim to send it within 10 working days.

If you are not happy with our response

If you are not satisfied with how we respond, you can contact the Equality Advisory and Support Service (EASS).

How we tested our websites

We last tested both websites in September 2026. We checked the main pages of the main website (home, about, events, get involved, donate, links, gallery, FAQs, our stories and the policy pages) and the main pages of the bookings website (the event pages, the t-shirt, summer and workshop forms, and the booking confirmation page). We used automated testing with axe-core on desktop and phone screen sizes, and checked by hand keyboard use, focus outlines, zoom and reflow at 320 pixels wide, and how pages appear to screen readers. We also checked our PDF documents.

This statement was first prepared in February 2026. It was last reviewed and updated in September 2026.