Accessibility Statement

How LittleBlueCup is working to make its website and services usable by as many people as possible.

Accessibility statement prepared: 10 July 2026

Last reviewed: 10 July 2026

Current accessibility status

Not yet fully assessed against WCAG 2.2 Level AA.

LittleBlueCup is being built with WCAG 2.2 Level AA as its accessibility target.
The website has not yet been fully assessed against every WCAG 2.2 Level A and Level AA success criterion, so LittleBlueCup does not currently claim full conformance.
Automated and manual checks are being added as the platform develops. Known barriers and incomplete features are listed on this page where they have been identified.

If something stops you from using LittleBlueCup, please tell us. You do not need to know the technical name for the problem.

LittleBlueCup is not currently understood to be a public-sector website. This statement is not legal advice and it is not proof of legal compliance.

Our aim

Accessibility matters from the start.

LittleBlueCup is used by disabled people, parents, carers, families, volunteers, people offering help, moderators and staff.

Accessibility should not be added as decoration after a feature is finished. It should influence how pages, forms, content and decisions are designed from the beginning.

We want people to be able to ask for help, offer help, read important information and use the website without avoidable barriers.

What we are working towards

These are the accessibility principles LittleBlueCup aims to apply as the website develops.

Clear language

Use plain English, practical labels and fewer unnecessary words.

Readable text

Provide text that can be enlarged, spaced and reflowed without losing information or controls.

Sufficient contrast

Make text, controls, focus indicators and important visual information distinguishable from their backgrounds.

Keyboard access

Make interactive controls usable without requiring a mouse, touchscreen or precise pointer movement.

Mobile and responsive layouts

Allow pages to work at narrow widths and high zoom without unnecessary horizontal scrolling.

Meaningful links and controls

Use labels that explain the destination or action clearly, including outside the surrounding paragraph.

Helpful headings and structure

Use headings, landmarks and page structure that help people understand and navigate content.

Useful text alternatives

Give meaningful images useful descriptions and ensure decorative images do not create unnecessary screen-reader noise.

Understandable forms

Use clear labels, instructions, error messages and confirmation states that do not rely only on colour.

Consistent and uncluttered design

Keep important actions predictable and reduce avoidable distraction, repetition and visual noise.

What you should be able to do

LittleBlueCup aims to let people use its main journeys in different ways.

Source checks and sampled browser checks show that many pages use headings, links, buttons and labelled form fields, but this has not yet been confirmed across the whole site or with every assistive technology.

navigate using a keyboard
use common screen-reader software
zoom text and pages without losing important content
use the site on phones, tablets and desktop screens
understand links, buttons and form labels
identify and correct form errors
pause before submitting important information
access information without relying on colour alone
use the website with browser text-spacing changes
avoid unnecessary motion
contact LittleBlueCup when another format or route is needed

Treat these as aims unless that part of the site has been tested and confirmed.

Known accessibility problems

LittleBlueCup is still developing. Some barriers may remain, and new features may introduce problems that have not yet been identified.

A full accessibility audit has not yet been completed. This means there may be barriers that are not yet listed here.

Search filters need stronger accessible labelling

Affected feature or page: Active Searches filter controls.
Barrier: The keyword field and filter select controls currently rely heavily on placeholder text, option text and visual position rather than separate visible labels for each control.
Who may be affected: People using screen readers, voice control, translation tools or high cognitive load may find the filters harder to identify.
Current workaround: Browse the unfiltered Search list, use broader keyword searches, clear filters, or contact LittleBlueCup if finding a Search is difficult.
What LittleBlueCup intends to do: Add explicit labels or equivalent accessible names to the filter controls during a focused Search directory accessibility pass.

Dialogs and image viewers need fuller focus checks

Affected feature or page: Cookie settings, public Search photo viewer and other dialogs or drawers.
Barrier: Some dialogs provide close controls and Escape-key support, but focus trapping and focus return have not yet been fully assessed across every dialog.
Who may be affected: Keyboard and screen-reader users may have a harder time staying within a dialog or returning to the previous control.
Current workaround: Use the visible close button or Escape where it works. If a dialog blocks progress, use the contact route to ask for help.
What LittleBlueCup intends to do: Check shared dialog, sheet and lightbox behaviour, then make keyboard focus work consistently.

