Light glass
Inspect all four corners and the gap between cards.
Glass response
The action opened this native popover.
VALIDATION
For every live component example, long content and all native form fields in one visit, open the complete manual-test page.
One repeatable page for navigation, glass and animated edges on a physical phone or desktop browser. Start with iPhone Safari, then repeat on desktop Firefox and Edge.
These pages describe RevaCSS 2.0.0 in development. Use the documentation build for a preview or build the stylesheets from source.
The recorded acceptance checks are resolved; the validation record identifies reviewers, scope and evidence limits.
Maintainer acceptance does not establish accessibility certification. Exact device and assistive-technology versions and a new screenshot baseline were not supplied with the latest visual sign-off.
These repeatable fixtures run without browser JavaScript. Automated engine checks and maintainer attestation are different forms of evidence; neither records a new pass for the device you are using now.
Page build: 4aed48713d4ed6b42ca08f73e75be0fca6fcd0bc. Keep this revision with your results.
If you prefer to keep motion reduced, E1 is not tested rather than failed. Review keyboard and screen-reader interactions separately from touch interactions.
The broad colour bands are a test backdrop. Compare the glass card with its solid exception. The glass should transmit a softened tint; the solid card should conceal the pattern.
Inspect all four corners and the gap between cards.
The action opened this native popover.
The shared Default palette stays in effect.
Palette and inheritance guideInspect all four corners and the gap between cards.
The action opened this native popover.
The shared Default palette stays in effect.
Palette and inheritance guideThese four cases explicitly use the Mono palette. Compare Animated with Plain for at least eight seconds. Movement belongs to the rim; the label and interior should stay steady.
The card and first button inherit the animated edge.
The card and first button inherit the animated edge.
The card and first button inherit the animated edge.
The card and first button inherit the animated edge.
The decorative rim did not block the tap.
P1 — Reduce Motion. On iPhone, use Settings → Accessibility → Motion → Reduce Motion. Return to Safari and reload. Decorative edge movement and popover/glide transitions should stop; navigation and controls must still work. Apple’s Reduce Motion instructions.
P2 — Reduce Transparency / Increase Contrast. In Settings → Accessibility → Display & Text Size, test these settings separately. When Safari exposes the corresponding CSS preference, glass falls back to opaque surfaces and increased contrast removes decorative edges. If the setting is not exposed, record unsupported rather than claiming the fallback was tested. Apple’s display accessibility instructions.
CSS Reduce Motion: not requestedrequested
CSS Reduce Transparency: not requested or unsupportedrequested
CSS Increased Contrast: not requested or unsupportedrequested
Backdrop blur: unsupported; opaque fallback expectedsupported; inspect actual rendering
Composite edge mask: unsupported; regular border expectedsupported; inspect the visible rim
These indicators use CSS feature and preference queries. They report what this browser exposes, not its model/version or a physical-device pass.
Copy this template and report any failed IDs with reproduction steps. An eight-second recording is more useful than a still image for an animation failure. The page does not store or submit results.
Device model:
OS version / browser version:
Page build revision:
Date / tester:
Orientation: portrait / landscape
Reduce Motion / Reduce Transparency / Increase Contrast:
Low Power Mode:
N1–N5: pass / fail / not tested
G1–G3: pass / fail / not tested
E1–E3: pass / fail / not tested
P1–P2: pass / fail / unsupported / not tested
Failure IDs, steps and screenshots/video:
Keyboard / VoiceOver: not tested unless separately reviewedFor a new release or regression report, provide fresh results with the build revision and device details. Existing release acceptance is recorded separately in the validation record above.