Skip to content

Applications ​

The full-screen application pages: mail, chat, kanban, files, calendar, contacts, notes and tasks, plus the support-ticket queue and one ticket, the administration side of user accounts, the project portfolio, the four pages of the blog and the three of the CRM. The first eight share the split-view shell and are where the layout system is most exercised; the fifteen that follow them deliberately do not — see the notes under the catalogue.


The catalogue ​

AppPathPanesKey components
Mail/apps/mail.html3Split view, list virtualisation, editor
Chat/apps/chat.html2Message list, composer, presence, WebSocket
AI assistant/apps/assistant.html1Message list, prompt composer, suggested prompts, model picker
Kanban/apps/kanban.html1Sortable, drag-and-drop, card modal
File manager/apps/files.html2Tree, grid/list toggle, upload, preview
Calendar/apps/calendar.html2Month, week, day and year views, event modal, filters
Contacts/apps/contacts.html2Alphabetical list, detail panel
Notes/apps/notes.html2Editor, tag filter, autosave
Tasks/apps/tasks.html1List, inline edit, due dates, filters
Support tickets/apps/tickets.html1Datagrid, status chips, KPI tiles
Ticket detail/apps/ticket.html1.av-message thread, .av-timeline history, initTicket
Users/apps/users.html1Datagrid, status chips, bulk bar
User detail/apps/user.html1.av-profile-hero, .av-timeline, initUser
Permissions/apps/permissions.html1.av-matrix, .av-segmented, initAccess
Projects/apps/projects.html1Datagrid, status chips, KPI tiles
Project overview/apps/project.html1.av-steps, .av-progress, .av-tasks, initProject
New project/apps/project-new.html1.av-steps, initWizard, initValidate
Posts/apps/posts.html1Datagrid, status chips, KPI tiles, initPosts
Blog feed/apps/blog.html1.av-card--media, .av-grid--cards, initNotifFilters
Post detail/apps/post.html1.av-timeline, initModeration, initCharts
Edit post/apps/post-edit.html1Quill, .av-checklist, initPublish, initFormHelpers
Companies/apps/companies.html1Datagrid, relationship chips, KPI tiles
Deals/apps/deals.html1Datagrid, .av-detail-list legend, initPipeline
Leads/apps/leads.html1.av-customer-card, .av-chip, initLeads

The two ticket pages use the ordinary page shell, not the split view. A support queue is a table with filters, and a ticket is a record with a conversation on it — neither is a list beside a reading pane. They borrow the chat component's inner parts rather than the component itself: .av-chat is block-size: 100% over three grid rows so that only its log scrolls, which is right in a pane and wrong on a page that scrolls as a whole. .av-chat__messages and .av-chat__composer carry their own padding and border, so they stand in for .av-card__body and .av-card__footer instead of nesting inside them.

The three user pages are the administration side, and account/ is the tenant side. They look like a pair because both list people, and they answer different questions. account/members.html is a workspace looking at its own team and its seat count; apps/users.html is whoever runs the product looking at every account in it, which is why it carries the workspace column, the sign-in method and the two moderation states — suspended and dormant — that a team page has no use for.

The same split explains why apps/permissions.html is not a second copy of account/roles.html. The roles screen is role-first: edit a role, and everyone holding it changes. The permissions screen is person-first: it shows what one role grants, the exception set on top of it for one person, and the outcome the two resolve to. Nothing on it states that outcome independently — initAccess writes every effective badge and both summary figures from one pass over the rows, because a permissions page whose header disagrees with its table is not a cosmetic defect. npm run test:access recomputes each resolution itself rather than reading the page's answer back.

The projects cluster is portfolio-first, and dashboards/projects.html is sprint-first. The dashboard answers "how is the work in flight going this fortnight" — burndown, workload, blocked items, one team. apps/projects.html answers "which of the things we committed to will land, and what do they cost", across every client. Same table component, a question the dashboard cannot be asked.

That list carries two badge columns that are not the same question, and says so on the page. Status is where somebody has put the project — planning, active, on hold, done — and moves only when they move it. Health is what the remaining work says about the dates, and nobody sets it by hand. A project can be Active and Late at once, and that pair is the reason a portfolio list exists.

