Written-first
Idea, issue, collaboration, clarification, and formal application routes support written participation rather than requiring a phone call or live pitch.
Accessibility
Access belongs at the front door of innovation.
A statewide idea program fails if participation depends on fast speech, public pitching, long forms, travel, high bandwidth, or social confidence.
AAC + support people
Equivalent communication routes can include AAC, typed responses, captions, communication supporters, and additional response time.
Remote + asynchronous
Where the activity allows it, people should be able to participate without traveling to Little Rock or appearing live at a single time.
Plain public rules
Each formal Challenge Brief should state what is required, what is optional, what the incentive is, how review works, and what happens next.
Low-bandwidth / printable
Key public information and forms should remain usable on mobile devices, slower connections, and printable formats.
Language access
Public-facing participation should plan for language access and translation rather than treating English-only participation as universal access.
Accessible digital baseline
State/local government web and mobile services are subject to the current DOJ Title II digital-accessibility rule and WCAG 2.1 AA compliance framework.
No diagnosis gate for discovery
An open idea, problem report, or general collaboration contribution does not need diagnosis proof. A specific research or funded activity may have separate lawful eligibility rules.
Formal challenge support
Support must be real enough to publish.
A Challenge Brief should identify the actual accommodations and participation supports available for that cycle: captioning, interpretation, travel help, stipends, office hours, accessible files, technical assistance, prototype access, or other support.
The site should not promise resources that have not been funded or scheduled.