Menu: Reference

Accessibility considerations

How to keep a tree readable for everyone, including people who cannot rely on color.

Why it matters

The standard notation tells node types apart by color. Color is fast, but it is not available to everyone:

Here is the same small tree, in grayscale, without and with text markers:

A tree in grayscale, without text markers 5 nodes and 4 arrows: 2 root / problem, 1 action / intervention, 1 artifact / deliverable, 1 desired state / outcome. A text version follows the diagram. Documentation isout of date Setting up alaptop takes aweek Write a one-pagestarter guide Laptop setupscript New hires shipsomething intheir firstmonth Legend Root / Problem Action / Intervention Desired State / Outcome Artifact / Deliverable Influences Attacks Flow: roots (bottom) → outcomes (top).
Without color, the node types blur together. Which nodes are problems?
Diagram as text: A tree in grayscale, without text markers

Nodes:

  • Root / Problem: "Documentation is out of date"
  • Root / Problem: "Setting up a laptop takes a week"
  • Action / Intervention: "Write a one-page starter guide"
  • Desired State / Outcome: "New hires ship something in their first month"
  • Artifact / Deliverable: "Laptop setup script"

Arrows:

  • "Documentation is out of date" influences "Write a one-page starter guide"
  • "Write a one-page starter guide" influences "New hires ship something in their first month"
  • "Laptop setup script" influences "New hires ship something in their first month"
  • "Laptop setup script" attacks "Setting up a laptop takes a week"
The same tree in grayscale, with text markers 5 nodes and 4 arrows: 2 root / problem, 1 action / intervention, 1 artifact / deliverable, 1 desired state / outcome. A text version follows the diagram. [P]Documentation isout of date [P]Setting up alaptop takes aweek [A]Write a one-pagestarter guide [D]Laptop setupscript [O]New hires shipsomething intheir firstmonth Legend [P] Root / Problem [A] Action / Intervention [O] Desired State / Outcome [D] Artifact / Deliverable Influences Attacks Flow: roots (bottom) → outcomes (top).
With text markers, every type stays readable, with or without color.
Diagram as text: The same tree in grayscale, with text markers

Nodes:

  • Root / Problem: "Documentation is out of date"
  • Root / Problem: "Setting up a laptop takes a week"
  • Action / Intervention: "Write a one-page starter guide"
  • Desired State / Outcome: "New hires ship something in their first month"
  • Artifact / Deliverable: "Laptop setup script"

Arrows:

  • "Documentation is out of date" influences "Write a one-page starter guide"
  • "Write a one-page starter guide" influences "New hires ship something in their first month"
  • "Laptop setup script" influences "New hires ship something in their first month"
  • "Laptop setup script" attacks "Setting up a laptop takes a week"

A tree that relies on color alone excludes some readers. The options below make it readable for everyone.

Text markers

The simplest option: add a short marker to each node, next to its text.

Node type Marker
Root / Problem [P]
Action / Intervention [A]
Desired State / Outcome [O]
Artifact / Deliverable [D]

Every Tree of Influence on this website uses text markers, except the comparison above.

Shape variants

Tools with several node shapes, such as Miro, Mural, and Lucidchart, let you give each type its own shape instead of, or in addition to, markers. There is no prescribed mapping. Any consistent one works, as long as the legend documents it. For example:

Node type Shape (example only)
Root / Problem Square
Action / Intervention Parallelogram
Desired State / Outcome Rounded rectangle
Artifact / Deliverable Diamond

Shapes are slower to work with than markers, because people have to pick a shape for every node. Use markers during live sessions, and consider shapes when a tree is being drawn deliberately, for example when cleaning it up to share.

Using shapes replaces the "one shape for every node" default. Say so in the legend.

Text contrast

Node text must be easy to read against its color:

See colors and shapes for the standard colors and text colors.

Sharing a tree

Board tools are mostly invisible to screen readers. When you share a tree with people who were not in the room, consider adding a text version: a list of the nodes by type, and a list of the arrows ("Documentation is out of date" influences "New hires ship something in their first month"). Every diagram on this website has one, under "Diagram as text."

How the accessibility layer works

Still being explored

Text markers and shapes address color vision. Other needs, such as cognitive load during large sessions or participation in physical sessions, have not been studied yet. If you have adapted the Tree of Influence for an accessibility need, share what you learned.