How should accessibility be added to market-board threads?

R

rhea_dove

Market analyst
Established
Market Reporter
While browsing the Lima board, I kept wanting a consistent way to identify accessibility information across property threads. Without it, local comparisons are awkward and the same questions recur in valuations and market reports.

Would accessibility work better as a required thread field, an optional tag, or a search filter fed by structured fields? My main concern is keeping posting quick enough for casual members, especially on mobile.
 
I would use an optional structured field rather than free-form tags. A simple “accessibility information available?” choice could reveal a few more options only when selected. Search could then use those answers. Making the full section compulsory would slow people down and probably produce lots of guesses.
 
What does “accessible” mean here? Step-free entrance, lift access, internal layout and adapted bathrooms are different things. A single yes/no result could be misleading, while a long checklist creates the posting problem Omar mentioned.
 
That is why I would avoid one broad accessibility tag. Use a small set of factual tags such as step-free entrance, lift and adapted bathroom, plus “not stated.” Members can report what a listing says without declaring that the whole property suits every person.
 
The distinction between factual features and an overall accessibility claim makes sense. I’m leaning toward an optional collapsed section with perhaps a few choices and an “other details” box. On the Lima board, even being able to filter for threads where accessibility was addressed would be better than searching every reply.
 
I disagree slightly on the text box. It is useful for nuance, but it should not drive filtering because wording will vary too much. Let the fixed choices power search and keep the text for things like an awkward route through a shared area.
 
Mobile layout is the deciding factor for me. If the choices appear as a large block during posting, casual members will skip the thread entirely. One compact prompt that expands only when tapped would preserve speed. The same choices should also be available when editing later.
 
How would this apply to market reports rather than individual listings? A report may cover many properties, so property-level boxes would not fit. Perhaps the field should include “discussed in thread” for reports, while listing threads get the feature choices.
 
That separation adds complexity, though. The forum could begin with one optional “accessibility details included” marker for every thread, then show the more specific choices only for property listings. Better to test a small version than design every regional and thread-type exception at once.
 
Regional wording matters too. A tag set created around Lima discussions may not map neatly onto boards elsewhere, even when the underlying feature is similar. Keep the visible labels plain and consistent globally, but allow the explanation field to carry local building terminology. Otherwise search fragments into near-duplicate tags.
 
There is also moderation effort. Member-created tags will drift into duplicates and subjective claims. A short fixed list avoids most cleanup, and moderators would only need to deal with clearly misplaced entries rather than standardise everyone’s wording.
 
Old threads should not be bulk-labelled by inference. Leave them as “not stated” unless someone edits them, and let search distinguish that from a definite no. A gradual migration is less complete, but it avoids turning missing information into inaccurate information.
 
A workable first version seems to be: optional collapsed fields, a small fixed set of factual features, “not stated” as the default, and a separate notes box that is not used for filtering. Add the report/listing distinction only if the initial Lima trial shows people need it. That keeps posting fast while still improving search.
 
You must log in or register to reply here.
Back
Top