Reporting a Problem

If something doesn’t work — a button doesn’t respond, a page shows an error, you got an email that mentions a setting you don’t see — report it to your NA admin first. They have a direct channel to the platform team and they’ll often know whether your specific report is already on the list.

For platform-wide issues (the whole site won’t load, a fresh sign-in flow breaks), report through the project’s GitHub issues at github.com/Tidobandito/birmingham-neighborhood-platform — even if you’re not technical, "I tried X on Y date and got Z error" is a perfectly good bug report.

If a screen-reader misreads a control, a contrast ratio is too low for you to read, or you can’t reach a feature with the keyboard alone — that’s an accessibility regression and it’s treated as a bug, not a feature request. The platform targets WCAG 2.1 Level AA, and that target is enforced by tests.

Send the report to your NA admin or to the GitHub issues link above. Include: what you were trying to do, what assistive technology you’re using (screen reader, magnification, switch control, etc.), and what happened. Screenshots help when you can attach them, but they aren’t required.

Residency claims taking a few days to approve — that’s the normal NA admin review cycle, not the platform stalling. Check your residency status at /settings/security or wait for the email notification.

A help topic showing English content when you’ve set Spanish — Spanish translations are being added topic-by-topic. Until a topic is translated, the platform shows the English version with a banner at the top so you know what’s happening.

A page you used to see disappearing — your role assignment may have changed (officer term ended, residency revoked). Your audit history at /settings/activity will show the change.