Accessibility

Accessibility statement

Taggart sells PDF accessibility, so this site should meet the standard it checks documents against. This page says how far it does, how that was tested, and what has not been done yet.

The standard

The site is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and the Israeli Standard IS 5568, which is based on WCAG 2.0 at level AA. The tests below found no failures. That is a self-assessment by the team that builds the site: it has not been audited by an outside body.

How it was tested

On 27 September 2026, on the site as published that day:

  • Every page, automatically. All 219 pages, in all ten languages, were tested with axe-core 4.13 against the WCAG 2.0 and 2.1 A and AA rules and axe's best-practice rules — once in the light colour scheme and once in the dark. No violations.
  • Reflow. Every page at 320 pixels wide — a 1280-pixel screen at 400% zoom — without sideways scrolling. Six pages failed this before the statement was written, each on one long unbroken string such as a URL or a German compound word in a heading; they were fixed first.
  • Enlarged text. Every page on a 375-pixel phone with the text at 150% and the WCAG 1.4.12 text spacing applied, again without sideways scrolling.
  • Keyboard. Fourteen pages, one of each kind, in Chrome, Firefox and Safari's engine (WebKit): every link and control reached with the Tab key, each with a visible focus indicator. The accessibility menu was operated by keyboard alone in English, Hebrew, Arabic and German.

The first three now run on every build of the site, and a build that fails them is not published — so they hold for the page written next week, not only for the day this statement was written.

Automated tools find some kinds of problem and are silent on others: whether a heading describes its section, whether an alternative text says what matters. That is the same limit this product explains to its own customers, and it applies here.

What the site does

  • A link to skip straight to the main content, landmarks for the header, navigation, main content and footer, and one level-one heading per page.
  • Each page declares its language, so a screen reader reads it with the right voice, and the Hebrew and Arabic pages run right to left throughout.
  • Text contrast of at least 4.5:1 in both the light and the dark colour scheme, which follow your system setting.
  • Animations are decorative, and stop when your system asks for reduced motion.

The accessibility menu

The round button in the bottom corner of every page opens a menu: text size up to 150%, wider text spacing, high contrast, underlined links, stopped animation and a large cursor. The choices are kept in your browser and sent nowhere.

The menu changes how this site looks. It does not replace your browser, operating-system or assistive-technology settings, and the site is meant to work without it — the tests above were run with it switched off.

The application

The start screen of the application at app.taggartpdf.com was tested with axe-core in English, Hebrew and Arabic, in the light and dark colour schemes, with no violations. The screens after signing in — the report, the review of proposed repairs, the account — have not been through the same test yet. The application has the same accessibility menu, in its top bar.

Documents

The sample report (PDF) linked from across the site is a tagged PDF with a title, a language and a logical structure. It was checked with Taggart itself against IS 5568, with no failures. A tool checking its own output is not independent evidence, which is why this sentence says so.

What is not done yet

  • Screen-reader users. Nobody who relies on a screen reader day to day has tested the site. Automated and keyboard tests do not replace that.
  • The signed-in application, as above.
  • Language. The reference sections — the failure conditions and the guides — are written in English. The pages in the other nine languages link to them.
  • Code examples keep their highlighting colours in high contrast mode. Each of those colours is held to 4.5:1 by a test that runs on every build.

Tell us what stopped you

The accessibility coordinator is Ronen Landesman:info@codama.dev. If something on the site or in the application keeps you from using it, write and say which page and what happened. A screenshot helps, but is not needed.

Taggart is operated by Codama Advanced Engineering, Inc.. This statement was written on 27 September 2026 and last updated on 27 September 2026.