Accessibility

Our aim

bram aims to meet WCAG 2.2 Level AA. This statement describes where we currently stand against that, including the parts that fall short. We would rather publish a list of known gaps than a claim of full conformance we have not had audited.

What is in place

• Keyboard operation. Every control is reachable and operable by keyboard, with a visible focus ring on each. Dropdowns close on Escape and return focus to the control that opened them.
• Contrast. Body text and interface text meet the 4.5:1 minimum in both the light and dark themes. Colour is never the only thing carrying a meaning.
• Reduced motion. Every animation on the site — the drifting hero backdrop, the counting figures, the scroll reveals, the icon movement — is disabled when your system requests reduced motion. Nothing is hidden behind an animation, so turning motion off never costs you content.
• Semantic structure. One h1 per page, headings in order, landmark regions, labelled form fields, and text alternatives for meaningful images. Decorative graphics are hidden from assistive technology rather than described.
• Zoom and reflow. The layout reflows to 320px and survives 200% text zoom without loss of content or horizontal scrolling.
• No content depends on JavaScript to be readable. Nothing is parked invisible waiting for a script.

Known gaps

We are aware of the following and are working on them.

• The hero comparison instrument conveys its result partly through an animated diagram. It carries a text description and the same figures appear as text beneath it, but the animation itself is not narrated as it progresses.
• Some tool interfaces are visual by nature. The image cropper, the colour picker and the background remover involve pointing at a region or a colour, and we do not yet offer a complete non-pointer path through all of them. Numeric entry covers part of this and not all of it.
• Live regions are incomplete. Some tools update a result without announcing it, so a screen-reader user may not learn that the output changed until they navigate to it.
• No formal audit yet. This statement is based on our own testing with keyboard navigation, browser zoom and automated checks — not on an independent assessment.

Tell us

If something here blocks you, please email support@tekhx.com with the page and what happened. We treat an accessibility barrier as a bug of the same severity as a tool producing the wrong output, and we will reply within 5 business days.

If you need something a tool here cannot currently give you in an accessible form, say so and we will find another way to get you the result.