initProject is what makes the second half of that true rather than decorative: the health badge, the completed-milestone count, the progress bar and the slip note all come out of one pass over the milestone list, so the header cannot contradict the milestones printed under it. Health is derived from slip against the baseline plan — a recorded fact — and deliberately not from the wall clock: a clock-derived badge would be equally defensible and would also mean a template that quietly reads "Late" in red six months after a buyer installs it. Four outcomes rather than two, because whether a project is in trouble and how are different questions. npm run test:projects resolves the milestones itself rather than reading the page back.

The blog is four pages and each answers a different question. apps/posts.html is the desk: every post in every state, in a table, because "who has it and how long have they had it" is a question about owners and elapsed days. apps/blog.html is the feed: the published posts at reader size, which is the only place a cover, an excerpt and the tag mix are visible at once — one of the six ships with no cover image, and no column on the desk can tell you that. apps/post.html is the record of one post: performance, comments awaiting moderation, and the whole edit history. apps/post-edit.html is the composer.

The desk's attention column is derived, and the figure in the banner above it comes out of the same pass, because a desk that says "five posts need somebody" over a table showing four is the number people plan the week from. Two rules in initPosts are worth copying. Idle is a recorded measurement, not a subtraction against today — the reasoning initProject records for schedule slip: a clock-derived desk fills with red six months after a buyer installs the template. And a scheduled post is never stalled; it is waiting on purpose, and only a slot it missed makes it loud. Four outcomes rather than two, because whether a post is in trouble and why are different questions.

initPublish on the composer is the same discipline applied to a form: one pass over the declared requirements writes each row's tick, its badge, the meter, the sentence underneath and whether the Publish button does anything. Blocking and advisory are different questions — a missing slug stops a post going out, a 74-character meta title does not — and exceeding a maximum never blocks, because nothing is missing. The button is neutered with aria-disabled and enforced by initActions, which also reads out the sentence the button is described by; a bare aria-disabled with nothing enforcing it is worse than no state at all. npm run test:blog resolves both panels itself rather than reading the pages back.

The CRM is three pages and none of them is the CRM dashboard.dashboards/crm.html answers "what shape is the pipeline in this month" — a stage chart, a leaderboard, an activity feed. apps/deals.html answers "what is it worth, and which of those numbers do we plan from", which is arithmetic and therefore a table.

apps/companies.html is an account list and apps/customers.html is a buyer list, and the page says so in an alert. A company holds a contract, a renewal date, seats and an owner; a customer holds orders, lifetime spend and an average order value. Not one column is shared, because not one question is — and npm run test:crm asserts exactly that, because the day ARR appears beside average order value the two pages are one page with two titles.

initPipeline writes the four figures, every weighted cell and the sentence under them from one pass. Four rules in it are decisions. Probability belongs to the stage, not the deal — it is read off the legend the page prints, so the configuration and the documentation are the same three lines, and two deals in one column cannot disagree. A won deal is revenue, not forecast; leaving it in counts it once in the number the quarter is planned from and again in the number it is measured by. A lost deal is not a nought-per-cent deal — it leaves the set entirely, which matters nowhere in the sums and decisively in the average, where the obvious implementation divides by every row. And committed is a subset of open, not a fourth bucket beside it.

initLeads grades a lead as the worst of its four answers, not their sum. Counting the yeses — the implementation every scoring plugin ships — calls three yeses and a no nearly qualified, and somebody spends an afternoon on a company that has already said no. A no is not an unknown either: one is an answer, the other is a question nobody has asked, and the difference is what makes the board's most useful figure possible — which question the team keeps forgetting. The chips carry their answer in words, because a green chip reading "Budget" and a red chip reading "Budget" are the same chip to anyone who cannot tell them apart by colour.

There is deliberately no filter on the lead board. The one filter worth having would be by grade, and grade is derived — a chip that could read it would mean writing the answer into the markup beside the signals it is computed from, which is two writers for the only claim the page makes.


The task list, and putting a second one on a page ​

