Accessibility

We want every part of Jinu to be usable by people of all abilities. Accessibility is not a one-time project for us; we treat it as part of building and reviewing every feature. This statement covers the Jinu website and the Jinu apps for iOS and Android.

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the widely recognized standard for accessible digital products. Working toward means we have implemented the majority of these standards and continue to close remaining gaps. We do not yet claim full conformance, and we would rather tell you that plainly than overstate where we are. WCAG is written for the web, so in our iOS and Android apps we hold ourselves to the same intent through the accessibility guidance Apple and Google publish for their platforms.

• Semantic structure: pages are built with semantic HTML, WAI-ARIA roles, landmarks, and headings so screen readers can convey the structure of a page.
• Keyboard access: interactive controls are reachable and operable with a keyboard, dialogs trap and restore focus and close with the Escape key, and a skip-to-content link is provided.
• Visible focus: keyboard focus is shown with a clear outline so you can always tell where you are on the page.
• Text alternatives: listing photos use the item title as their text alternative, and icon-only buttons carry descriptive labels.
• Color and contrast: text and interactive elements are designed to meet WCAG contrast ratios, and we support a dark theme. Layouts reflow and remain usable when text is enlarged.
• Mobile browsers: the site is built for phones, and supports the screen reader, text scaling and zoom settings your device already provides.
• Our iOS and Android apps: both are built on the accessibility settings you have already chosen on your device rather than settings of their own. Text scales with your system text size, controls carry labels for VoiceOver on iOS and TalkBack on Android, color and contrast follow your system appearance including dark mode, and turning on Reduce Motion replaces animated transitions with plain ones.

• User-uploaded photos: listings are created by our community, and we cannot guarantee that every uploaded image has a rich description. Where an image does not have its own caption, we use the item title as its text alternative. If a photo is important to you, the listing title and description are written to convey the key details in text.
• Maps and embedded content: some third-party features, such as the map used in the location picker, may not be fully accessible. Where a map is used, the same location is also available as text, such as the city and approximate area.
• Ongoing work: as we ship new features, some may reach you before every accessibility detail is complete. When you tell us about a barrier, we prioritize fixing it.
• Our apps are newer than our website: the site has had more accessibility review behind it, so if something is harder to use in an app than in a browser, that is worth telling us about rather than working around.

Jinu is designed to work with recent versions of major screen readers, including VoiceOver, TalkBack, NVDA, and JAWS, and current versions of major browsers. If you use an older browser or assistive technology, some features may not behave as expected. We are happy to help if you run into trouble.

If you encounter an accessibility barrier on Jinu, or you need information from a listing in a different format, please tell us. We take this seriously and aim to respond within 5 business days.

• Email accessibility@jinu.app, or
• Use our contact form.

When you write, it helps to include the page or screen where the problem happened, what you were trying to do, and the browser, device, or assistive technology you were using. None of that is required; even a short note helps.

We evaluate Jinu through a combination of internal review, automated testing, and manual testing with assistive technology. We use the feedback you send us to find and fix issues that testing alone does not catch.

As we improve, we will update this page and the effective date at the top. If our conformance status changes, we will say so here. This statement should be read together with our Privacy Policy and Terms of Service.