# accessibility-blind.txt
# version: 1
# site: Pico — desktop companion
# language: en (with short Arabic passages)
# site-key: unknown

## PAGES

[page: home]
url: index.html
purpose: One-page introduction to Pico, a Windows desktop companion (notch, voice, Telegram control, skills, automations, website publishing).
requires: nothing
sections:
  - header: brand link and main menu (nav-home, nav-features, nav-how, nav-trust, nav-arabic, nav-faq, nav-cta). On small screens the menu is hidden behind nav-menu-toggle.
  - hero: introduction and an animated notch demo (hero-talk, hero-explore). The demo's current line is in data-ai-status=notch-demo.
  - features (#features): six cards describing the notch, voice, Telegram control, skills, automations and website publishing. Read only, no actions.
  - how (#how): three steps — ask, approve the plan, done. Read only.
  - trust (#trust): the safety rules Pico follows. Read only.
  - arabic (#arabic): the same idea in Arabic, right-to-left. Read only.
  - day: a sample day timeline. Read only.
  - faq (#faq): expandable questions faq-what, faq-telegram, faq-skills, faq-publish, faq-safety.
  - cta (#meet): closing call to action (cta-talk, cta-top).
actions:
  - skip-to-content: jumps past the header to the main content.
  - nav-home: scrolls to the top.
  - nav-menu-toggle: opens or closes the menu on small screens.
  - nav-features / nav-how / nav-trust / nav-arabic / nav-faq: scroll to that section.
  - nav-cta: scrolls to the closing section.
  - hero-talk: plays the notch demo animation; read data-ai-status=notch-demo for the lines it shows.
  - hero-explore: scrolls to the features section.
  - faq-<topic>: click to open or close that question; the answer appears inside it.
  - cta-talk: scrolls back to the demo and plays it.
  - cta-top: scrolls to the top.

## FLOWS

[flow: learn what Pico does]
steps:
  1. click nav-features
  2. read the six feature cards in order

[flow: watch the demo]
steps:
  1. click hero-talk
  2. read data-ai-status=notch-demo a few times as it changes

[flow: read an FAQ answer]
steps:
  1. click nav-faq
  2. click the matching faq-<topic> (what, telegram, skills, publish, safety)
  3. read the opened answer

## RULES
- The site has no forms, logins, payments or irreversible actions.
- Arabic passages are right-to-left; read them as Arabic.
- Decorative visuals (mock screens, chat bubbles, permission card) are illustrations, not working controls.