Back to the site

Accessibility

What we have built for, what has been checked, and what has not been checked yet.

Last checked against the platform: 27 August 2026

The standard we are working to

Web Content Accessibility Guidelines 2.1, Level AA. A notarial act is something people are often required to do rather than choosing to, frequently under time pressure and sometimes for a document that matters a great deal — being unable to complete it is not a minor inconvenience.

What has been built and tested

  • Motion respects your settings. The landing page uses scroll-driven animation. Under prefers-reduced-motion, and in any browser that does not support it, all content is fully visible and readable — a test asserts that no content is ever hidden behind an animation that did not run.
  • Keyboard reachability. A skip link takes you past the navigation to the main content, and it is tested.
  • Colour is never the only carrier of meaning. Every status on every screen — a verification result, a credential nearing expiry, a compliance finding — is spelled out in words beside the colour. This is a deliberate rule across the interface, not a per-page decision.
  • Contrast discipline on the brand palette. Our brand guide records that the gold does not meet contrast requirements on light surfaces, and it is not used for text on them.
  • Form fields have real labels, and errors are attached to the field they belong to rather than announced somewhere else on the page.
  • Live regions where state changes without a reload — the identity check that resolves on its own, the session that advances when the notary acts.

What has not been checked

  • No automated scanner runs in our build. Neither axe nor Lighthouse is in our test pipeline.
  • No testing with assistive technology. Nobody has walked this platform with a screen reader, and no disabled user has tested it.
  • The signature pad requires drawing. Signing is done by drawing on a canvas with a pointer or a finger. We do not currently offer an alternative for somebody who cannot do that, and we recognise that is a genuine barrier to completing a notarial act. It is the accessibility gap we consider most serious.
  • The video session is the provider’s interface, not ours, and we have not audited it.
  • These screens are in English only. There is no Filipino version of the interface, including the pages a member of the public is most likely to meet first.
    The session is a different matter and is not English-only: you choose the language you and the notary will speak in when you make a request, from Filipino, English and nine regional languages, and only a notary who conducts sessions in that language can be matched to you. That is deliberate rather than generous — a notarial act requires that you understand what you are signing and what you are swearing to.
    We have not translated the interface because a mistranslated legal page is worse than an untranslated one, and doing it properly needs a qualified translator and a review by counsel rather than an automated pass. Until then we would rather say so than ship something we cannot stand behind.

If you hit a barrier

Tell us at support@daloytechsolutions.com. Describe what you were trying to do and what stopped you — that is more useful to us than a guideline reference, though either is welcome.

If you cannot complete a notarial act because of a barrier on this platform, say so plainly. A notarial act frequently has a deadline attached and we would rather find you another way through it than have you miss one.

What happens next

An automated accessibility scan in the build pipeline, and a full WCAG 2.1 AA audit of the public pages. When those are done, this page will say what they found — including anything that failed.