№ 171 / Wayfinding
Slope arrow
Put a direction marker on the actual incline when explaining an accessible route.
IN EVERYDAY WORDS
Put a direction marker on the actual incline when explaining an accessible route. Lift the far end of the ramp.
The look
The ramp angle grows while its rise and direction remain tied to the same endpoints. Keep the type and annotation in a listing presentation as the visual subject.
Say this to a designer
On my type and annotation in a listing presentation, lift the far end of the ramp. Show “Level” and “Sloped”. Put a direction marker on the actual incline when explaining an accessible route.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- The visitor controls “Raise the ramp” with touch, pointer or arrow keys.
- entrance
- Begin with the recognizable state “Level” in view.
- path
- The ramp angle grows while its rise and direction remain tied to the same endpoints.
- timing
- Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds.
- easing
- Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay.
- hold
- Hold “Sloped” while the viewer inspects the result or opens the brief.
- exit
- Keep the complete original wording available to read, select and speak at every stage.
The vocabulary
- Raise the ramp
- Put a direction marker on the actual incline when explaining an accessible route.
- Reference endpoints
- “Level” and “Sloped” define the two checkable states of this effect.
Make it fit your project
Good places to use it: type and annotation in a listing presentation, wayfinding example.
Apply this to the type and annotation in a listing presentation when the visitor needs to see the change from “Level” to “Sloped”.
Watch for: Keep the complete original wording available to read, select and speak at every stage.
When motion is off: Show the two named states “Level” and “Sloped” on demand. Keep automatic movement off.
Implementation and accessibility
- Lift the far end of the ramp.
- Start in “Level”. Bind the control “Raise the ramp” to one reversible value between zero and one.
- The ramp angle grows while its rise and direction remain tied to the same endpoints.
- Keep the complete original wording available to read, select and speak at every stage.
- Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard.
- Give “Raise the ramp” an accessible name and keyboard controls.
- Expose the before and after descriptions as text.
- Load the active study’s assets on demand. Stop rendering while its stage is off screen.
Give it to your AI
Download the working source and example assets. Match this reference number in the included catalog to its renderer.
Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.
Read the full prompt
Use AI Acceleration Design Ref #171 (Slope arrow, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/171. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Put a direction marker on the actual incline when explaining an accessible route. DESIGN REF #171 · Slope arrow In everyday words: Put a direction marker on the actual incline when explaining an accessible route. Lift the far end of the ramp. The look: The ramp angle grows while its rise and direction remain tied to the same endpoints. Keep the type and annotation in a listing presentation as the visual subject. Say this to a designer: On my type and annotation in a listing presentation, lift the far end of the ramp. Show “Level” and “Sloped”. Put a direction marker on the actual incline when explaining an accessible route. Motion direction (starting points to adapt): Trigger: The visitor controls “Raise the ramp” with touch, pointer or arrow keys. Entrance: Begin with the recognizable state “Level” in view. Path: The ramp angle grows while its rise and direction remain tied to the same endpoints. Timing: Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds. Easing: Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay. Hold: Hold “Sloped” while the viewer inspects the result or opens the brief. Exit: Keep the complete original wording available to read, select and speak at every stage. Design vocabulary: Raise the ramp: Put a direction marker on the actual incline when explaining an accessible route. Reference endpoints: “Level” and “Sloped” define the two checkable states of this effect. Reduced motion: Show the two named states “Level” and “Sloped” on demand. Keep automatic movement off. Implement: 1. Lift the far end of the ramp. 2. Start in “Level”. Bind the control “Raise the ramp” to one reversible value between zero and one. 3. The ramp angle grows while its rise and direction remain tied to the same endpoints. 4. Keep the complete original wording available to read, select and speak at every stage. 5. Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Show the two named states “Level” and “Sloped” on demand. Keep automatic movement off. Accessibility: Give “Raise the ramp” an accessible name and keyboard controls. Expose the before and after descriptions as text. Performance: Load the active study’s assets on demand. Stop rendering while its stage is off screen. Avoid: Keep the complete original wording available to read, select and speak at every stage. Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.
Permanent reference #171 · version 1. Pairs with #193, #003.