Inclusive digital experience
Accessibility Statement
Effective date: 21 August 2026 | Last updated: 21 August 2026 | Version 1.0
Accessibility at a glance
Percepta Growth is committed to providing a professional digital experience that is usable by the widest practical range of people, including people who use assistive technologies or experience visual, auditory, motor, speech, cognitive or neurological barriers.
| Item | Details |
|---|---|
| Organisation | Percepta Growth, operated by Percepta Advisory & Strategy Ltd |
| Website | https://perceptagrowth.com |
| Target standard | Web Content Accessibility Guidelines (WCAG) 2.2, Level AA |
| Current status | Not yet formally assessed. This Statement does not claim full or certified conformance. |
| Assessment approach | Design and development self-evaluation, followed by planned manual and assistive-technology testing. |
| Feedback contact | hello@perceptagrowth.com |
Our standard: accessibility is treated as an ongoing operating responsibility, not a one-time badge. We aim to prevent barriers during design and development, test critical journeys, respond constructively to feedback and provide a reasonable alternative when a barrier cannot be resolved immediately.
1. Commitment and scope
This Accessibility Statement applies to perceptagrowth.com and the public web pages, forms and digital content controlled by Percepta Growth on that domain. It describes our target, present assessment status, design measures, known areas of risk, feedback process and approach to improvement.
It does not automatically cover third-party websites, platforms or content that we link to but do not control. Where a third-party tool is embedded into our experience, we seek an accessible implementation and offer an alternative route where reasonably practicable.
2. Accessibility standard and status
2.1 Target standard. Our target is conformance with WCAG 2.2 at Level AA. WCAG is an internationally recognised technical standard organised around content being perceivable, operable, understandable and robust.
2.2 Current conformance status. The website has not yet completed a documented, representative accessibility evaluation against every applicable WCAG 2.2 Level A and AA success criterion. Its present status is therefore Not Assessed rather than fully or partially conformant. This is an intentionally cautious statement and will be updated after a formal evaluation.
2.3 No certification claim. Use of WCAG terminology, accessibility techniques or automated testing does not mean the website has been certified by W3C or another organisation. Automated tools can identify some issues but cannot establish full conformance on their own.
3. Measures to support accessibility
Our website standard is designed to incorporate the following measures:
- use semantic HTML and a logical heading hierarchy;
- provide keyboard access to navigation, menus, controls, forms and dialogs;
- maintain visible focus indicators and avoid obscuring the focused element;
- use sufficient colour contrast and avoid relying on colour alone to communicate meaning;
- provide text alternatives for meaningful images and hide decorative images from assistive technology;
- associate form fields with clear labels, instructions and understandable error messages;
- support responsive reflow and text enlargement without loss of essential content or functionality;
- use descriptive link and button labels that make sense in context;
- respect reduced-motion preferences and avoid unnecessary flashing or autoplay;
- provide captions, transcripts or another alternative for meaningful time-based media where applicable; and
- review major templates and critical journeys before publication and after material changes.
4. Core experience standards
| Area | Percepta Growth standard |
|---|---|
| Navigation | Consistent page structure, skip access where appropriate, meaningful page titles and keyboard-operable menus. |
| Visual design | Strong contrast, readable type, restrained motion, clear spacing and no essential information conveyed only by colour. |
| Forms | Programmatic labels, clear requirements, accessible validation, error identification, focus management and a non-visual success state. |
| Interactive controls | Native controls where possible, visible focus, accessible names, sufficient target size and no keyboard traps. |
| Images and graphics | Purposeful alternative text for meaningful images; decorative assets omitted from the reading order. |
| Documents | Legal and important information published as structured HTML where practicable; accessible alternatives available on request. |
| Motion and media | Reduced-motion support, user control over movement and captions or transcripts for material audio or video. |
| Language and content | Plain, direct language, defined technical terms and consistent instructions appropriate to a professional audience. |
5. Technical specifications
Accessibility of the website relies on the following technologies working with the visitor's browser and any assistive technology or plug-ins:
- HTML for structure and semantics;
- CSS for presentation, responsive layout, contrast and focus styling;
- JavaScript for menus, form validation, consent controls and other interactive functions; and
- WAI-ARIA only where native HTML does not provide the required name, role, state or relationship.
Where JavaScript is essential to a requested function, we aim to provide a clear state, error message or alternative route. We avoid using ARIA to replace appropriate native elements.
6. Compatibility expectations
The website is intended to work with current stable versions of major browsers on desktop and mobile devices and with commonly used assistive technologies supported by those environments. We do not yet claim verified compatibility with a specific browser, operating-system and screen-reader matrix because representative manual testing has not been completed.
Very old browsers, unsupported operating systems, aggressive script blocking, custom style overrides or third-party browser extensions may affect presentation or functionality. This does not remove our responsibility to address barriers within the website we control.
7. Assessment and maintenance
7.1 Current approach. The initial approach is self-evaluation by the website owner and development team, using a combination of code review, automated checks and manual review. Automated testing is treated as a screening tool rather than proof of conformance.
7.2 Planned evaluation. Before representing the website as conformant, we plan to evaluate a representative sample of pages, components and user journeys, including navigation, service pages, forms, legal pages, consent controls and the booking path. Testing will include keyboard-only use, zoom and reflow, contrast review, screen-reader checks and error recovery.
7.3 Ongoing review. Accessibility is reviewed after material design or platform changes, new forms, new embedded services and significant content releases. This Statement is reviewed at least annually even where no material change is identified.
8. Present limitations
Because a full evaluation is pending, additional barriers may exist. The areas below require particular attention and are not statements that every listed issue is present.
| Area | Potential limitation | Alternative or response |
|---|---|---|
| Third-party scheduling | An embedded scheduling interface may not provide the same keyboard, screen-reader or contrast experience as the main website. | Open the provider in a separate page or email hello@perceptagrowth.com to arrange a call. |
| Downloadable PDFs | A PDF may not expose headings, reading order, tables or links as effectively as a structured web page. | Use the HTML policy page where available or request an accessible text or document version. |
| Third-party media | Externally hosted video, audio, maps or social content may have incomplete captions, transcripts or controls. | Request the material or essential information in an alternative format. |
| New or changed content | A newly published component may contain an issue not identified during release review. | Report the page and task affected so we can prioritise a repair or provide another route. |
Need an alternative? If a barrier prevents you from accessing information, submitting an enquiry or booking a call, email hello@perceptagrowth.com. Tell us the page, the task you were trying to complete, the format you need and any assistive technology involved if you are comfortable sharing it. You do not need to disclose a diagnosis.
9. Third-party services and content
Links may lead to independent websites, advertising platforms, social networks or service providers. We cannot control their accessibility. For embedded services that form part of a critical journey, we will seek a reasonable alternative under our control when a barrier is reported or identified.
10. Accessibility feedback and assistance
We welcome specific feedback because it helps us identify barriers that technical checks may miss. When contacting us, include enough information to reproduce the issue, but do not send sensitive medical information or identity documents.
We aim to acknowledge accessibility feedback within five business days. Where the issue is within our control, we will assess its severity, identify a practical alternative where needed and communicate the expected next step. Complex issues involving third-party providers or substantial redevelopment may take longer.
11. Complaints and escalation
If you are dissatisfied with the initial response, reply using the subject line Accessibility Escalation and explain the outcome you need. The matter will be reviewed separately from the initial handling where practicable. Nothing in this process limits any right or remedy available under applicable law.
12. Changes to this Statement
We may update this Statement after an audit, remediation, platform change, new third-party integration or change in applicable standards. We will revise the effective and last-updated dates and will describe a material change where doing so would help users understand the website's status.
13. Contact
Accessibility contact — use the subject line: Accessibility Feedback.
Percepta Growth, operated by Percepta Advisory & Strategy Ltd
hello@perceptagrowth.com
https://perceptagrowth.com
Appendix A — Accessibility operating standard
The following schedule defines the minimum internal control expected for the website. It is adapted as the site's functionality expands.
| Stage | Control |
|---|---|
| Design | Define keyboard behaviour, focus order, contrast, responsive states, errors, motion and content alternatives before development. |
| Development | Use semantic HTML first, label controls, preserve zoom and reflow, manage focus and test interactive states without a mouse. |
| Content | Apply logical headings, descriptive links, meaningful alt text, plain instructions and captions or transcripts where required. |
| Release review | Check critical journeys using keyboard-only navigation, automated tools, contrast review, zoom, reflow and at least one screen-reader workflow. |
| Third-party procurement | Review accessibility information for embedded and critical providers, document limitations and maintain an alternative route. |
| Issue triage | Prioritise barriers that block access, navigation, form submission, legal information or booking; provide an interim alternative. |
| Evidence | Record pages tested, environments, methods, findings, owners, remediation and retest results. |
| Governance | Review this Statement at least annually and after material changes. Do not claim conformance without documented representative evaluation. |
Appendix B — Standards and reference materials
This Statement was informed by the following public W3C Web Accessibility Initiative resources. W3C does not endorse Percepta Growth, and this Statement is not a W3C certification.
- W3C Web Content Accessibility Guidelines (WCAG) 2.2: https://www.w3.org/TR/WCAG22/
- W3C WCAG 2 Overview: https://www.w3.org/WAI/standards-guidelines/wcag/
- W3C How to Meet WCAG 2.2 Quick Reference: https://www.w3.org/WAI/WCAG22/quickref/
- W3C Accessibility Statement Generator and guidance: https://www.w3.org/WAI/planning/statements/generator/