Accessibility statement

How LiveInAIWorld makes its site accessible, which standard it follows, known limitations, and how to report a problem.

Last reviewed: September 18, 2026.

LiveInAIWorld wants every reader, including people with disabilities, to be able to read our tests, use our tools and download our templates independently and with dignity. We treat accessibility as part of the quality of the site, not as an add-on.

Standard we follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This covers the requirements of Israeli Standard SI 5568 (based on WCAG) at Level AA, referred to in the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, and is consistent with the European standard EN 301 549 and the accessibility expectations of the Americans with Disabilities Act.

What we have done

  • Structure: every page uses real headings, landmarks (header, navigation, main content, footer) and lists, so screen readers can navigate by structure. Articles with several sections have a table of contents.
  • Keyboard: everything that works with a mouse works with a keyboard. A "Skip to content" link appears as the first item when you press Tab, and a clearly visible focus outline shows where you are.
  • Text and contrast: body text is large (18px), line length is limited for readability, and text colors meet WCAG contrast ratios. The site stays usable when zoomed to 200% and on small screens.
  • Images: meaningful images have text alternatives; decorative illustrations are hidden from screen readers. Build screenshots come with captions that describe what they show.
  • Forms and tools: every field has a label, required fields are marked, and results and error messages are announced to screen readers.
  • Motion and media: nothing plays automatically. Videos start only when you press play, and animations are turned off when your system asks for reduced motion.
  • Cookie banner: it does not block the page, can be operated with a keyboard, and offers "Allow" and "No thanks" with equal prominence. You can reopen it from "Cookie settings" in the footer.
  • Language: each page declares its language so assistive technology pronounces it correctly.

We check pages with automated accessibility tests and by hand with a keyboard when we make significant changes.

Known limitations

We are a small, independent publication and some content is not fully under our control:

  • Embedded videos use YouTube's player once you press play. Its accessibility depends on YouTube, and captions may be missing or inaccurate. Every video accompanies an article that contains the same findings in text.
  • Screenshots of third-party software show interfaces we did not design and may contain small text. The caption and the article text describe what matters in each one.
  • Downloadable spreadsheets (.xlsx) are built to be simple and labeled, but spreadsheet programs vary in how well they support assistive technology.
  • Vendor websites we link to are outside our control, including their sign-up and payment pages.

If any of these stops you from getting the information you need, contact us and we will provide it in another way, for example by email in plain text.

Report a problem or ask for help

If you find a part of the site that is hard to use, or you need information in an accessible format, please tell us:

Please include the page address and a short description of the problem, and, if you can, the browser and assistive technology you use. We aim to reply within 5 business days and to fix confirmed problems as quickly as we can.

Updates

We review this statement whenever we make significant changes to the site and at least once a year. The date at the top shows the latest review.

Last updated September 18, 2026