Description
Record an explicit communication-support preference flag.
Accessibility records distinguish requested support, recorded barriers, display choices and measured local geometry. Six-dot permutations depend on array orientation, angular text size depends on viewing geometry, and playback speed changes nominal runtime. These operations do not establish accessible communication, consent, legibility or compliance for an individual or environment.
Record an explicit communication-support preference flag.
When to use this tool
Use Communication Support Consented Choice when you already have recordId, suppliedSupportChoice, preferenceRecorded and need to record an explicit communication-support preference flag.
How to use the tool and how it works
- Enter recordId, suppliedSupportChoice, preferenceRecorded. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter recordId, suppliedSupportChoice, preferenceRecorded using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup. Boolean permission or verification fields are recorded assertions, not authorizations.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedSupportChoice | Supplied Support Choice | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| preferenceRecorded | Preference Recorded | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordId": "R17",
"suppliedSupportChoice": "Support A",
"preferenceRecorded": true
},
"output": {
"token": "[\"R17\",\"Support A\",true]"
}
}Limitations and assumptions
- The result records supplied values without deciding consent validity or assigning support needs. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the person's recorded preferences and actual resource or route with the complete accessibility requirements. Test the relevant output and physical arrangement directly; a display token, scalar clearance or nominal playback ratio does not verify suitability or access.
References
Similar or alternative tools
- Caption Speaker Identification Token
Qualify an explicit caption speaker label by source.
- Alternative Format Print Audio Unit Pair
Preserve explicit alternative-format print and audio unit labels.