Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify language around "ADA Compliant" filter and reserved community type filter and pill #591

Closed
anders-schneider opened this issue Sep 20, 2021 · 3 comments
Assignees
Labels
good first issue Good for newcomers M14 P0 Highest priority
Milestone

Comments

@anders-schneider
Copy link

anders-schneider commented Sep 20, 2021

Work:

  1. Change to "Reserved for: Special Needs" in the pill
  2. Provide text explanation of ADA compliance (tooltip? text in the filter modal?)

Context:
Writing up some feedback from Gabe (based on a meeting with the city):

When we filter listings by "ADA Compliant" set to "Yes", there are at least two points of confusion:

  • What does ADA compliant mean?
  • Why do only some of the resulting listings have the "Special Needs" pill?

This ticket proposes two pieces of work to address them.

@avaleske avaleske changed the title Confusion around "ADA Compliant" filter and reserved community type (filter and pill) Clarify language around "ADA Compliant" filter and reserved community type filter and pill Sep 21, 2021
@avaleske
Copy link

Reworded title and ticket to clarify what's actionable.

@anders-schneider are these product/detroit requests or is this the starting point for discussion?

@anders-schneider
Copy link
Author

Note from property management weekly sync: Gabe met with the City of Detroit Office of Disability Affairs and they recommended that we change "ADA Compliant" to "Accessible units" (b/c "ADA compliant doesn't mean anything").

Elen's point from a previous sync with a disability-focused CBO: ADA-compliant units aren't always accessible. So maybe "accessible" is misleading. (@elenm to add any detail here.)

So: we may want to change "ADA compliant" to "Accessible units", or find another term. This will likely only matter until we have the more structured disability filtering (i.e. "does this building have an elevator?").

@jnowell jnowell added this to the M13 milestone Oct 12, 2021
@jnowell jnowell added M13 P0 Highest priority labels Oct 12, 2021
@jnowell
Copy link

jnowell commented Oct 12, 2021

Safiya would like to change 'ADA Compliant' to 'Accessible Features for Residents with Disabilities?'.

@GabeBenjamin GabeBenjamin added the good first issue Good for newcomers label Oct 13, 2021
@jnowell jnowell added M14 and removed M13 labels Oct 28, 2021
@jnowell jnowell modified the milestones: M13, M14 Oct 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers M14 P0 Highest priority
Projects
None yet
Development

No branches or pull requests

5 participants