1. Our commitment
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA in the Pogama desktop app and on pogama.xyz. Accessibility is one of the rules every change to Pogama must follow, and we take the European Accessibility Act (Directive (EU) 2019/882) and the standard EN 301 549 as our reference.
2. Conformance status
Partially conformant: we design and build for WCAG 2.2 AA, but Pogama has not yet been audited by an independent third party, and some parts don't fully conform yet (see “Known limitations”). This statement was prepared on the date shown above by self-assessment.
3. What we do on pogama.xyz
- A “Skip to content” link, real headings and landmarks, and labels on every control and navigation area.
- Everything works with a keyboard, with a visible focus indicator.
- Text colors are chosen for a contrast of at least 4.5:1 against the background.
- If your system asks to reduce motion, animations and scroll effects are reduced and the 3D scene stays still. Small screens and devices that can't run WebGL get the same content with a lighter, non-3D version.
- The site is available in English and Spanish, with the language declared on each page, and the layout adapts to browser zoom and narrow screens.
4. What we do in the desktop app
- Every feature is reachable by keyboard, with visible focus and keyboard shortcuts you can look up in the Help center (Ctrl+/).
- Buttons and fields have accessible names, and dialogs and menus can be used and closed with the keyboard.
- Animations respect your system's “reduce motion” setting.
- The default color themes meet WCAG AA contrast (checked by automated tests), and you can change the text size without breaking the layout.
- The interface is available in English and Spanish.
5. Known limitations
- The 3D scene on the home page and the animated backgrounds are decorative: they are hidden from screen readers and carry no information that isn't also in the text.
- The code editor and the terminal in the app are built on Monaco Editor and xterm.js. They support keyboards and screen readers, but some screen-reader workflows (for example reading long terminal output) can be harder than in the rest of the app.
- Visual tools such as the screen capture editor and some charts rely mainly on sight and pointer use.
- Custom colors you choose in the app can lower contrast below AA; the default themes don't.
- AI answers are generated by third-party models; we render them as accessible text, but we can't guarantee the structure or the alternative descriptions they produce.
- The desktop app is currently available only for Windows.
We are working on these. If one of them stops you from using Pogama, tell us: we will help you find another way and prioritize the fix.
6. Report a problem or ask for help
Write to soporte@pogama.xyz with “Accessibility” in the subject. Tell us the page or the part of the app, what you were trying to do and, if you like, the assistive technology you use. We will reply, tell you what we will do, and if needed provide the information in another format.
If you are in the EU and are not satisfied with our answer, you can contact the authority responsible for accessibility in your country.
7. Technical details
pogama.xyz relies on HTML, CSS, WAI-ARIA and JavaScript; the 3D scene uses WebGL as an optional enhancement. The desktop app uses the system's web view (WebView2 on Windows) with the same technologies. This statement is reviewed whenever we make significant changes.