Our unattended kiosk uses react js but is a fully closed system. What WCAG 2.2 AA applies to us?

[bopete1313]

Hi,

We run chromium in kiosk mode on our unattended kiosks. The customer facing UI uses react js and the customer navigates through the UI to dispense their product. It's ran by a touch screen without any mouse.

What WCAG 2.2 AA rules apply to us? Some of these seem to really not apply but it's hard to say for sure.

[mraccess77]

EN 301 549 (Clause 11 covers how the WCAG requirements can be applied to software with closed functionality (software where the user can't use their own assistive technology).

[bopete1313]

Thanks for linking that @mraccess77. I read through, but it's still unclear to me if we'd need to bundle in a TTS system or on screen navigation arrows. Do you know if we're required to add that?

We use a browser (chromium) but it's totally locked down in Kiosk mode.

I also read WCAG2ICT, but it's still pretty unclear to me. Thanks in advance, the legal wording of this stuff is super complex.

[GreggVan]

If you are running a kiosk -- you are running a closed product.

So neither WCAG nor WCAG2ICT apply (since neither deals with closed products)

Best is to look at EN 301 549 but you can view the latest at https://labs.etsi.org/rep/HF/en301549/-/issues/219

Pull down the CLEAN version that is there.

There is also a tool there that helps you eliminate rules that would not apply to you.

It is being revised and t

[TestPartners]

Best is to look at EN 301 549 but you can view the latest at https://labs.etsi.org/rep/HF/en301549/-/issues/219

This is a draft version that is not yet in force. The current version is 3.2.1, which only contains WCAG 2.1 success criteria. When the new version is published, it will include WCAG 2.2, so it's worth looking at the draft version even though it may change. I was expecting it to be published before 28 June 2025 when the European Accessibility Act came into force, but it wasn't and there doesn't appear to be a timetable for publication.

[mraccess77]

For closed functionality products there are requirements in clause 5 for speech output - and also some in clause 11. You can meet that requirements different ways though by bundling a screen reader, building in your own TTS, or some other way which meets the requirements outlined for speech output.

[GreggVan]

PS
The new EN 301 549 is in final review stages. I think it goes out for final vote in September if I remember correctly.

As noted above -- the latest draft will always be at https://labs.etsi.org/rep/HF/en301549/-/issues/219

[bruce-usab]

@bopete1313 if your kiosk was owned/operated by a U.S. government entity, under Section 508 you would want to primarily be using 402 Closed Functionality. An informal approach is to design the kiosk so that you, as the developer (i.e., someone who knows the product quite well) can operate it while blindfolded.

Almost certainly, that means TTS and at least some physical keys. On-screen navigation arrows are hard to make workable for someone who cannot see. WCAG and even WCAG2ICT do not go into the detail that is needed for hardware accessibility.