cityofaustin / cityofaustin/techstack
Include text about Title VI language access in the "location details" section
- Dominant language
- No language data
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### As a resident, I want to see what languages are available at the location or learn how to access a language that isn't always available onsite so that I can plan accordingly if advanced notice is needed to provide interpretative services.
Per @anukandimalla, we should make it clear what's available as MVP and figure out the content solution to language around Title VI long term.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by locating the location-details content entry point and confirm the MVP language-availability information and the process for requesting interpretation under Title VI. Done means the resident-facing section clearly explains available languages and how to request language access when needed.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, content, documentation, localization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100