{
 "scenario": "form1-browse",
 "counts": {
  "match": 59,
  "tolerated": 0,
  "waived": 3,
  "defect": 0,
  "unmapped": 0,
  "harness": 0
 },
 "pairs": {},
 "pairs_by_draw_order": [],
 "waivers": [
  {
   "id": "S1",
   "status": "proposed",
   "title": "Screen-reader announcement of the COURSE_NO item read as a message",
   "reason": "After the cursor enters COURSE.COURSE_NO by record navigation (Next Record, the first record of a query, the Hide Student Count button), the Forms 14.1.2 Java client announces the item for assistive technology: its prompt or hint (\"Course No.\" in QAFE_FORM1, \"Course No Required\" in QAFE_FORM3) followed by the current value, e.g. \"Course No.454\". The recorder reads this accessible text where the message line lives, but nothing is written to the visible message line (the screenshots of those steps show an empty status bar) and no form code issues it. A browser target leaves screen-reader announcements to the browser (the item's label is its accessible name), so the visible message line stays empty, as on screen in the source. Only these announcement values are waived; every other message is still compared.\n",
   "applied": 3
  }
 ],
 "groups": [
  {
   "class": "waived",
   "group": "ui.message",
   "rule": "waiver:S1",
   "note": null,
   "count": 3,
   "where": [
    "step01.message",
    "step02.message",
    "step03.message"
   ]
  }
 ],
 "entries": [
  {
   "where": "step01.message",
   "class": "waived",
   "source": "Course No.454",
   "target": "",
   "rule": "waiver:S1",
   "note": null,
   "group": "ui.message"
  },
  {
   "where": "step02.message",
   "class": "waived",
   "source": "Course No.455",
   "target": "",
   "rule": "waiver:S1",
   "note": null,
   "group": "ui.message"
  },
  {
   "where": "step03.message",
   "class": "waived",
   "source": "Course No.454",
   "target": "",
   "rule": "waiver:S1",
   "note": null,
   "group": "ui.message"
  }
 ]
}