iToolHub

Accessibility statement

iToolHub is meant to work with a keyboard, a screen reader, magnification and high contrast. This page says what has been built for that, what has not been tested, and how to tell the operator when something does not work.

The standard being aimed at

Suraj Giri builds itoolhub.com against the Web Content Accessibility Guidelines 2.2 at Level AA.

No conformance claim is made. The site has not been audited by an independent assessor and has not been tested with assistive technology by anyone whose findings are on record. Saying it conformed would be a claim nobody here can support. "Aiming at" is the honest description, and this page will say something stronger when there is something stronger to say.

In plain terms: the site is built to the standard, and nobody has certified that it meets it.

What is in place

These hold on every page of the site and are checked against the rendered markup rather than promised:

  • A skip link is the first thing in the page, so a keyboard or screen-reader user reaches the tool without walking the navigation.
  • Each page declares its language and has exactly one first-level heading, with no level skipped below it.
  • Header, navigation, main content and footer are marked as landmarks, and both navigation regions are named.
  • Every text box, file input and dropdown in a converter has a label attached to it, not only placeholder text.
  • Keyboard focus is shown with a visible outline that does not depend on the browser's default.
  • Data tables use real header cells, so a screen reader can announce which column a value sits in.
  • The only photographs are of the maintainer. Where his name is not already written beside the photo, it carries his name as alternative text. No picture carries information that the text does not.
  • Nothing moves, flashes, plays automatically or opens in a new window without being asked.
  • Text is set in relative units and reflows, so page zoom and larger default text sizes work rather than clipping the page.

How that was checked

The markup of every rendered page is examined by automated checks that run before the site can ship. They cover language, landmarks, heading order, label association, table headers and the presence of the skip link. That is a check of structure, and structure is the part a program can see.

What a program cannot see, and what has therefore not been verified: whether a screen reader announces a converter's result in a way that makes sense, whether the colour contrast holds at every size, whether the reading order matches the visual order in every layout, and whether the working shown beneath a result is followable without sight. Those need people and have not been done.

Known limitations

The converters need JavaScript
The explanations, the tables and the worked examples are in the page itself and read fine with scripting off. The live conversion boxes do not: they are the code that does the converting. There is no version that works without it.
Wide reference tables scroll sideways
The ASCII table and the larger conversion tables are wider than a phone screen and scroll within their own region. That region is reachable by keyboard, but a horizontal scroll is a poorer experience than a table that reflows.
Colour contrast was measured on some pages, not all
On 16 September 2026 the text and form controls of seven page types were measured in both the light and dark themes. Text met 4.5 to 1, and the edges of form fields were darkened to meet 3 to 1. Pages not in that sample, and colours inside pictures you convert, have not been measured.
The typeface is a web font
Two typefaces are served from this site's own address. If they are blocked or slow, the page falls back to a system serif and monospace and stays readable; the layout does not depend on the web font arriving.
Some reference tables repeat a row identifier
Reviewed on 5 September 2026: several of the larger character tables give more than one row the same identifier. Reading the table is unaffected, but a link that should take you to one specific row lands on the first row that shares its name instead. It is recorded as a defect to fix.
No assistive-technology testing is on record
Nobody has published a test of this site with a screen reader, a magnifier or speech input. Until that exists, a report from you is the best evidence available.

Reporting a barrier

If something here stops you, that is a defect and the report is welcome. Write to suraj@theblogtimer.com and include, as far as you can:

  1. the address of the page;
  2. your browser and operating system;
  3. the assistive software and version, if you use any;
  4. what you were trying to do, and what happened instead.

There is no promised response time, and printing one this site cannot keep would be worse than saying so. Accessibility reports are read and acted on ahead of most other messages, because they describe something that is broken for somebody.

If you need a conversion this site will not give you, say what you need in the same message. The result can be worked out and sent back to you.

Review

This statement is rebuilt from its own source file, and the date beneath it is the date that file last changed. It is reviewed whenever the site's chrome or a converter's controls change, and at least once a year.

How results are checked more generally is set out under how iToolHub computes and checks conversions, and what else that address handles is listed separately.

Last updated by .