Skip to content

Main content

Access Request Preferred Format Tool

Compare an explicit access-format preference with a supplied availability list without treating an unlisted preference as unreasonable.

Loading tool…

Description

Check exact membership in availableFormats and label available or not listed.

Accessibility decisions depend on the person, context, content, and relevant design requirements. A supplied measurement or formatting check addresses one condition and cannot establish that an entire interface, sign, or space is accessible.

Check exact membership in availableFormats and label available or not listed.

When to use this tool

Use Access Request Preferred Format when you need one documented accessibility component under a supplied criterion.

How to use the tool and how it works

  1. Enter requestCode, preferredFormat, availableFormats. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read available, label. Inspect available before interpreting the associated values.

Require nonempty requestCode and preferredFormat. Check exact membership in availableFormats and label available or not listed.1

Input fieldMeaning and unitsAccepted input
requestCodeRequest CodeRequired. Text; maximum UTF-16 length 8192.
preferredFormatPreferred FormatRequired. Text; maximum UTF-16 length 8192.
availableFormatsAvailable FormatsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
availableAvailableRequired. Boolean.
labelFormatted label for the supplied components under the convention above.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "requestCode": "R17",
    "preferredFormat": "large-print",
    "availableFormats": [
      "audio",
      "large-print"
    ]
  },
  "output": {
    "available": true,
    "label": "R17; preferred format=large-print; available"
  }
}

Limitations and assumptions

  • Format labels are supplied and unnormalized; actual accessible delivery, usability, individual needs, and accommodation obligations are not verified.
  • 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

Evaluate the complete experience with relevant guidance, appropriate expertise, and people who use the access features.

References

  1. Calculation and input contract: disability-studies/access-request-preferred-format — tool.io

Similar or alternative tools