Skip to content
ATAHSKIA

Accessibility Statement

Last updated October 1, 2026

ATAHSKIA's commitment to making atahskia.si and the ATAHSKIA platform usable by everyone, the standards we test against, known limitations, and how to request help or report a barrier.

Our commitment

Import operations analysts, NVOCC finance teams and drayage dispatchers spend hours a day in the ATAHSKIA audit queue. Everyone on those teams, including people who use screen readers, magnification, voice control or keyboard-only navigation, should be able to review findings, approve disputes and track deadlines without help. Siddharth Menon, VP Product, owns accessibility across the website and platform.

Standards we follow

We design and test against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That target also supports customers who must meet Section 508 of the US Rehabilitation Act for procurement, the European standard EN 301 549, and India's Rights of Persons with Disabilities Act, 2016.

What we have built in

Accessibility is part of our component library rather than a late fix, so new screens inherit it.

  • Full keyboard operation of the audit queue, invoice detail, dispute approval and evidence upload flows, with visible focus indicators.
  • Semantic headings, landmarks and labelled form controls throughout, and ARIA live regions for status changes such as "dispute sent" or "deadline in 3 days".
  • Text and interface colours that meet WCAG contrast ratios in light and dark themes.
  • Charts in carrier scorecards and milestone timelines paired with data tables that screen readers can read.
  • Layouts that reflow at 400% zoom and respect reduced motion settings.
  • Session timeout warnings with the option to extend before you lose work.

How we test

Every release runs automated accessibility checks in continuous integration. Before major releases we test manually with NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and keyboard-only navigation, and we commission an independent WCAG 2.2 AA audit each year.

Known limitations

We are working on the following and track each item in our product backlog.

  • Invoice PDFs, terminal screenshots and other evidence files uploaded by customers or issued by billing parties may not be tagged for accessibility. The platform extracts invoice fields into accessible text, but the original files are shown as received.
  • The drag-and-drop column editor in custom audit reports has a keyboard alternative through the column settings menu, but the drag interaction itself is pointer only.
  • Some exported dispute packet PDFs generated before July 2026 lack full tag structure; regenerating the packet produces a tagged version.

Accessibility Conformance Report

Customers and procurement teams can request our Accessibility Conformance Report, based on the VPAT 2.5 template and covering WCAG 2.2, Section 508 and EN 301 549, by emailing support@atahskia.si.

Feedback and assistance

If you hit a barrier on our website or in the platform, or need information in a different format, contact support@atahskia.si or call 1800-266-2929. Tell us the page or feature, what you were trying to do, and the assistive technology you use. We acknowledge reports within two business days and aim to provide a fix or a workable alternative within 10 business days.

If a barrier is blocking time-sensitive work, such as sending a dispute before a § 541.8 deadline, say so in your message and our customer recovery team will help you complete the task directly.