Video, audio, captions and transcripts are not yet consistent

Affected feature or page: Public Search media, updates, uploaded clips, audio and future story media.
Barrier: Video controls exist where clips are displayed, but captions, transcripts and audio descriptions are not yet consistently required, stored or shown.
Who may be affected: Deaf users, hard-of-hearing users, people who cannot play sound, and people who need text instead of video or audio may miss important information.
Current workaround: Ask LittleBlueCup for a written summary or another usable format when video or audio is not accessible.
What LittleBlueCup intends to do: Build captions, transcripts, descriptions and media-review checks into normal publishing workflows.

Long forms need more assistive-technology testing

Affected feature or page: Search-request and full Search application journeys, including upload and consent sections.
Barrier: Many fields have labels, helper text, errors and saved-draft behaviour, but the longer multi-step application has not yet been fully tested with screen readers, browser text-spacing changes or disabled users.
Who may be affected: People using screen readers, keyboard navigation, magnification, speech input or memory-support tools may meet barriers on longer forms.
Current workaround: Use save points where available and contact LittleBlueCup if a form cannot be completed accessibly.
What LittleBlueCup intends to do: Run a dedicated form accessibility review covering labels, helper text, validation, focus order, review screens and error recovery.

There is not yet a global skip link

Affected feature or page: Shared public and account layouts.
Barrier: Pages use main content areas and headings, but the shared layout does not currently provide a visible skip-to-main-content link.
Who may be affected: Keyboard users may need to tab through repeated navigation before reaching the main page content.
Current workaround: Use browser heading, landmark or find-in-page tools where available.
What LittleBlueCup intends to do: Add and test a skip link in the shared layout.

Uploaded documents are not automatically checked for accessibility

Affected feature or page: Applicant uploads, staff files and any future downloadable documents.
Barrier: The platform can accept PDF, DOC and DOCX files in some upload flows, but it does not automatically confirm whether those documents are accessible.
Who may be affected: People using screen readers, text reflow, high zoom or keyboard-only navigation may not be able to use inaccessible documents.
Current workaround: Ask LittleBlueCup for an accessible version, clearer written format or summary.
What LittleBlueCup intends to do: Set document-accessibility expectations before downloadable public documents become part of essential journeys.

Motion and animation have not had a full reduced-motion review

Affected feature or page: Hover effects, transitions, image cards and interactive public Search views.
Barrier: The site uses some movement and transition effects. These have not yet been fully reviewed against reduced-motion preferences.
Who may be affected: People with vestibular conditions, migraine, attention difficulties or motion sensitivity may be affected.
Current workaround: Use browser or operating-system reduced-motion settings where available and report any movement that causes difficulty.
What LittleBlueCup intends to do: Review animation and transition patterns and add reduced-motion alternatives where needed.

Media accessibility

Photographs, video and audio can make Searches easier to recognise and understand, but they can also create barriers when accessible alternatives are missing.

meaningful images should have useful text alternatives
decorative images should be ignored by assistive technology
video with important speech should have captions
important audio-only content should have a transcript or equivalent
controls should be keyboard accessible
media should not play unexpectedly
flashing or rapidly moving content should be avoided
captions and transcripts should be checked for accuracy

The aim is to make captions, transcripts, descriptions and usable controls part of normal publishing rather than an afterthought.

Forms and Search journeys

LittleBlueCup forms may ask for detailed or emotional information. They should remain understandable, predictable and forgiving.

The project aims to provide:

visible labels
clear explanations of why information is requested
optional and required fields identified in text
helpful error messages
a way to review important information before final submission
confirmation when information has been saved or submitted
enough time to read and complete a form
preservation of entered information where reasonably possible after an error
alternatives where a form cannot be used accessibly

Some form features, including draft preservation and review-before-submit flows, already exist in parts of the platform. They have not yet been fully assessed across every form and assistive technology.

Making difficult tasks easier to understand

People may use LittleBlueCup while tired, distressed, overwhelmed or under pressure.

Accessibility includes more than screen readers and contrast. LittleBlueCup also aims to:

