Tools should remain usable.

We use the Web Content Accessibility Guidelines as a practical reference for structure, keyboard operation, labels, contrast, error messages, focus, and responsive layout. Conformance is assessed by page and feature; this statement does not claim that every browser, file preview, advertisement, or third party service is free of barriers.

Visual cropping and edge inspection naturally rely on the image itself. We aim to keep settings and actions keyboard reachable, but a visual preview may not communicate the same information to every visitor. Canvas based editors, native file pickers, temporary preview links, and third party processors can also behave differently across browser and assistive technology combinations.

If a task cannot be completed with your setup, report the page and the step involved. That is more useful than sending the private source image.

Functional icons should have an accessible name or nearby text. Decorative graphics should not add noise. Informative images should receive text alternatives that communicate their purpose. Headings are intended to describe page structure rather than act as visual decoration.

Advertising, consent interfaces, remote processing, and linked websites may be supplied by other providers. We choose and configure services with accessibility in mind where possible, but their interfaces can change independently. A barrier caused by a third party should still be reported so we can investigate or offer another route.