Accessibility Statement
EarlyBridge aims to make this website clear, readable and usable for as many people as possible, including people who use assistive technologies or access the site in different ways.
1. Our approach to accessibility
EarlyBridge believes that information about early-years development and family support should be easy to understand and straightforward to access.
The website has therefore been designed with clarity, readability and usability in mind. This includes attention to page structure, navigation, text presentation, contrast, keyboard use and mobile access.
Accessibility is treated as an ongoing part of website quality rather than a one-time design task.
2. Who this statement is for
This statement is intended for anyone using the EarlyBridge website, including parents, carers, early-years professionals, nursery staff and other visitors.
Different users may interact with the website in different ways. Some people may use a keyboard instead of a mouse, zoom text significantly, use a screen reader, browse on a mobile device, or prefer reduced movement and simpler visual presentation.
3. Accessibility features included
The website has been designed to include a number of accessibility-conscious features.
Semantic structure
Pages use headings and structural HTML elements to create a more logical reading order.
Keyboard navigation
Interactive elements are intended to remain usable without relying only on a mouse or touchscreen.
Skip link
A skip-to-main-content link helps keyboard users move past repeated navigation more quickly.
Readable typography
Text sizes, spacing and line height are designed to support comfortable reading.
Colour contrast
The visual design uses strong contrast between text and backgrounds wherever possible.
Responsive design
Layouts adjust for desktop, tablet and smaller mobile screens.
Alternative text
Meaningful images should include appropriate text alternatives where relevant.
Form labels
Forms are designed with visible labels and clear input purposes to make completion easier.
4. Keyboard access
The website is intended to support keyboard navigation for important interactive elements such as links, buttons and form controls.
Focus styles are used so that users can identify which interactive element is currently selected while navigating with the keyboard.
Users should be able to move through key site functions using common keyboard controls such as the Tab and Shift + Tab keys.
5. Screen readers and page structure
The website uses HTML structure intended to help assistive technologies interpret page content more clearly.
This includes page landmarks, headings, navigation labels, meaningful link text and form labelling.
Decorative images should not create unnecessary noise for screen-reader users, while meaningful visual content should provide appropriate alternatives.
6. Text size and browser zoom
Visitors should be able to use browser zoom to increase the size of page content without losing access to important information or controls.
The responsive layout is designed to adapt as the available viewing area becomes smaller.
Users can also adjust browser and operating-system settings according to their own visual preferences.
7. Colour and visual presentation
EarlyBridge uses a restrained visual palette with strong contrast between text and background areas.
Information should not rely solely on colour to communicate meaning wherever practical.
Buttons, headings, links and content areas are designed to remain visually distinguishable across the site.
8. Motion and animation
The EarlyBridge website intentionally avoids heavy animation and unnecessary motion.
Where movement or transitions are used, the design should respect user preferences for reduced motion where technically possible.
This supports users who may find excessive motion distracting, uncomfortable or difficult to process.
9. Forms and enquiries
Website forms are intended to use clear labels, meaningful field names and straightforward instructions.
Users should not need to rely on placeholder text alone to understand what information is being requested.
Error messages and validation should be presented clearly so that users can understand what needs to be corrected.
10. Mobile and smaller screens
The website is designed to adapt to smaller screens and mobile devices.
Navigation, cards, forms and content sections should stack appropriately rather than requiring unnecessary horizontal scrolling.
Touch targets should also remain practical for users accessing the site from phones and tablets.
11. Plain and understandable language
Accessibility is not only about technical features. It also involves making information easier to understand.
EarlyBridge aims to use plain, reassuring language and to avoid unnecessary clinical or bureaucratic terminology.
Where specialist terms are necessary, the surrounding content should provide enough context to help users understand what they mean.
12. PDFs and downloadable documents
If EarlyBridge introduces downloadable documents in the future, accessibility should be considered as part of their preparation.
This may include appropriate heading structure, readable text, meaningful document order and accessible alternatives where needed.
13. Third-party content
Some website features may in future depend on third-party services, such as booking systems, embedded media, payment providers or external forms.
EarlyBridge may not have complete control over the accessibility of externally provided tools.
Where third-party services are added, accessibility should be considered during selection and implementation.
14. Known limitations
Accessibility can be affected when content, technology or third-party tools change.
The website should therefore be retested after significant design changes, new integrations or major content updates.
Any identified barrier should be reviewed and, where reasonably possible, improved.
Ongoing review
Accessibility should be considered whenever new pages, images, forms, videos, documents or third-party tools are introduced.
15. Accessibility testing
The website should be reviewed using more than one method. No single automated tool can identify every accessibility issue.
Useful checks may include:
- keyboard-only navigation;
- browser zoom and text enlargement;
- mobile and tablet testing;
- visible focus testing;
- colour contrast checks;
- form label and error-message review;
- screen-reader testing where possible; and
- automated accessibility audit tools.
16. Requesting information in another format
If information on the website is difficult to access, visitors may contact EarlyBridge to discuss whether the information can reasonably be provided in another format.
The appropriate format will depend on the information being requested and the needs of the individual.
Requests can be made through the website contact page.
17. Reporting an accessibility problem
EarlyBridge welcomes feedback about accessibility barriers.
If you experience difficulty using a page, link, form or other part of the website, please explain the issue and, where possible, identify the page or feature involved.
This information can help identify and prioritise improvements.
18. Future improvements
The EarlyBridge website may continue to develop as the service grows.
Future improvements should continue to consider accessibility alongside performance, privacy, safeguarding and usability.
Significant new features should be reviewed before launch to reduce the risk of introducing unnecessary barriers.
19. Review of this statement
This Accessibility Statement should be reviewed when major website changes are made or when accessibility issues are identified.
It should reflect the website and services actually available rather than describing features that are no longer in use.
Accessibility note: EarlyBridge aims to provide a clear and inclusive digital experience. Accessibility testing should continue as the live website, content and any third-party services develop.