GlobalXess
Login Sign up
Legal

Accessibility statement

Global Premium Telecom B.V. is committed to making globalxess.com usable by as many people as possible. This statement explains the conformance target we aim for, the measures we take, the limitations we know about, and how to tell us when something on the site doesn't work for you.

# 1. Conformance status

We aim to conform with the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. This is the level referenced by the EU European Accessibility Act (Directive (EU) 2019/882) and the EN 301 549 harmonised standard.

The statement reflects the state of the website as of the "Last updated" date in the sidebar. We re-test the site after any major release.

Current self-assessed status: the site partially conforms to WCAG 2.2 AA. Most content meets the AA criteria; the items in § 5 below are the known gaps and our plan for closing them.

# 2. Measures we take

To support accessible use we have built the site as follows:

  • Semantic HTML - one <main> per page, headings in document order, lists for lists, real form labels and validation messages.
  • Skip-to-main-content link on every page so keyboard and screen-reader users can jump past the navigation.
  • Visible keyboard focus on every interactive element, including the mega-menu, the locale switcher and the form fields.
  • Colour contrast meeting at least 4.5:1 for body text and 3:1 for large text and UI controls, validated against the WCAG 2.2 AA thresholds.
  • Responsive layout that re-flows down to a 320 px viewport width without loss of content or functionality.
  • Form labels and validation tied programmatically to their inputs (label[for] + id), with inline error messages exposed to assistive tech.
  • Alt text on meaningful images; decorative images are marked with empty alt attributes so screen readers skip them.
  • No motion-based content that flashes or auto-plays; users keep full control of the page.
  • JavaScript is enhancement, not requirement: the primary content of every page is readable with JavaScript disabled.

# 3. Compatibility with assistive technology

The site is built and tested to work with the latest two versions of:

  • Chrome, Firefox, Safari and Microsoft Edge on macOS, Windows and Linux.
  • Safari on iOS and Chrome on Android.

And with the following assistive technologies in their currently-supported releases:

  • VoiceOver on macOS (Safari) and iOS (Safari).
  • NVDA and JAWS on Windows (Chrome and Edge).
  • TalkBack on Android (Chrome).
  • System-level keyboard-only navigation.

# 4. Technical specifications

Accessibility relies on the following technologies working with your browser and any assistive technologies or plugins installed on your device:

  • HTML5 (semantic landmarks)
  • WAI-ARIA where it adds value beyond plain HTML
  • CSS for visual presentation
  • JavaScript for progressive enhancements only (mega-menu, mobile drawer, form validation feedback)
  • SVG for the world map and inline icons

# 5. Known limitations

We are aware of the following limitations and are actively working on them:

  • Interactive world map (coverage page). The SVG map shows where we have live coverage. The same information is also presented as a fully accessible region-grouped list of countries directly below the map. Screen-reader users get the complete set; users with reduced motion don't need to interact with the map at all.
  • Decorative blog imagery. The hero image on each blog card is decorative and uses an empty alt attribute, so it is not announced by assistive tech. The card's title and excerpt carry the meaning.
  • Long-form numerical tables (coverage detail pages). Where we list area codes and rates, the table includes column headers but currently no row-level scope attributes. We are reviewing the markup as part of the next accessibility audit.

If you spot something not on this list, please tell us - see § 6 below.

# 6. Feedback and contact

We welcome feedback on the accessibility of the site. If something doesn't work for you, or you need a piece of content in an alternative format, please email us:

Accessibility contact: support@globalxess.com
Subject line: "Accessibility feedback"
Response target: within 5 business days.

Please include the URL of the page you were using, what you were trying to do, and what happened (or didn't happen). Tell us which browser and assistive technology you use if you can - that helps us reproduce the issue quickly.

# 7. Formal complaint

If you are not satisfied with our response to an accessibility feedback message you can lodge a complaint with the relevant national authority. In the Netherlands the competent body is the College voor de Rechten van de Mens (mensenrechten.nl). Other EU Member States have equivalent bodies under the European Accessibility Act.

# 8. Approval

This statement was last reviewed on 14 May 2026 and approved by the GlobalXess operations team. The next scheduled review is six months after this date or after the next major release of the website, whichever comes first.