Accessibility Statement

Last reviewed: October 8, 2026

Online safety help is only useful if people can actually use it. I want this website, the member portal and the chat to work for everyone, including people who use screen readers, keyboards, voice control, magnification or other assistive technology.

My commitment

I aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA published by the W3C. Where it's practical, I also follow parts of WCAG 2.2. This applies to this website (aldrianloyola.com), the member portal and the chat assistant.

Current status

This website partially conforms with WCAG 2.1 Level AA. "Partially conforms" means some parts don't yet fully meet the standard, or haven't been independently checked. I have not yet had the site audited by an outside accessibility specialist, and I don't claim certification or full conformance.

What I've done so far

  • A "Skip to content" link on every page, and clear page landmarks (header, navigation, main content, footer).
  • Descriptive page titles, one main heading per page, and headings that follow a logical order.
  • Text descriptions (alt text) for meaningful images. Decorative images are hidden from screen readers.
  • Every button, icon button and link has an accessible name. Links that open a new tab say so.
  • Form fields have labels, and error and status messages are announced to screen readers.
  • Everything can be used with a keyboard, with a visible focus outline.
  • Text colors are checked for contrast, and the pages reflow on small screens and when zoomed to 200%.
  • Animations are reduced or turned off when your device asks for reduced motion. The animated preview on the home page has a Pause button.
  • Automated testing with the axe accessibility engine, plus my own keyboard checks, when changes are made.

Known limitations

  • Member portal and chat. These are newer and more complex. I'm still improving screen reader announcements and keyboard behavior in places such as the tool results and the chat window.
  • AI replies. Alds Privacy writes its answers on the fly, so I can't check every reply for accessible formatting.
  • Images in guides and articles. Each image has a text description field, but a description may occasionally be missing or brief on older content. Tell me if you find one.
  • Third-party services. Payment is handled by PayPal, and the site uses Google Analytics and Google Fonts. I don't control their accessibility.
  • Testing coverage. Automated tools find only part of the problems. I haven't yet tested with every screen reader and browser combination.

Tell me about a barrier

If something is hard or impossible for you to use, please tell me. It helps to include the page address, what you were trying to do, and the device, browser and assistive technology you use (if you're comfortable sharing).

I'll reply within two business days, and I aim to fix reported barriers or offer a workaround within ten business days. You can also read the accessibility help page for tips on using the site.

If you can't use part of the site

I'm glad to help another way: through email or chat, in plain text, or in another format you prefer. If you're a member, I can do a task with you in the chat instead of making you use a feature that doesn't work for you.

This statement is not legal advice

This is a description of my effort and current status, not a legal guarantee. I'll update it as I make improvements and after any independent review.