Skip to content
Ditap®
Back to Home

Accessibility Statement

Last updated: August 2026

1. Our commitment

DITAP wants ditap.io to be usable by as many people as possible, including people with visual, motor, hearing or cognitive disabilities. This statement explains, honestly, how close we are to that goal today — not just what we aspire to build.

2. Standard and target conformance level

Our target is to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, and to the harmonized standard EN 301 549, the technical reference standard of Directive (EU) 2019/882 on accessibility requirements for products and services (the "European Accessibility Act"), in force since 28 June 2025.

This conformance level applies to new content we publish and is the benchmark we measure existing pages against as we audit them.

3. Current conformance status

The site is partially conformant with WCAG 2.1 AA. "Partially conformant" means some parts of the content don't yet meet the standard in full — not that we haven't started, and not that we're finished either. We haven't yet completed a third-party accessibility audit of the full site; this statement is based on an internal review of the code and the site's behavior.

4. Measures already in place

These are concrete measures that exist on the site today, not a list of intentions:

  • "Skip to content" link: every page includes a keyboard-accessible link, visible on focus, that lets you jump straight to the main content without repeating header navigation.
  • Semantic heading structure: every page uses a single `<h1>` followed by a coherent `<h2>`/`<h3>` hierarchy, rather than heading-styled text without semantic markup.
  • Main content landmark: each page's core content is marked with `<main id="main-content">`, the target of the skip link.
  • Adjustable contrast: the light/dark theme switcher in the header lets each person choose the contrast combination that's most comfortable for them, with a smooth color transition instead of an abrupt switch.
  • Semantic HTML: buttons are `<button>`, links are `<a>`/`<Link>`, and informative images include alt text.
  • 5. Known limitations

    With the same honesty, here's what's still unresolved:

  • We haven't completed a formal audit with automated tools (e.g. axe, Lighthouse accessibility audit) or with real assistive-technology users across the full site.
  • Some animated interactive components (built with Framer Motion) may not yet consistently respect the system's `prefers-reduced-motion` preference.
  • We haven't exhaustively verified keyboard focus order in complex flows (for example, multi-step forms or interactive calculators).
  • Color contrast hasn't been systematically checked against the 4.5:1 (AA) threshold for every text/background combination on the site.
  • We'll update this section as we resolve each item.

    6. Compatibility with assistive technologies

    The site is built on standard semantic HTML and doesn't depend on proprietary plugins, so it should be reasonably compatible with modern screen readers (NVDA, JAWS, VoiceOver) and with keyboard-only navigation. We haven't completed formal testing across every screen reader and browser combination.

    7. How to report an accessibility issue

    If you run into an accessibility barrier on ditap.io — content you can't use with your assistive technology, insufficient contrast, an element you can't reach by keyboard, or any other difficulty — tell us:

  • Email: hola@ditap.io
  • What to include: the page where it happened, what you were trying to do, and whether you use any assistive technology (screen reader, keyboard navigation, zoom, etc.).
  • We respond to and prioritize every accessibility report directly — this isn't a generic support channel.

    8. Ongoing improvement plan

    Accessibility is a process, not an end state. Our plan is: (1) complete an automated audit of the full site, (2) prioritize and fix the highest-impact findings, (3) build accessibility review into the workflow for new pages, and (4) update this statement with every material step forward.

    PEOPLE, PROCESS AND SUPPORT

    Alongside you, before, during and after.

    A clear first conversation. A written proposal. Next steps agreed together.

    1. Before: understand and define

      We discuss your needs and set out objectives, deliverables, timelines and costs in the proposal.

    2. During: coordinate the work

      We agree on responsibilities, stages and the information needed to move forward. Launch and training are defined for each project.

    3. After: know what comes next

      We agree on support channels, hours and scope so you know whom to contact.

    Answers before you decide.

    What will I receive before signing?

    A written proposal with scope, deliverables, stages, pricing and terms, including any additional services you choose.

    How is support organized?

    We define contact channels, hours and support scope in the proposal, so you know what is included and how to request help.

    What happens to my organization’s information?

    We review what information is needed, who can access it and how it is shared. For software systems, we also agree on backup, retention and export conditions.

    TECHNOLOGY THAT SUPPORTS YOUR TRUST

    A protected technology foundation.

    HTTPS / TLS

    Encrypted connections

    Your browsing on this website uses HTTPS/TLS to protect information during transmission.

    AES-256

    Infrastructure encryption

    Vercel, this website’s hosting provider, documents AES-256 encryption for data stored on its infrastructure.

    DITAP

    Protection for your operation.

    Each project defines its services and the protection needs of information and operations.

    Explore the provider’s safeguards