feat: a shared alert component

Open
#787 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html, rust

Research direction

Start by reading DESIGN.md §4.5 (contract row) and §13.7.5 (the checklist this component must satisfy), plus tracking issue #776 for the shared bar. Find the existing Icon and Button components in the Leptos UI crate and the gallery and axe-core/ARIA snapshot tests that already cover them, since the alert must follow the same pattern. The issue is blocked until Icon and Button land, so confirm those first; done means the component, its gallery entry, contract row, and passing axe-core, ARIA and keyboard-only scenarios.

Written by the indexing model from the issue text.

Description

accessibility enhancement

Part of #776.

A shared inline message for a page's state (information, success, warning, error): an Icon and words, never color alone, optionally dismissible with a Button. It is not a live region by itself; urgent text goes through the announcer's assertive region. One failure is said once (DESIGN.md).

Needs first: Icon (Lucide), Button (see "blocked by").

Acceptance: Meets the bar in the tracking issue: WCAG 2.2 AA in full when it merges, a contract row in §4.5, and every step of §13.7.5 (component, gallery entry, axe-core and ARIA snapshot rows, keyboard-only contract scenarios).

Dominant language
Rust
Stars
0
Forks
0
Avg merge
56m
Merged PRs (30d)
349

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nledford/Ladderback

All issues in nledford/Ladderback

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.