Built into the interface
Semantic structure, keyboard operation and visible focus states are part of the Core PHP design system.
Corporate information
Accessible digital service
The Core PHP website is designed with semantic HTML, keyboard navigation, visible focus states, responsive layouts and form labels intended to support a broad range of users and devices.
Responsive by default
Content and forms are designed to remain usable across desktop, tablet and mobile layouts.
Feedback welcomed
Accessibility difficulties can be reported through a dedicated option in the secure contact form.
01 / Corporate information
Accessibility approach for the public website
The website has been designed toward WCAG 2.2 Level AA principles, including clear landmarks, logical headings, meaningful labels, keyboard-accessible controls and reduced-motion support. Automated and manual checks form part of release validation, but no website should claim perfection without ongoing real-user testing.
- A skip link provides direct access to the main content
- Navigation and form controls expose names and states to assistive technology
- Focus indicators and colour contrast are included in the corporate component styles
- Form errors are presented in text and are not communicated by colour alone
02 / Corporate information
Known boundaries and requesting support
External services reached from the public website, including the Client Area and third-party documents, may have separate accessibility arrangements. If any content or process is difficult to use, provide the page and the task you were trying to complete so an alternative route can be considered.
- Use the contact form and select “Website accessibility”
- Describe the device, browser or assistive technology where relevant
- Do not include passwords or private account credentials
- Account-specific help should be requested through the secure Client Area
Who this information supports
Where this policy applies
The applicable order and service documents remain important where the enquiry or account relates to a purchased service.
Keyboard-only navigation
Screen-reader use
Mobile and zoomed layouts
Visitors requesting an alternative contact route
Clear answers
Frequently asked questions
These answers explain the public policy at a practical level. Account-specific matters should use the secure Client Area.
Does the website support keyboard navigation?
The navigation, links, forms and disclosure controls are designed to work by keyboard, with visible focus indicators.
Can I request information in another accessible format?
Use the accessibility option on the contact form and explain what content or format is required. BLCS Global will consider a practical alternative.
Does this statement cover the Client Area?
The Client Area is a separate application and should be assessed under its own interface and release process.
Continue exploring
Related infrastructure and guidance
Need clarification?