ZipCodeGlobe aims for WCAG 2.2 AA intent across core search, lookup, tools and administration.
Measures
The site uses semantic landmarks, a skip link, visible keyboard focus, labelled forms, error associations, reduced-motion support, responsive tables and touch targets designed for mobile use. Search autocomplete follows combobox and listbox behaviour while the submitted form remains usable without JavaScript.
Known limits
Third-party map content and future advertising or consent interfaces may have accessibility characteristics outside our direct control. Postal place names can also contain scripts unfamiliar to assistive pronunciation tools.
Feedback
Email hello@zipcodeglobe.com or use the contact form with the page URL, assistive technology and task you were trying to complete. We will prioritise barriers in core flows.
Design and development approach
Core pages are server rendered so search, country browsing, postal results and explanatory content remain available when JavaScript fails or is disabled. JavaScript adds autocomplete, copy controls, consent choices and progressive form behaviour without replacing the underlying HTML. Layouts are designed from 320 pixels upward, avoid horizontal scrolling, reserve space for media, and use touch targets intended to be usable on mobile devices.
Keyboard and assistive technology
A skip link, landmarks, logical headings, visible focus states and labelled controls support keyboard and screen-reader navigation. Autocomplete uses combobox and listbox semantics, while submitting the ordinary search form remains an equivalent route. Tables include headings and responsive handling. Status is communicated with text or icons as well as colour. Motion is reduced or removed when the user expresses a reduced-motion preference.
Content accessibility
Postal codes and coordinates use readable text rather than being embedded only in images. Images and author marks include alternative text, while decorative graphics are hidden appropriately. Link purpose should be understandable from surrounding context. Error messages are associated with the relevant fields and do not rely solely on colour. Country flags supplement, rather than replace, country names.
Known external constraints
OpenStreetMap frames, future advertising and a future certified consent platform may have accessibility behaviour outside the application’s direct control. Those features are optional and must not block the core answer. Place names in many scripts can be pronounced differently by assistive technologies, and source data may not include local-language pronunciation guidance. The site avoids fabricating transliterations to compensate.
Feedback and remediation
Report a barrier through the contact page or hello@zipcodeglobe.com. Include the page URL, task, browser, operating system and assistive technology, but do not include passwords or private customer data. Core lookup and form barriers receive priority. A report may lead to a code correction, content clarification or documented limitation when the issue belongs to an external service.