Semantic content
Pages should use meaningful headings, landmarks, labels and reading order so information does not depend only on visual position.
Access is part of the build
Make the information and action usable by more people.
GA Applications works to make this website perceivable, operable, understandable and robust across a practical range of devices, browsers and assistive technologies. Accessibility is an ongoing design, content and engineering responsibility rather than a one-time certification claim.
Help us reproduce the barrier
Include the page, task and technology.
Tell us the page address, what you were trying to do, what happened, and—if you are comfortable sharing it—the browser, device or assistive technology involved. Do not include passwords, payment details or other sensitive information.
01 / APPROACH
Standards guide the work; user experience tests it.
We use the Web Content Accessibility Guidelines as a reference point and aim for WCAG 2.2 Level AA across the main GA Applications experience where reasonably practicable.
Keyboard and focus
Core navigation and controls should be available without a pointer, with visible focus and understandable control names.
Contrast and motion
Text and controls should remain readable, while important experiences provide reduced-motion or silent choices where relevant.
02 / SCOPE
What this statement covers.
This statement covers the main pages published at gaapplications.com. Independent concept previews and imported experimental work may use separate design systems and can contain additional limitations.
Shared navigation and service pages
We review the common shell, primary service journeys, industry pages, Work routes, contact paths and policy pages.
Separate experimental sites
Concepts are clearly labelled and may not yet meet the same standard as the main website. Their exit and feedback routes should remain available.
External platforms
Embedded media, maps, forms, payment, booking or other third-party services can have accessibility behaviour outside our direct control.
03 / SUPPORT
Ask for another usable route.
If a page or feature prevents access, contact us. We can investigate the barrier and, where reasonably possible, provide the information or service through another format or assisted route.
hello@gaapplications.com
Use the subject “Accessibility feedback” and include the affected page or task.
Send accessibility feedbackShare only what is needed
You do not need to disclose a disability. Describe the barrier and preferred response method; avoid sending sensitive information.
Read the privacy noticeLast reviewed 22 July 2026
This statement and the website will be reviewed as significant content, navigation and interaction systems change.
Accessibility feedback
Tell us what stopped you completing the task.
We will use the page, action and environment details to reproduce the barrier and decide the appropriate correction or alternative route.