Skip to content

Main content

Tactile Dot Cell Rotation

Rotate an explicit six-dot cell by 180 degrees in standard column-based dot order without interpreting a Braille character.

Loading tool…

Description

Permute six supplied dot flags under a half-turn policy.

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.

Permute six supplied dot flags under a half-turn policy.

When to use this tool

Use Tactile Dot Cell Rotation when you already have dots, halfTurn and need to permute six supplied dot flags under a half-turn policy.

How to use the tool and how it works

  1. Enter dots, halfTurn. 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 rotatedDots. Use the output convention below.

Require exactly six Boolean entries; for halfTurn=true return source positions [6,5,4,3,2,1], otherwise copy the six flags.1

Input fieldMeaning and unitsAccepted input
dotsDotsRequired. Array of boolean; minimum items 6; maximum items 6.
halfTurnHalf TurnRequired. Boolean.
Output fieldInterpretationReturned shape
rotatedDotsFor a half-turn use source positions [6,5,4,3,2,1]; exactly six Boolean slots, not a character decoder.Required. Array of boolean; minimum items 6; maximum items 6.
json
{
  "input": {
    "dots": [
      true,
      false,
      false,
      false,
      false,
      false
    ],
    "halfTurn": true
  },
  "output": {
    "rotatedDots": [
      false,
      false,
      false,
      false,
      false,
      true
    ]
  }
}

Limitations and assumptions

  • Positions refer to the supplied array order. No Braille character, language, eight-dot cell, physical embossing or readable output is validated.
  • 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

  1. Calculation and input contract: disability-studies/tactile-dot-cell-rotation — tool.io

Similar or alternative tools