You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2026/08/30 18:35:55 UTC

(causeway) 06/07: docs(openspec): archive localized date accessibility

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch htmx
in repository https://gitbox.apache.org/repos/asf/causeway.git

commit cb009cdd1c593a4097aa91735b47f7799fb7a964
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Sun Aug 30 20:29:58 2026 +0200

    docs(openspec): archive localized date accessibility
---
 .../.openspec.yaml                                 |  0
 .../design.md                                      |  0
 .../proposal.md                                    |  0
 .../specs/domain-web-components/spec.md            |  0
 .../specs/vaadin-semantic-editor-families/spec.md  |  0
 .../tasks.md                                       |  0
 openspec/specs/domain-web-components/spec.md       | 24 ++++++++++++++++++++++
 .../specs/vaadin-semantic-editor-families/spec.md  | 24 ++++++++++++++++++++++
 8 files changed, 48 insertions(+)

diff --git a/openspec/changes/localize-date-editor-accessibility/.openspec.yaml b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/.openspec.yaml
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/.openspec.yaml
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/.openspec.yaml
diff --git a/openspec/changes/localize-date-editor-accessibility/design.md b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/design.md
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/design.md
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/design.md
diff --git a/openspec/changes/localize-date-editor-accessibility/proposal.md b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/proposal.md
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/proposal.md
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/proposal.md
diff --git a/openspec/changes/localize-date-editor-accessibility/specs/domain-web-components/spec.md b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/specs/domain-web-components/spec.md
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/specs/domain-web-components/spec.md
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/specs/domain-web-components/spec.md
diff --git a/openspec/changes/localize-date-editor-accessibility/specs/vaadin-semantic-editor-families/spec.md b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/specs/vaadin-semantic-editor-families/spec.md
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/specs/vaadin-semantic-editor-families/spec.md
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/specs/vaadin-semantic-editor-families/spec.md
diff --git a/openspec/changes/localize-date-editor-accessibility/tasks.md b/openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/tasks.md
similarity index 100%
rename from openspec/changes/localize-date-editor-accessibility/tasks.md
rename to openspec/changes/archive/2026-08-30-localize-date-editor-accessibility/tasks.md
diff --git a/openspec/specs/domain-web-components/spec.md b/openspec/specs/domain-web-components/spec.md
index f09abf2215e..bba62d5e500 100644
--- a/openspec/specs/domain-web-components/spec.md
+++ b/openspec/specs/domain-web-components/spec.md
@@ -1994,3 +1994,27 @@ The default treatment MUST use a light neutral background, dark text, a visible
 - **WHEN** an application installs only the structural component styles
 - **THEN** equivalent high-contrast light tooltip fallback values remain effective
 - **AND** tooltip content remains readable and visually bounded
+
+### Requirement: Locale-aware local-date presentation
+Qualified local-date editors SHALL format and parse visible calendar dates according to the active document language, falling back to the browser locale and then a safe default when no valid document language is available.
+Locale presentation MUST NOT change the ISO lexical value retained by the temporal codec, pending interaction state, validation, or GraphQL submission.
+
+#### Scenario: Document declares a non-US date convention
+- **WHEN** a qualified `LocalDate` or `LocalDateTime` date portion is presented under a document language whose numeric date order differs from the default US order
+- **THEN** the visible date uses that document language's numeric order and separators
+- **AND** the underlying semantic value remains the same ISO local date
+
+#### Scenario: User enters a localized date
+- **WHEN** the user enters a valid date in the active locale's displayed numeric format
+- **THEN** the picker resolves the corresponding calendar date
+- **AND** the existing temporal codec receives its ISO lexical representation without timezone conversion
+
+#### Scenario: Locale is absent or invalid
+- **WHEN** the document has no valid language declaration
+- **THEN** the adapter uses the browser locale when available and otherwise its safe default
+- **AND** the field family does not fail solely because locale metadata is absent or malformed
+
+#### Scenario: Localized calendar opens
+- **WHEN** the platform exposes localized month names, weekday names, and first-day-of-week information
+- **THEN** the date chooser uses those locale settings
+- **AND** date selection still produces the same ISO local semantic value
diff --git a/openspec/specs/vaadin-semantic-editor-families/spec.md b/openspec/specs/vaadin-semantic-editor-families/spec.md
index 4b0908c7ab8..62329a04bd2 100644
--- a/openspec/specs/vaadin-semantic-editor-families/spec.md
+++ b/openspec/specs/vaadin-semantic-editor-families/spec.md
@@ -139,3 +139,27 @@ The policy MUST retain `style-src-attr 'none'` and MUST NOT add blanket `unsafe-
 - **WHEN** a control requires blanket inline style permission, external assets, telemetry, Pro code, Flow state, or another excluded capability
 - **THEN** that family fails qualification and remains native
 - **AND** no broader policy is enabled to make the candidate appear successful
+
+### Requirement: Accessible local-date calendar trigger
+Each editable qualified Vaadin date picker SHALL expose its calendar trigger as a field-labelled button in the normal sequential keyboard focus order.
+Keyboard use of the trigger MUST preserve Causeway-owned pending value, validation, commit, cancellation, and focus semantics.
+
+#### Scenario: Keyboard user reaches the calendar trigger
+- **WHEN** focus is in an editable qualified date input and the user presses Tab
+- **THEN** focus moves to the associated calendar trigger
+- **AND** the trigger's accessible name identifies the calendar and semantic field
+
+#### Scenario: Keyboard user opens the calendar
+- **WHEN** the focused calendar trigger receives Enter or Space
+- **THEN** the existing Vaadin calendar overlay opens for date selection
+- **AND** no property commit, action-parameter commit, submission, or cancellation occurs merely because focus moved to or activated the trigger
+
+#### Scenario: Date control is not operable
+- **WHEN** a qualified date control is read-only or disabled
+- **THEN** it does not expose an operable calendar trigger in the Tab sequence
+- **AND** its existing read-only or disabled semantic state remains authoritative
+
+#### Scenario: Pinned toolkit structure drifts
+- **WHEN** the pinned Vaadin date picker no longer exposes the qualified internal calendar affordance
+- **THEN** browser qualification fails with the missing keyboard contract identified
+- **AND** applications are not required to address Vaadin shadow-DOM structure directly