Accessibility

We build against WCAG 2.1 level AA. We are not going to tell you we have met it everywhere, because we have not tested everywhere — and a badge we cannot back is worth less than an honest list. What follows is what has actually been measured, what it found, and what is still open.

Colour contrast. Every piece of text on the public pages was measured against the colour actually behind it. Three failures turned up and all three are fixed: our muted text in both light and dark themes, and our orange where it was used for small text. Body text and headings passed comfortably.

Keyboard. Every control can be reached and operated with a keyboard, and each one shows a visible focus ring when you get there with the Tab key. There is a “Skip to content” link as the first thing on every page, so you do not have to tab through the header to reach what you came for.

Touch targets. Buttons and links are at least 44  pixels, checked automatically every time we build.

We have not run a full screen-reader pass with VoiceOver or NVDA. We have not tested reflow at 200% zoom. We have not audited reduced-motion preferences. And nothing behind the sign-in page has been through the same contrast work as the public pages, though it shares the same colours and the same focus ring.

Those are real gaps, not modesty. If you hit one, the next section is the fastest way to get it fixed.

GetBucked is built by one person, which means there is no ticket queue to disappear into. Email support@getbucked.app and say what you were trying to do, what got in the way, and what you use — a screen reader, keyboard only, magnification, whatever it is. We answer, and we will tell you honestly whether it is a quick fix or a longer one.

If something on this site is blocking you from getting your own photos out, say so in the subject line and we will treat it as urgent. Your library is yours and an accessibility problem on our side is not an acceptable reason for you to lose access to it.