The .av-tasks component ships whole on /apps/tasks.html and again, scoped to one project, on /apps/project.html. Its controls do not sit inside the list — the count belongs in the page or card header, the filter chips beside it, the add form above the rows — so the module cannot find them from the list element.

HookOnDoes
data-av-tasksulThe list. One module claim per list
data-av-tasks-scopeany ancestorThe region that owns one list and its controls
data-av-task-checkinput[type=checkbox]Completes a row
data-av-task-titleinput[type=text]The title, editable in place
data-av-task-duetimeRe-rendered, and worded Overdue when it is
data-av-task-filterbuttonall / open / done
data-av-task-countanywhere in scopeThe derived "N open · N shown" line
data-av-task-addformClones the first row rather than building one from a string

Declare the scope when a page has two lists. Without data-av-tasks-scope the controls are found from the document, which is right for exactly one list per page and quietly wrong for two: the second list's chips would drive the first, and its count would never be written at all. A page shipping a single list declares no scope and behaves as it always has.

html
<div class="av-card av-card--flush-body" data-av-tasks-scope>
  <div class="av-card__header">
    <p class="av-card__subtitle" data-av-task-count aria-live="polite">—</p>
    <button class="av-filter-chip" type="button" data-av-task-filter="open">Open</button>
  </div>
  <ul class="av-tasks" data-av-tasks>…</ul>
</div>

Do not write the accessible names in markup. The module names each row from its own title, on mount, on rename and on every row it clones. They were markup once, spelled aria-label="Mark complete: <title>", and that name kept saying it after the task was completed and after it was renamed — a name describing an action the control no longer performs. axe cannot see this: it checks that an accessible name exists, not that it is true. The checkbox is named for the task alone, because whether it is done is what the checkbox role already announces.


The split-view shell ​

The two- and three-pane apps share one structure. Mail is the three-pane case; chat, files, contacts and notes are the two-pane one.

html
<main class="av-content av-content--flush" id="main" tabindex="-1">
  <div class="av-split av-split--three" data-av-split>

    <nav class="av-split__nav" aria-label="Mailboxes">
      <button class="av-btn av-btn--primary av-btn--block" type="button"
              data-av-shortcut="c: Compose a message">
        <svg class="av-icon av-icon--sm" aria-hidden="true" viewBox="0 0 24 24">
          <path d="M4 20h4l10-10-4-4L4 16v4z"/><path d="M13.5 6.5l4 4"/>
        </svg>
        Compose
      </button>

      <ul class="av-menu">
        <li class="av-menu__item av-menu__item--active">
          <a class="av-menu__link" href="#inbox" aria-current="page">
            <svg class="av-icon av-menu__icon" aria-hidden="true" viewBox="0 0 24 24">
              <path d="M4 13h4l2 3h4l2-3h4"/><path d="M4 13l2-7h12l2 7v5H4z"/>
            </svg>
            <span class="av-menu__label">Inbox</span>
            <span class="av-menu__badge">12</span>
          </a>
        </li>
      </ul>
    </nav>

    <div class="av-split__list" role="region" aria-label="Messages">
      <div class="av-split__list-header">…</div>
      <ul class="av-mail-list">…</ul>
    </div>

    <div class="av-split__detail" role="region" aria-label="Message" tabindex="-1">…</div>

  </div>
</main>

.av-content--flush removes the page padding, because each pane owns its own. Only the panes scroll; the shell does not.

Mobile: one pane at a time ​

Below 768px the panes stack and data-av-split-view decides which one is on screen. initSplit owns three things, and the third is the one usually missed.

js
function showDetail(id, { push = true } = {}) {
  split.dataset.avSplitView = 'detail';
  if (push) history.pushState({ avSplit: 'detail', id }, '', `#item-${id}`);
  detail?.focus();
}

function showList(id) {
  split.dataset.avSplitView = 'list';
  const item = id && split.querySelector(`[data-av-split-item="${id}"]`);
  (item || split.querySelector('[data-av-split-item]'))?.focus();
}
  1. Back returns to the list, because opening a row pushes history. Most web apps get this wrong and drop the reader out of the app entirely.
  2. Focus follows the pane — into the detail region on open, and back onto the row you came from on return, not the top of the list.
  3. It only engages below 768px. Above that, both panes are on screen; there is nothing to switch between, and pushing history for a selection that changed nothing would make Back do nothing visible.

