ACCESSIBILITY ISSUE RECORD
Purpose: connect a reproducible barrier to ownership, repair and verification.
Use with https://yenra.com/software-to-track-accessibility-status/
Reference: https://www.w3.org/WAI/planning-and-managing/implement/
Copy one block per finding. Use test data and redact private evidence.
This record describes its test scope; it is not a conformance certificate.

Identifier / reported date / reporter:
Affected task / URL or component / account role / state:
Browser, OS, device, access tools and versions:
Steps to reproduce:
Observed behavior / expected result:
User impact and essential task affected:
Evidence location:
Standard/version and criterion if assessed:
Validation result / reviewer / date:
Shared cause / related occurrences / duplicate links:
Priority and reason:
Owner / agreed action / target date:
Status: reported / validated / assigned / ready for retest / verified / reopened
Blocked or deferred reason / decision-maker / review date:
Interim access route / owner / adequacy review:
Changed source / build / deployment scope:
Retest steps / environment / reviewer / date / result:
Remaining limits / regression check / next review:

ILLUSTRATIVE ENTRY A-014 (fictional)
Booking dialog keeps keyboard focus on Close, preventing date selection.
Owner: shared dialog maintainer. Retest: open, choose date, submit and close;
then check another page using the component. If that page uses an older
version, keep its deployment task open even after the main repair succeeds.

ILLUSTRATIVE COUNT
20 validated open findings - 8 verified repairs + 5 new findings = 17 open.
This is a register total, not the percentage of site accessibility.