Skip to content
EG/

BFSG Check / Sample report

Sample report

The findings shown are synthetic examples and are not from a real customer scan.

01Sample finding
HighPriority
WCAG 1.3.1 / 3.3.2Technical reference

01 / Prioritized

See what a finding looks like.

#01 / FormsHigh

Form field has no associated label

An input has no programmatically associated label. Screen reader users may not know what information it expects.

/contact · 3 occurrences · WCAG 1.3.1 / 3.3.2

Recommendation: Associate the visible label with the input using matching for and id attributes.

Evidence, affected pages and references

Evidence: Example: An input on /contact has no programmatically associated label.

  • /contact

WCAG: 1.3.1, 3.3.2

02 / Methodology and limitations

How a report is prepared.

Automatically detectable WCAG-related findings are grouped by cause and prioritized. A complete BFSG or WCAG assessment also requires manual testing.

The findings shown are synthetic examples and are not from a real customer scan.

Check for free →

03 / Worked technical example

From evidence to recommendation

All values and locations below are synthetic examples. They show how a report separates evidence, interpretation, and the next verification step.

Example: contact-form label

On /contact, three fields have visible labels. One label points to for="email", but its input has a different id. Visible text alone does not establish an accessible name for that input.

  • Evidence: affected URL, element selector, and observed for/id values.
  • Possible impact: a screen reader user may not hear the field purpose.
  • Recommendation: match for and id, then verify with keyboard and a screen reader.

The automated check can identify this technical defect. It cannot establish complete form usability or BFSG conformity.

Start your own check → · All checks and audits →