Property type
Price ceiling
Up to$40.0M
Minimum cap rate
At least0.0%
Map area

For sale in Greater Los Angeles

Sorted by relevance

What a screen reader hears

Design decisions

Why the empty state names the constraint

“No results” tells a broker nothing they did not already know. The prototype computes which single filter is responsible for the emptiness, says so, and offers the relaxation with the resulting count attached — so the next click is a decision rather than a guess.

Seen in: Zero results

Keyboard shortcuts

The results list and the map each take one Tab stop. Inside them, these keys do the moving. The bar along the bottom of the page shows what a screen reader hears as you go.

/
Jump to the search box
↓
From the search box, move into the results
↑ ↓
Move through the results
Home End
First and last result
Enter
Open or close the focused result
S
Save the focused result, or remove it from saved
← →
On the map, move between pins; Enter selects one
Esc
Close a dialog

Working prototype · commercial real estate search

What Happens When Search Doesn't Go as Planned

Every search has a happy path. This prototype is about the other one: results come back empty, a listing goes under contract while you are looking at it, a filter stops making sense. Eight of those moments, built as working interface: clickable, keyboard-navigable and readable by a screen reader. Pick one of the eight scenarios, or break the search yourself with the filters. All listings are invented sample data.

Kayhan Atamyildiz kayhan.me More experiments Built with Claude Code · accessible from the first commit, not audited at the end

Theme
Type floor, and what has actually been tested

Nothing on this page is set below 0.875 rem. WCAG specifies no minimum type size at all, so that is a house standard sitting above the spec: hierarchy here comes from weight, case, tracking and colour rather than from shrinking the secondary text until it is deniable. axe-core, WCAG 2.1 A and AA rule sets, run against all eight scenarios: zero violations. Reflow holds at a 320 px viewport, and the 1.4.12 text-spacing override introduces no horizontal scroll. That is a floor, not a certificate — automated tooling catches perhaps a third of real accessibility problems, and no manual screen-reader pass has been run on this prototype. The remaining “incompletes” are axe declining to judge contrast in three places: the glyph-only key hints, the two-way toggles, whose chosen side is drawn by a sliding thumb behind the text, and text in the dialogs, which float over the page. Motion and the simulated loading are both switched off for anyone whose system asks for reduced motion: nothing animates or loops, and the pauses that stand in for a server shrink to a tenth of a second. Treating an automated pass as conformance is the habit this page exists to argue against.

Sample data is invented; addresses, prices and cap rates are not real listings and no Crexi data was used. Built as an independent prototype by Kayhan Atamyildiz to demonstrate edge-case and accessibility practice — keyboard model, ARIA roles, live regions, focus management and reduced-motion support are implemented, not simulated.