Accessibility statement

Conformance target

The site is built to meet the Web Content Accessibility Guidelines version 2.2 at Level AA. That standard is the benchmark most public bodies and enterprises in the United Arab Emirates and internationally use to judge whether a digital service is accessible. We design and develop against it across every page, every locale and every interactive component.

What we do

The measures below are built into the site:

• Semantic HTML is used first, so headings, landmarks, lists and forms convey structure to a screen reader without relying on visual styling. ARIA is added only where the native semantics genuinely fall short.
• Every interactive element is reachable and operable by keyboard alone, with a visible high-contrast focus ring, and skip links let a keyboard or screen reader user jump straight to the main content.
• Colour contrast is checked against the WCAG AA thresholds on both the light and the dark surfaces the site uses, and information is never conveyed by colour alone.
• Every image carries meaningful alternative text in the language of the page, and images that are purely decorative are marked so assistive technology skips them.
• Forms label every field, announce errors to assistive technology, and describe how to fix an error rather than only stating that one occurred.
• Interactive features, including the calculators, the team builder, the filters and the timelines, are keyboard operable and carry meaningful content even without JavaScript.
• All motion respects the reduced-motion preference: when a visitor asks their system to reduce motion, animations are disabled and the final state is shown immediately.
• Text can be resized to 200 percent without loss of content or function, and touch targets meet the minimum size for comfortable use on a phone.
• The Arabic experience is a first-class right-to-left layout, mirrored correctly, and tested as its own experience rather than as an afterthought.

How we test

Accessibility is checked in several ways. Automated checks run against the pages to catch common failures. Beyond automation, which cannot judge everything, the site is reviewed by keyboard alone, with a screen reader, and at a range of screen sizes down to a small phone, in both English and Arabic. Interactive components are tested individually, because a component that passes in isolation can still fail in context.

Automated tools do not catch every barrier, so a passing automated result is treated as a floor and not as proof of conformance. Where a human review finds an issue an automated tool missed, the human review takes precedence.

Known limitations

We aim for full conformance, and we are honest about the fact that a large site is never finished. Some content that comes from third parties, such as an embedded scheduling widget or a video hosted elsewhere, is outside our direct control, and its accessibility depends on the provider. Where a third-party component falls short, we provide an accessible alternative route to the same outcome, for example a form or a direct contact channel in place of an embedded widget. Any specific limitation we are aware of at a point in time is corrected as a priority.

Tell us about a problem

If you meet a barrier on corpshore.ae, or you need information from the site in a different format, please tell us. We treat accessibility reports as a priority and we will work with you to give you the information or the service you were trying to reach. Contact us at info@corpshore.ae and describe the page and the problem, and we will respond promptly.

This statement will be updated as the site changes and as we complete further review. The date at the top reflects the most recent update.