The URL fragment is #item-<id> rather than a query string, because these pages are built to open from file://, where history.pushState with a path throws.

A control inside a row is not a request to open it — initSplit ignores clicks that land on a nested button, input or link, which is what lets the star and the checkbox work on a phone.

[data-av-split-back] on a .av-split__back button returns to the list. It is visible only in the one-pane layout.


Mail ​

html
<li class="av-mail-row">
  <input class="av-check" type="checkbox" aria-label="Select message from Sarah Kim">
  <button class="av-mail-row__star" type="button"
          aria-label="Star message from Sarah Kim" aria-pressed="false">
    <svg class="av-icon av-icon--sm" aria-hidden="true" viewBox="0 0 24 24">
      <path d="M12 4l2.4 4.9 5.4.8-3.9 3.8.9 5.4-4.8-2.5-4.8 2.5.9-5.4L4.2 9.7l5.4-.8z"/>
    </svg>
  </button>
  <button class="av-mail-item is-unread" type="button" data-av-split-item="1"
          data-av-mail-box="inbox"
          data-av-mail-subject="Q3 report review"
          data-av-mail-from="Sarah Kim &lt;sarah@northwind.io&gt;">
    <span class="av-avatar av-avatar--sm" aria-hidden="true">SK</span>
    <span class="av-mail-item__body">
      <span class="av-mail-item__row">
        <span class="av-mail-item__from">Sarah Kim</span>
        <time class="av-timestamp" datetime="2026-08-12T09:14" data-av-relative-time>12m</time>
      </span>
      <span class="av-mail-item__subject av-truncate">Q3 report review</span>
      <span class="av-mail-item__preview av-truncate">Hi — I have gone through the draft and…</span>
    </span>
    <span class="av-mail-item__labels"><span class="av-chip">Work</span></span>
  </button>
</li>

Three controls, three siblings. The checkbox and the star are not inside the open button: a <button> may not contain interactive content, and tabindex="-1" on a nested control does not hide it from assistive technology — it only hides it from the keyboard, which is how the star shipped unreachable. Everything inside the open button is a <span>, because a button's content model is phrasing content; display: block in the stylesheet gives those spans a box.

The detail pane is .av-message-head (with __subject and __meta), .av-message-body and .av-message-actions. A source attribute and a target attribute must never share a name — the row carries data-av-mail-subject and the heading it fills carries data-av-mail-out="subject", after a version where both were called the same thing and the module matched the wrong one.

Keyboard shortcuts ​

Shortcuts are declared on the markup, not in a table in the module, as data-av-shortcut="key: description". One declaration binds the key and supplies the row in the help panel, so a shortcut cannot exist without being listed or be listed without working — the single-writer rule applied to a keyboard model.

Eight ship on the mail page:

KeyAction
j / kNext / previous message
EnterOpen message
eArchive
sStar or unstar
uBack to the list
cCompose
/Focus search

? opens the shortcut panel and is shell-wide rather than per page. A keyboard-driven app with no discoverable shortcut list is usable only by the person who built it.

[data-av-shortcuts-scope] narrows a page's bindings to one region, with [data-av-shortcut-shell] marking the handful that stay global. It began as a mail-only feature and became shell-wide when a second page wanted three keys.

The two guards a document-level shortcut needs ​

js
document.addEventListener('keydown', (e) => {
  if (IGNORE.has(e.target.tagName) || e.target.isContentEditable) return;
  if (e.ctrlKey || e.metaKey || e.altKey) return;
  // Enter and Space belong to whatever has focus.
  if ((e.key === 'Enter' || e.key === ' ') && e.target.closest?.(ACTIVATES)) return;
  …
});

The first guard is obvious: a single-letter key must not fire inside a search field. The second is the one that is easy to miss. The listener is on document, so binding Enter means calling preventDefault() on every button and link on the page whenever one has focus. The control looks focused, is announced correctly, and does nothing when pressed. It stays invisible for as long as every reachable control handles Enter in its own listener — which is why it survived here until the star became keyboard-reachable.

