Accessibility statement

Pasaran is where people in Bali find somewhere to live, something to drive and somewhere to work. A marketplace that only some people can use is not doing that job, so accessibility is treated as part of whether a feature is finished, not as something added afterwards.

We aim for the Web Content Accessibility Guidelines version 2.1 at Level AA across every page of the site, including the account, business and checkout areas.

Pasaran is partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the site meets the standard, and the parts that do not are listed below with a date by which we expect them to.

Conformance is assessed in two ways: automated checks run against every route on each release, and manual testing of the main journeys — search, listing detail, contact a seller, post a listing, checkout — using a keyboard alone and using a screen reader.

The following hold across the site and are checked on every release.

• Every interactive control is reachable and operable with a keyboard, in a logical order, with a visible focus ring that meets the contrast requirement.
• A skip-to-content link is the first focusable element on every page.
• Body text meets a contrast ratio of at least 4.5 to 1, and large text and interface components at least 3 to 1.
• Pages carry one h1 and a nested heading structure that can be navigated by heading level.
• Form fields have persistent visible labels, and errors are announced and described in text rather than by colour alone.
• Images that carry meaning have alternative text; decorative images are hidden from assistive technology.
• Layouts reflow to a 320 pixel viewport width without horizontal scrolling, and text can be enlarged to 200 per cent without loss of content.
• Motion respects the reduced-motion system setting; animation is decorative and never conveys information on its own.

Testing is done on current versions of the following combinations, which cover the majority of our members who use assistive technology.

• VoiceOver with Safari on macOS and iOS.
• NVDA with Firefox and with Chrome on Windows.
• TalkBack with Chrome on Android.
• Keyboard-only navigation in Chrome, Safari, Firefox and Edge.
• Browser zoom to 200 per cent, and operating-system text scaling.

These are the gaps we are aware of. Each has an owner and a target date, and this list is updated when one is closed rather than when the next release ships.

• Map view on search results is difficult to operate without a mouse. Every listing shown on the map is also present in the list view, which is fully accessible, and a keyboard-operable map is targeted for the fourth quarter of 2026.
• The image lightbox on listing detail announces the image count but does not yet announce a change of image to screen reader users. A live region fix is targeted for the third quarter of 2026.
• Some price-range and area-size sliders are hard to set precisely with a keyboard. Every range filter also accepts typed minimum and maximum values as an alternative.
• A small number of seller-supplied listing photographs have no meaningful alternative text, because it is written by the seller. We prompt for it at upload and are adding a validation step.
• PDF invoices generated before June 2026 are not tagged for screen readers. Invoices from that date forward are tagged, and an earlier invoice can be supplied as accessible HTML on request.
• The administration console is not covered by this statement; it is an internal tool and is assessed separately.

Some parts of a page come from other companies — map tiles, the payment step at checkout, and embedded video in area guides. We do not control their code.

Where a third-party component fails our standard we raise it with the supplier and provide an accessible alternative route in the meantime. Checkout, for example, can be completed with support by telephone if the payment step blocks you.

If something on Pasaran blocks you, tell us and we will treat it as a defect rather than a suggestion. The more specific you can be, the faster it is fixed.

• Email [email protected], or use the contact form and choose the accessibility topic.
• Tell us the page address, what you were trying to do, and what happened instead.
• Tell us your browser, operating system and any assistive technology, including versions if you know them.

We acknowledge accessibility reports within two working days and give an assessment with a target date within ten. Barriers that block a core journey — searching, contacting a seller, completing a purchase — are treated as urgent and fixed ahead of feature work.

If a barrier stops you completing something time-sensitive, our support team can do it with you rather than making you wait for a fix. That includes posting a listing over the phone, completing a purchase, and reading out the details of a listing or a document.

Contact details and opening hours are on the contact page. Say that you are contacting us about an accessibility barrier and the request is routed to a team member trained to handle it.

This statement was prepared by the Pasaran engineering team using a combination of self-evaluation and external review. Automated testing runs on every route on each release; manual keyboard and screen reader testing covers the main journeys each quarter.

An independent accessibility audit was last carried out in May 2026 and the findings are reflected in the limitations above. The next external audit is scheduled for May 2027, and this statement is reviewed at least every six months in between.

If you report a barrier and are not satisfied with our response, ask for the report to be escalated and it will be reviewed by the head of engineering, who replies personally.

We would rather hear about a problem than have someone quietly give up on the site. Reports from members are how most of the limitations listed above were found in the first place.