Accessibility Statement

CISS Geo2go aims to meet WCAG 2.2 Level AA. AAA criteria are implemented where they are practical for the map-first workflow. This statement covers the customer-facing shop, catalog, checkout, orders and map selection.

This is an implementation statement, not a formal external conformance audit. The automated checks and manual checks listed below are part of the release process and do not replace testing with people who use assistive technology.

• All form controls, links and dialogs are keyboard operable.
• Visible focus indicators, skip navigation and logical heading structure are provided.
• Dynamic price, cart, order and map changes are announced through live regions.
• Touch targets are at least 44 × 44 CSS pixels where controls are used.
• Animations respect prefers-reduced-motion.
• The product map can be operated without a mouse after the map receives focus.

1. Focus the map with Tab.
2. Select a drawing tool with the map toolbar.
3. Move the keyboard pointer with the arrow keys. Hold Shift for smaller steps.
4. Press Enter to place points. Press Enter once more after the minimum number of points to finish the geometry.
5. Press Escape to cancel an unfinished drawing.

The map announces tool changes, pointer movement, placed points and completion through a polite status region. The workflow supports points, lines, polygons, rectangles, routes and cadastral frame selection.

The repository contains:

• Playwright Axe-core checks in frontend/tests/accessibility.test.ts;
• unit tests for keyboard shortcuts and keyboard drawing in frontend/src/lib/map/;
• Lighthouse checks for accessibility and page quality;
• code review checks for labels, focus order, reduced motion and minimum touch targets.

Manual verification should include keyboard-only navigation and VoiceOver on macOS. NVDA or JAWS should be used for Windows-specific verification before a formal accessibility declaration is issued.

• Complex WFS feature-selection workflows still require additional assistive technology testing.
• Map content from external providers may have accessibility limitations that CISS cannot fully control.
• This statement does not claim that every third-party dataset or document is accessible.

Accessibility problems can be reported through the shop contact route. Include the affected URL, the interaction that failed, the browser and assistive technology if applicable. Reports are triaged with the same priority as other customer-blocking defects.