feat: a shared date and time picker

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html, rust

Research direction

Read §4.5's native-first rule and the §13.7.5 checklist in the tracking issue #776 before anything else, then confirm the four blockers (Input/text field, Popover, Button, Lucide Icon) have landed. Start with the native <input type="date">/"time"/"datetime-local" path and only add a Popover calendar where native falls short, applying the ARIA date-picker grid pattern, jiff time-zone display and l10n formats. Done means the component plus gallery entry, axe-core and ARIA snapshot rows, a §4.5 contract row, and keyboard-only scenarios passing WCAG 2.2 AA.

Written by the indexing model from the issue text.

Description

accessibility enhancement

Part of #776.

A shared date and time field: native <input type="date">, "time" and "datetime-local" first (§4.5's native-first rule), with a calendar in a Popover only where the native control falls short, the ARIA date-picker grid pattern if built, times shown in the page's time zone through jiff's rules, and every format through l10n.

Needs first: Input and text field, Popover, Button, Icon (Lucide) (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.