Sabet

Built for everyone

Accessibility at Sabet.

A collection is for everyone who loves the work. We design and build sabet.com with that in mind — the goal is for any collector, on any device, with any assistive technology, to use every part of this site without friction.

The standard we follow

We design and develop sabet.com to meet WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C. That covers four broad areas: content is perceivable, controls are operable, copy is understandable, and the site is robust across browsers and assistive tech.

What works today

  • Keyboard navigation.Every interactive control — buttons, links, form fields, popovers, the verified-mark tooltip, the certificate gallery lightbox — is reachable and operable with the Tab and Shift+Tab keys, Enter or Space to activate, and Escape to dismiss modals.
  • Visible focus. Every focusable element shows a clear ring when it has keyboard focus, with sufficient contrast against any background.
  • Skip link.The first Tab press on any page surfaces a “Skip to main content” link so screen reader and keyboard users can bypass the header navigation on every page.
  • Semantic HTML. We use real heading levels, buttons that are <button>s, links that are <a>s, and forms with labeled inputs. Screen readers announce structure correctly.
  • Alt text on artwork. Every piece, drop, and collector avatar includes meaningful alternative text so screen reader users get the same information sighted visitors do. Decorative ornaments use alt="" per the WCAG decorative-image guidance.
  • Reduced motion.If your device requests reduced motion (Settings → Accessibility on iOS/macOS, or the equivalent on Windows/Android), our hover image-zoom, the signup-popup slide-in, and other non-essential animations are suppressed automatically.
  • Color contrast. Body copy and primary controls meet or exceed the WCAG AA contrast ratios against both light and dark backgrounds.
  • Resizable text.All copy uses relative units; zooming to 200% (browser zoom or pinch-zoom on touch) doesn’t break layout or cut off content.
  • ARIA where it helps. Modals, popovers, and lightboxes use role="dialog" + aria-modal + aria-label. Buttons that change state use aria-pressed. Toggle icons carry descriptive aria-labels.
  • Forms. Every input has a real <label>, validation errors are surfaced in text (not color alone), and the tab order matches the visual order top-to-bottom.
  • Mobile.Tap targets follow Apple’s 44pt minimum on touch surfaces; the mobile tab bar at the bottom keeps navigation reachable with one thumb.

What’s in progress

We test new pages against automated tooling (axe-core) and manual screen-reader sweeps (VoiceOver on iOS/macOS, TalkBack on Android), but no audit is perfect. Specific areas we’re continuing to harden:

  • Live-region announcements for asynchronous updates (favorite count, new comments, optimistic message sends).
  • Captioning and transcripts for Instagram Reels embedded on drop pages — today we link out to Instagram, where their native captions handle this.
  • Continued copy edits for plain-English clarity, especially in transactional flows (checkout, verification submission).

Compatible with

sabet.com is tested against current versions of Chrome, Safari, Firefox, and Edge on desktop; Safari and Chrome on iOS; Chrome on Android. Screen reader testing covers VoiceOver (iOS, macOS), NVDA (Windows), and TalkBack (Android). If you use an older assistive technology and run into a barrier, please tell us which one — specifics let us reproduce and fix.

If something doesn’t work for you

Report a barrier, suggest an improvement, or request the same information in a different format — we’ll respond within five business days. Email hello@sabet.com with “Accessibility” in the subject line.

When you write, please tell us:

  • The URL of the page where you hit the issue
  • What you were trying to do
  • What happened instead
  • The browser, device, and assistive technology you’re using

Formal feedback & legal

This statement was last reviewed on . It is published to comply with the European Accessibility Act (EAA), Section 508 of the U.S. Rehabilitation Act, and the Americans with Disabilities Act (ADA) — including any specific guidance adopted in your jurisdiction.

If you’ve reported a barrier through the email above and aren’t satisfied with our response, you can escalate to your local accessibility enforcement authority. We’re happy to help you find the right contact for your region.

How we keep checking

Accessibility is built into our development process, not bolted on:

  • Pull requests are reviewed for keyboard reachability and semantic markup before merging.
  • We run automated checks (axe-core, Lighthouse) on every deploy.
  • We do periodic manual screen-reader sweeps and act on any barriers reported here.

← Back to sabet.com