break long tasks into clearer steps
explain unfamiliar terms
avoid unnecessary deadlines or pressure
show what happens next
provide useful confirmation messages
avoid forcing people to repeat information without a good reason
keep important warnings clear and consistent
allow people to pause where the process supports it

Services LittleBlueCup does not fully control

Some parts of LittleBlueCup may rely on external services. LittleBlueCup cannot directly control every accessibility feature or barrier within another provider's website or interface.

Firebase and Google sign-in infrastructure
Postmark email notifications where configured
Patreon, Paper Armour and other linked support routes
Facebook, Instagram, TikTok, YouTube and other social platforms where content is shared or linked
browser, device and assistive-technology behaviour outside LittleBlueCup's code

We still want to know when a third-party service prevents somebody from completing an important task, so we can look for another route where reasonably possible.

Ask for another way to access something

If a page, form, video, document or process is not usable for you, contact LittleBlueCup and explain what you are trying to do.

You may ask for:

information in a clearer written format
help understanding a process
a transcript or written summary
an accessible version of a document
another reasonable way to provide information
help reaching the correct form or contact route

We may need to discuss what alternative is practical, but we will take the request seriously and try to find a reasonable route.

Tell us the barrier and what would help. You do not have to prove your disability or know the technical accessibility term.

If something is hard to use

Please tell us if something stops you, slows you down, causes confusion or makes LittleBlueCup harder to use than it should be.

Useful details may include:

the page or Search you were using
what you were trying to do
what happened
the device and browser used
any assistive technology used, where you are comfortable sharing it
the wording of an error
a screenshot with unnecessary personal information removed
what would make the task easier

You do not need to know the technical name for the problem. A plain description is enough.

Sharing information about assistive technology is optional. Do not include passwords, banking details or unnecessary sensitive information.

Report an accessibility problem

What happens after you contact us?

LittleBlueCup will review the problem and try to understand which part of the website or process created the barrier.

Depending on the issue, we may:

ask for clarification
suggest a temporary alternative
correct page content
record the issue for technical work
contact an outside service
explain what can and cannot currently be changed
update this statement when a significant known issue is confirmed

Some accessibility changes may take longer than others, but reports should not disappear without being considered.

How this website has been tested

This statement is based on source inspection and sampled checks carried out on 10 July 2026. It is not a full accessibility audit of the whole website.

The sampled pages and journeys included:

homepage and shared navigation
mobile navigation
Active Searches and Search filters
public Search detail pages and media galleries
How LittleBlueCup Works
Search-request form
full application form source
sign-in and account menu source
messaging attachment source
contact form and contact API
cookie banner and cookie settings
Privacy Policy, Terms of Use, Content and Media Permissions and related public policy pages
staff-facing layout, media and Search workspace source where relevant to this statement

Checks included page structure, headings, landmarks, labels, errors, focusable controls, mobile reflow, 200% zoom, keyboard tab order on sampled pages, contact routing and automated checks where tooling was available.

Automated testing can identify some accessibility problems, but it cannot confirm that a website is fully accessible. Manual checks and feedback from people using the service remain important.

No screen-reader testing with assistive-technology users and no testing with disabled users has been completed for this statement.

Technical information

LittleBlueCup aims to work with current versions of commonly used browsers and assistive technologies.

LittleBlueCup is working towards WCAG 2.2 Level AA.

Current status: not yet fully assessed against WCAG 2.2 Level AA.

A specific browser or assistive-technology support matrix has not yet been tested and published.

Ongoing improvement

Accessibility is not a one-off checklist.

LittleBlueCup is continuing to test, learn and improve as the service develops.

New pages and tools can introduce new barriers. Accessibility should be considered during design, development, content writing, testing and review.

When LittleBlueCup changes, its accessibility work must continue with it.

Reviewing this statement

This statement will be reviewed when significant accessibility information changes and as the platform develops.

Accessibility statement prepared: 10 July 2026
Last reviewed: 10 July 2026

No fixed annual or six-month review schedule is being claimed here until that review process has been chosen and can be maintained.

If something stops you using LittleBlueCup, we want to know.

Tell us what happened, what you were trying to do and what would make the task easier.

We will do our best to understand the barrier, provide a reasonable alternative where possible and improve the website where we can.

Report an accessibility problem