A modal is exempt for exactly two keys, not wholesale. An earlier version exempted the whole shortcut panel with a selector, so pressing t in front of the shortcut list toggled the colour mode behind it.

What this demo does not do ​

.av-message-body renders server-authored markup from the page itself. Nothing here sanitises, sandboxes or blocks remote images, because nothing here receives untrusted email.

If you connect a real mailbox, that becomes the most important code you will write. The shape of it: sanitise with DOMPurify (FORBID_TAGS including script, style, iframe, object, embed, form, link, base), render inside <iframe sandbox="allow-same-origin"> — withoutallow-scripts, so nothing runs even if sanitisation missed something — and rewrite src to data-blocked-src until the reader opts in, because remote images in email are tracking pixels. None of that is in this template, and the page should not imply it is.


Chat ​

html
<div class="av-chat">
  <div class="av-chat__header">
    <span class="av-avatar av-avatar--sm av-avatar--status" data-av-status="online"
          aria-hidden="true">DT</span>
    <div>
      <div class="av-chat__name">Design team</div>
      <div class="av-chat__meta">3 online</div>
    </div>
    <div class="av-chat__header-actions">…</div>
  </div>

  <div class="av-chat__messages" role="log" aria-live="polite" aria-atomic="false"
       aria-label="Messages">
    <div class="av-chat__day-divider"><span>Today</span></div>

    <article class="av-message">
      <span class="av-avatar av-avatar--sm" aria-hidden="true">SK</span>
      <div class="av-message__body">
        <div class="av-message__header">
          <span class="av-message__author">Sarah Kim</span>
          <time class="av-message__time" datetime="2026-08-14T09:14">09:14</time>
        </div>
        <div class="av-message__text">Draft is ready for review.</div>
        <div class="av-message__reactions">
          <button class="av-reaction is-active" type="button" aria-pressed="true"
                  aria-label="Thumbs up, 3 reactions">👍 <span>3</span></button>
        </div>
      </div>
    </article>

    <div class="av-chat__typing">
      <span class="av-typing-dots" aria-hidden="true"><i></i><i></i><i></i></span>
      Mark is typing…
    </div>
  </div>

  <form class="av-chat__composer" data-av-chat-composer>
    <button class="av-btn av-btn--ghost av-btn--icon" type="button" aria-label="Attach a file">…</button>
    <textarea rows="1" placeholder="Write a message…" aria-label="Message"
              aria-describedby="composerHint" name="text"></textarea>
    <p class="av-visually-hidden" id="composerHint">
      Press Enter to send, Shift plus Enter for a new line.
    </p>
    <button class="av-btn av-btn--primary av-btn--icon" type="submit" aria-label="Send message">…</button>
  </form>
</div>

role="log" with aria-live="polite" announces new messages without repeating the conversation. aria-atomic="false" is essential — with true, every new message re-reads the entire log.

.av-message--own is a message from the reader; .av-message--cont is a consecutive message from the same person, which drops the repeated avatar and name. .av-chat__new is the "new messages" pill.

The composer's keyboard contract is written into the page, in a visually-hidden paragraph the textarea points at with aria-describedby. Enter sends and Shift+Enter breaks the line — a convention a sighted reader infers from the placeholder and a screen-reader user cannot.

The conversation rail beside the thread is .av-convo with __row, __name, __preview and __time.

.av-chat is block-size: 100% over three grid rows, so only .av-chat__messages scrolls. That is right inside a pane and wrong on a page that scrolls as a whole, which is why the ticket pages borrow .av-chat__messages and .av-chat__composer rather than .av-chat itself.


Kanban ​

