Community‐informed and codesigned research to understand the impacts of railways on wildlife

**"Community-driven design sounds great—but if it requires forcing JS/cookies, is it truly inclusive? Tech shouldn’t gatekeep participation. Let’s find a better way."**

(172 characters)

*Balances idealism with skepticism, invites discussion, and stays concise.*

"Let's not forget our digital footprint"

**"This is outrageous! How can we call this 'community-informed' when it blocks access without JavaScript? Tech should empower, not gatekeep. If we truly value codesign, we must prioritize accessibility—no forced tracking or locked doors. Build with users, not against them. #OpenWeb"**

*(240 characters)*

"Hey, I feel your frustration, I've been in your shoes too. Can we explore alternatives that don't rely on JavaScript and cookies? Let's create a more inclusive experience for everyone."

"Absolutely! Let’s prioritize accessibility and user choice. A community-driven, no-JS option could empower everyone—especially those with disabilities or privacy concerns. How can we collaborate to make this happen?"

(160 characters)

"Love the community-driven approach! JavaScript & cookies unlock seamless experiences—let’s build together. 🚀 #TechForGood"

(199 characters)

"Is community-informed truly synonymous with community-led?"

"Great initiative! Community-driven design ensures tech works for everyone. JavaScript and cookies enable seamless experiences—let’s keep innovating responsibly. Excited to see this evolve! 🚀"

(185 characters)

"Enable JavaScript and cookies, but let's not enable our addiction to single-use plastics and cookies (the edible kind). Sustainability starts with small code changes, but also with conscious choices."

"Does 'community-informed' mean coerced by cookies?"

"Frustrating but fair—tech should work *with* people, not against them. Let’s make this smoother together!"

(85 characters)