Accessibility

Accessibility statement

CODE BARRES BARCODE is committed to making Lobbly accessible in accordance with RGAA 4.1.2, the French accessibility reference framework for digital services.

Compliance status

Accessibility: non-compliant.

This provisional statement does not publish a compliance percentage because no complete, reproducible audit of all applicable RGAA criteria and authenticated product states is currently available. The service is therefore declared non-compliant until that audit has been completed and independently retested.

Scope of this statement

This statement applies to the public website at https://www.lobbly.io/, the authentication flow, the workspace playground, the admin console and the map editor.

Audit sample

• Public landing page.
• Authentication, signup, workspace creation and invitation screens.
• Legal, privacy, terms, cookies and accessibility pages.
• Workspace playground shell, including modals, menus, participant lists and room panels.
• Admin console shell, members, invitations, rooms, billing and workspace settings views.
• Map editor shell, toolbar, side panels and room editing controls.

Non-accessible content

• The 2D playground canvas does not yet provide a complete keyboard equivalent for spatial movement and map interaction.
• The map editor canvas remains pointer-first for tile painting, camera movement and some shape editing workflows.
• Live audio and video conversations do not yet provide integrated live captions or transcription.
• Some visual canvas effects, such as path previews, particles and room membranes, have no exact non-visual equivalent yet.

Conforming improvements already implemented

• Modal dialogs now expose dialog semantics, labels, escape handling and focus management.
• Authentication forms expose inline errors to assistive technologies and associate messages with fields.
• Custom menus, presence selectors and room customization selectors support keyboard navigation.
• People and room lists expose clearer labels and keyboard entry points for contextual actions.
• Status messages used in settings, invitations and room customization are announced politely.
• Automated checks are used for regression detection but are not presented as proof of RGAA compliance.

Accessibility roadmap 2026-2028

• 2026: secure the public website, authentication, admin console and settings flows.
• 2026: document and improve keyboard alternatives for the spatial playground and map editor.
• 2027: improve live meeting accessibility, including captions, device states and audio/video alternatives.
• 2027: run assistive technology validation with NVDA, VoiceOver and browser combinations used in the RGAA reference base.
• 2028: maintain accessibility checks as part of product delivery and feature acceptance.

2026 action plan

• Maintain zero confirmed axe-core violations on public and authenticated HTML interfaces.
• Finalize a product decision for keyboard use of the playground canvas.
• Add keyboard-first alternatives for key map editor operations.
• Review contrast manually when gradients, sprites or canvas rendering prevent automated validation.
• Prepare live meeting accessibility improvements, including captions feasibility.

Technologies used

Lobbly uses HTML, CSS, JavaScript, SVG, Canvas and WebRTC. The service is designed for modern browsers.

Feedback and contact

If you cannot access a feature or content, contact us at bonjour@lobbly.io. Please describe the page, the issue encountered, your browser and the assistive technology used when relevant.

Recourse

If an accessibility issue prevents you from accessing content or a service, you have reported it to us and have not received a satisfactory response, you may write to the French Defender of Rights, contact a regional delegate, or send a postage-free letter to: Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07, France.

Statement preparation

This provisional statement was prepared on 2026-07-11 following a pre-audit using RGAA 4.1.2, automated browser checks, keyboard navigation checks and source review. No assistive technology test has yet been used to calculate an official compliance rate.

Established and last updated: 2026-07-11.