html
<div class="av-kanban" data-av-kanban>
  <section class="av-kanban__column av-kanban__column--todo" aria-labelledby="col-todo">
    <div class="av-kanban__header">
      <h2 class="av-kanban__title" id="col-todo">
        <span class="av-kanban__dot" aria-hidden="true"></span>
        To do
      </h2>
      <span class="av-kanban__count">8</span>
    </div>

    <ul class="av-kanban__list" data-av-sortable>
      <li class="av-kanban__card" tabindex="0">
        <div class="av-kanban__labels">
          <span class="av-chip av-chip--sm av-chip--primary">Design</span>
        </div>
        <h3 class="av-kanban__card-title">Update onboarding flow</h3>
        <footer class="av-kanban__card-foot">
          <span class="av-kanban__meta">
            <svg class="av-icon" aria-hidden="true" viewBox="0 0 24 24">
              <rect x="3" y="5" width="18" height="16" rx="2"/><path d="M3 10h18M8 3v4M16 3v4"/>
            </svg>
            <time datetime="2026-08-18">18 Aug</time>
          </span>
        </footer>
      </li>
    </ul>

    <button class="av-kanban__add" type="button">Add a card</button>
  </section>
</div>

The keyboard model is ours, not the vendor's ​

Sortable.js is pointer-only. Without a keyboard equivalent the board is unusable for a significant number of people, and nothing fails while it is missing.

KeyAction
SpacePick up, or drop
← / →Move to the previous / next column
↑ / ↓Move up / down within the column
EscCancel and return the card

Every move is announced — "Picked up Update onboarding flow. Use the arrow keys to move it, Space to drop, Escape to cancel.", then position and column as it travels. A card carries is-picked and aria-grabbed while held.

Bind the keyboard half first. The pointer half waits for Sortable.js to lazy-load, and a broken loader key would otherwise leave the board silently pointer-only with nothing failing.

Cards are added by cloning an existing node, never from an HTML string — the title is text a person typed.


File manager ​

html
<div class="av-files" data-av-files>
  <div class="av-files__toolbar">
    <h1>Files</h1>
    <span class="av-toolbar__count" data-av-file-count aria-live="polite">9 items</span>
    <div class="av-files__toolbar-spacer"></div>
    <div role="group" aria-label="View">
      <button class="av-btn av-btn--ghost av-btn--icon av-btn--sm" type="button"
              data-av-file-view="grid" aria-pressed="true" aria-label="Grid view">…</button>
      <button class="av-btn av-btn--ghost av-btn--icon av-btn--sm" type="button"
              data-av-file-view="list" aria-pressed="false" aria-label="List view">…</button>
    </div>
  </div>

  <div class="av-files__scroll">
    <ul class="av-file-list" data-av-file-list data-av-state="grid">
      <li>
        <button class="av-file" type="button" data-av-file-folder="brand" data-av-file-kind="PDF"
                data-av-file-name="brand-guidelines-v4.pdf" data-av-file-size="4.2 MB"
                data-av-file-modified="9 Aug 2026">
          <span class="av-file__icon av-file__icon--doc" aria-hidden="true">…</span>
          <span class="av-file__body">
            <span class="av-file__name">brand-guidelines-v4.pdf</span>
            <span class="av-file__meta">PDF · 4.2 MB</span>
          </span>
        </button>
      </li>
    </ul>
  </div>
</div>

Grid and list are one list in two states, not two lists. data-av-state on .av-file-list switches the layout in CSS; the DOM does not change, so selection and focus survive the toggle. A pair of separate containers would have to re-render, and a re-rendered container drops the reader's focus — the defect the datagrid's pagination bar shipped.

The view buttons carry aria-pressed rather than being a radio group. They are two toggles over one setting and the state is on the control, where a screen reader announces it.

The folder rail is .av-tree with .av-tree__link, __count and __twisty. It is a plain list of buttons with aria-current on the open folder — deliberately not role="tree". That role obliges you to supply treeitem, group, expanded state and the full arrow-key model, and a half-built tree announces a structure that does not respond the way it claims to. A list of buttons is honest and works.

.av-preview (with __frame and __name) is the detail pane; .av-storage is the quota meter.

Each file's data lives in data-av-* attributes on the button rather than being parsed out of the rendered text, so filtering and sorting read 4.2 MB as a value and not as a string to interpret.


Notes ​

