accessibility statement

We want the noble roast website to be comfortable for everyone, including people who use a keyboard instead of a mouse, screen readers, screen magnification, high-contrast mode or the «reduce motion» setting.

Goal and status. Our goal is conformance with WCAG 2.2 (Web Content Accessibility Guidelines) at level AA. The site currently partially conforms to this standard: the main shop pages — the catalog, coffee pages, cart, checkout, sign-in and the customer account — have been reviewed and improved, but there are known limitations, listed below.

What we have done. Every page starts with a «skip to content» link; keyboard focus is always visible; dialogs and panels (cart, filters, forms) work with the keyboard and close with the Esc key; form fields have labels and hints, and errors and successful submissions are announced by screen readers; autofill works for name, phone, email and passwords; text and field borders have sufficient contrast; the site follows the system «reduce motion», «increase contrast» and Windows forced-colours settings; the roast curve is also available as a table.

Known limitations. The site's admin panel (for staff) has not yet been reviewed for accessibility. Batch certificates (CoA) in PDF format are not tagged — the same information is on the certificate page on the site. On the coffee belt map, region labels can sit close together when zoomed in — the same content is available as a list below the map. Texts added by staff (coffee descriptions, articles) may contain images without descriptions — we fix these as soon as we notice them. Testing with screen readers on different devices and with automated scanners is not finished yet.

How to report a problem. If anything on the site is inconvenient or inaccessible for you, write to us or call — the contacts are below. Please describe the page and what did not work: we will reply and help you place your order in another way that suits you.

Date. This statement was prepared on 17 November 2026. The site was last reviewed on 17 November 2026: a code audit against the WCAG 2.2 AA criteria and fixes for what was found. We update this statement after every review.

contacts for feedback