Google Opens an Accessibility Discovery Centre in Warsaw, Its First in Central and Eastern Europe

Google opened its ninth Accessibility Discovery Centre on October 8, 2026, this time in Warsaw. It is the company's first such facility in Central and Eastern Europe, a region that has largely sat outside the orbit of Big Tech's accessibility research.

The centre sits inside Google's Warsaw office at Rondo Ignacego Daszyńskiego 2C and joins a network of similar spaces in London, Zurich, Munich, Milan, Paris, New York, Dubai, and São Paulo. The formula is the same at every site: bring people with disabilities, non-profit organisations, researchers, developers, and public institutions into one room with the engineers building the products, and test technology before it ships, not after.

A testing lab, not a showroom

The Warsaw centre will host workshops, product testing sessions, hackathons, and software bug-finding events, according to the opening announcement. The emphasis matters. These centres are not marketing exhibits; they are working spaces where disabled testers are involved in the process and their feedback feeds directly into product teams.

That co-design model has a history at Google. The first Accessibility Discovery Centre opened in London, built in partnership with organisations such as the Royal National Institute of Blind People, and the network has since expanded city by city. Each centre adapts to its local ecosystem: the Warsaw site is explicitly positioned to work with Polish non-profits, researchers, developers, and public institutions, which means Polish-language accessibility gets attention it rarely receives from global product teams.

The timing is not accidental. Poland has implemented the European Accessibility Act, whose requirements for specified products and services took effect on June 28, 2025, subject to exemptions and transitional provisions. Companies selling into the EU now face binding obligations on digital accessibility, and a testing facility in Warsaw gives Google both a compliance foothold and a regional pool of accessibility professionals.

What visitors will actually touch

The demonstrations on offer at the opening show where Google's accessibility engineering is currently pointed: alternative input and AI-generated descriptions.

ChromeOS Face Control lets users navigate a computer with head movements and facial expressions, an approach aimed at people who cannot use a mouse, keyboard, or touchscreen comfortably. Look to Speak converts eye-selected words into speech, a tool for people who communicate through eye gaze. Live Transcribe turns spoken words and some environmental sounds into text on screen, something many deaf and hard-of-hearing users rely on daily.

On Pixel phones, Guided Frame provides audio and haptic guidance for framing photographs, giving blind and low-vision photographers feedback on whether the subject is centred and how many faces are in shot. Google also highlights AI-generated descriptions of images through TalkBack and Gemini, which narrate the contents of photos and on-screen graphics.

Testing technology with disabled people before it ships is the whole point of the centre. Products improve faster that way than any accessibility checklist could ever manage.

The honest caveat

Google itself notes an important limitation: automatically generated image descriptions can be inaccurate and should not be treated as definitive. That candour is worth sitting with. AI vision descriptions are probabilistic guesses, and when a blind user relies on one to read a chart, a label, or a photo, a confident error is worse than silence.

This is precisely why in-person testing centres matter more than the press cycle around them. Automated captioning and description tools are improving, but they still fail in exactly the situations where accuracy counts most: unusual lighting, low-contrast interfaces, cultural context, and images that depend on tone rather than objects. The reliable way to find those failures is to put the tools in the hands of the people who depend on them, watch what breaks, and fix it.

The Warsaw centre's bug-finding events formalise that loop. Instead of waiting for complaints to surface through support channels, product teams invite testers to hunt for defects in pre-release software. It is a small shift in process, and it changes who gets to define "working."

Why Warsaw changes the map

The World Health Organization estimates that more than 1.3 billion people live with significant disabilities. Most of them do not live in London, New York, or Zurich. They live in places like Poland, Romania, and Hungary, countries where accessibility testing infrastructure has historically been thin and where many global products ship with localisation gaps.

A centre in Warsaw does not fix that overnight. But it puts Google's accessibility research within reach of the disabled communities, universities, and start-ups of an entire region, and it gives Polish public institutions a venue to test whether their own digital services hold up under the European Accessibility Act.

Organisations interested in visiting or collaborating can contact the centre directly. Google has not disclosed the project's budget or staffing levels, which is worth noting: the centres are inexpensive compared to the company's research budgets, and their value depends entirely on whether the feedback loop stays open after the opening week.

For now, the signal is a simple one. Accessibility stopped being a side project at the platform companies years ago. It is now infrastructure, with buildings, staff, and regional strategy behind it. Warsaw is just the latest pin in that map, and likely not the last.