lighthouse fixes
This commit is contained in:
@@ -97,3 +97,23 @@ The theme MUST keep text readable and interactive affordances obvious, including
|
||||
#### Scenario: High contrast theme improves readability
|
||||
- **WHEN** the user enables `high-contrast` theme
|
||||
- **THEN** primary text and secondary UI labels remain clearly readable and interactive elements are visually distinct
|
||||
|
||||
### Requirement: Interactive elements use correct semantics
|
||||
Interactive elements MUST use correct semantic elements:
|
||||
|
||||
- Navigation MUST use anchors (`<a>`) with valid `href`.
|
||||
- Actions that do not navigate MUST use `<button>`.
|
||||
|
||||
The site MUST NOT render anchor elements that lack an `href` attribute.
|
||||
|
||||
#### Scenario: Modal triggers are buttons
|
||||
- **WHEN** a content card opens the media modal
|
||||
- **THEN** the card is a `<button>` element and is keyboard operable
|
||||
|
||||
#### Scenario: Navigation CTAs are anchors
|
||||
- **WHEN** a user sees a CTA that navigates to another page
|
||||
- **THEN** the CTA is an `<a>` element with a valid `href`
|
||||
|
||||
#### Scenario: No non-crawlable anchors exist
|
||||
- **WHEN** a crawler inspects the rendered HTML
|
||||
- **THEN** there are no `<a>` elements without `href`
|
||||
|
||||
Reference in New Issue
Block a user