html
<div class="av-split" data-av-split data-av-notes>
  <div class="av-split__list" role="region" aria-label="Notes">
    <div class="av-split__list-header">
      <h1 class="av-visually-hidden">Notes</h1>
      <div class="av-demo-row" role="group" aria-label="Filter by tag">
        <button class="av-filter-chip" type="button" data-av-note-tag="all" aria-pressed="true">All</button>
        <button class="av-filter-chip" type="button" data-av-note-tag="work" aria-pressed="false">Work</button>
      </div>
    </div>

    <ul class="av-note-list" data-av-note-list>
      <li>
        <button class="av-note-item" type="button" aria-current="true" data-av-split-item="1"
                data-av-note-tags="work"
                data-av-note-title="Q3 board pack — outline"
                data-av-note-saved="Saved at 15:48">
          <span class="av-note-item__title">Q3 board pack — outline</span>
          <span class="av-note-item__excerpt">Three slides on retention…</span>
          <span class="av-note-item__foot">…</span>
        </button>
      </li>
    </ul>
  </div>

  <div class="av-split__detail" role="region" aria-label="Note" tabindex="-1">
    <div class="av-note-editor">
      <div class="av-note-editor__head">
        <button class="av-btn av-btn--ghost av-btn--sm av-split__back" type="button"
                data-av-split-back>All notes</button>
        <label class="av-visually-hidden" for="noteTitle">Note title</label>
        <input class="av-note-editor__title" type="text" id="noteTitle"
               data-av-note-field="title" placeholder="Untitled note" autocomplete="off">
      </div>

      <label class="av-visually-hidden" for="noteBody">Note</label>
      <textarea class="av-note-editor__body" id="noteBody" data-av-note-field="body"
                placeholder="Start writing…"></textarea>

      <div class="av-note-editor__foot">
        <span class="av-save-state" data-av-note-state data-av-state="saved"
              role="status" aria-live="polite">
          <svg class="av-icon" aria-hidden="true" viewBox="0 0 24 24">…</svg>
          <span data-av-note-state-text>Saved</span>
        </span>
        <span data-av-note-saved-at>Saved at 15:48</span>
      </div>
    </div>
  </div>
</div>

The editor is a plain <textarea>, not Quill. A note is prose someone types, and the rich-text editor is documented under Editors where it enhances a real field.

Save state is an enumerated data-av-state, and the label follows it. The state and the words are one writer — data-av-note-state-text is written by the module that sets the attribute, so a page cannot show a tick beside the word "Saving".

If you wire autosave to a real endpoint ​

The demo saves nothing. The rules worth keeping when it does:

RuleReason
Debounce ~1.5s after typing stopsNot on every keystroke
Save on blur and on visibilitychangeCatches tab switches and closes
Show explicit status — "Saving…", "Saved 2m ago", "Not saved"Silence is indistinguishable from failure
Retry with backoffTransient network failures are common
Keep a local copySurvives a crash or an accidental close
Guard beforeunload while unsaved
js
addEventListener('visibilitychange', () => { if (document.hidden) flush(); });

Application page checklist ​

  • [ ] Only the inner panes scroll; the shell does not
  • [ ] Mobile pane switching pushes history so Back works, and only below the one-pane breakpoint
  • [ ] Focus moves to the detail pane on selection, and back to the originating row on return
  • [ ] A control inside a row does not open the row
  • [ ] Shortcuts are declared on the markup, so binding and help panel cannot disagree
  • [ ] A document-level shortcut never steals Enter or Space from a control
  • [ ] Shortcuts do not fire while typing in a field
  • [ ] Drag-and-drop has a complete keyboard equivalent, bound before the vendor loads, with announcements
  • [ ] Live regions used correctly — role="log" with aria-atomic="false" for chat
  • [ ] A view toggle changes state on one list rather than swapping containers and dropping focus
  • [ ] An ARIA role is either fully implemented or not claimed
  • [ ] Row data lives in data-av-* attributes, not parsed back out of rendered text
  • [ ] New nodes are cloned, never built from a template string, when they carry text a person typed
  • [ ] Every list item has a descriptive accessible name

Read next: E-commerce.

Documentation for @creativeigniter/adminvora