Collaborate
The standard is useful only if other networks shape it. Here is how to take part without needing a developer.
Ways to take part
- Adopt a definition
- Write it into your State Plan or subaward and tell us. We list adopters on the definitions page, which gives the next council a precedent to point at.
- Propose a question
- Send the wording, the answer options, who it is for and what decision it informs. If a tested instrument already asks it, send that too. Questions are added with a new id and a note of who proposed them; wording and values are never changed in place.
- Share an instrument your network has tested
- Especially one a screen reader user has worked through. We will map it to the question bank, note which questions pool with the shared ones, and credit the network.
- Correct the data
- Send the page, the figure and your source. Corrections to the federal file go to ACL; corrections to our transforms are made in the open and listed in the repository's change log.
- Add a public source
- A state contract report form, an audit, a legislative appropriation record, a monitoring report. Anything public that bears on how Independent Living money or service is counted.
How to send it
- Email hello@ildata.org or use the contact form. Plain text is fine; attachments are fine.
- If you use GitHub, open an issue or a pull request at the repository. The instrument definitions are JSON files under
src/_data/instruments/and the definitions page is a template undersrc/standards/.
Ground rules
- Accessibility is a requirement for anything published here, not a preference. A question that cannot be asked as a labelled form control is not added until it can.
- Plain language. A respondent should not need to know what a CSR is to answer a survey.
- Stability over elegance. An id, once published, keeps its meaning forever. Better wording gets a new id.
- Say what you cannot show. Every measure here carries its limitations beside it, and proposals should too.