Accessibility

This is a tool people use for work, so it has to work with a keyboard and with a screen reader. Here is what that means in practice, and where to write when something blocks you.

Last updated September 10, 2026

The standard we build against

We build this site and the converter against the Web Content Accessibility Guidelines 2.1, level AA. That is the standard United States courts have applied to commercial websites under the Americans with Disabilities Act, the standard behind the reasonable adjustments duty in section 29 of the UK Equality Act 2010, and the standard the European Accessibility Act points to.

This page is a statement of how the product is built and tested. What is written below is what the code does, and you can check any of it in a browser in a couple of minutes.

What is in place

  • A keyboard reaches everything. Every page opens with a "Skip to content" link that takes you past the navigation, the menus open and close from the keyboard, and focus is drawn with a two-pixel outline that is never removed.
  • Uploading works without a mouse. Drag and drop is the fastest way in, and it is not the only one: the file field is in the tab order, opens your system file picker from the keyboard, and outlines the drop area while it holds focus. The Choose a file button opens the same picker.
  • Conversion announces itself. The progress bar carries its value and its label, and the status line and the remaining-pages line are live regions, so a screen reader hears each step as it happens instead of a silent spinner.
  • Tables are real tables. The result of a conversion is a table with a caption and a marked header on every column, so a screen reader reads a statement row by row and repeats the column it is in. The tables on this site that carry the terms you are agreeing to, in the privacy policy, the security page and the data processing agreement, are built the same way.
  • Every field has a label. Sign-in, contact and account forms use visible labels tied to their fields, and errors are written out in text rather than signaled by color alone.
  • Color is measured, not guessed. Every step of the palette carries the contrast ratio it was measured at, and the roles are assigned from those measurements. Against any surface it is allowed to sit on, body text stays above 11 to 1 and muted text and links stay above 5.3 to 1, where level AA asks for 4.5. The lightest border a control may use clears the 3 to 1 that WCAG 1.4.11 asks of a boundary you have to be able to see.
  • Motion is optional. When your system asks for reduced motion, transitions, the reading-progress bar and every entrance animation stop. Nothing on the site flashes, plays sound, or starts moving without you asking it to: the only thing that animates during work is a conversion reporting its own progress.
  • The layout reflows. Pages work down to a 320 pixel window without sideways scrolling, which is the same requirement as zooming to 400 per cent on a laptop. Wide tables scroll inside their own frame rather than pushing the page around them.
  • Text scales. Type and spacing are set in relative units, so raising the browser's text size enlarges the page rather than clipping it.

Working with a converted statement

A converted statement is a wide table: date, description, debit, credit, balance and the result of the balance check. Two things make that easier to work with.

  • On a narrow screen the result scrolls inside its own frame, so the rest of the page stays where you left it.
  • Every conversion can be downloaded as XLSX, CSV or one of the accounting formats, and for reading a long statement your own spreadsheet or accounting software is usually the better tool. The download carries the same rows as the screen, including the balance-check column.

The balance check never relies on color alone. A row that breaks the running total is labeled in words, with the size of the difference, in the export as well as on screen.

Tell us when something blocks you

If anything on this site or in the converter stops you from doing your work, email support@statementtable.com with the page you were on, what you were using, and what happened. Every message to that address is answered within one business day. An accessibility fault goes to the front of the queue, ahead of feature work.

If you need a conversion done while a barrier is being fixed, say so in the same email and we will do it for you and send the file back.

Privacy Policy · Terms of Service · Security and data flow · Help center