Finding reference

Semantic labeling accessibility issue

Retained automated accessibility evidence showed controls, links, form fields, regions, headings, or ARIA attributes with label, accessible-name, role, relationship, or name/role/value signals that may require semantic accessibility review. Review the evidence context, methodology, common causes, and reviewer questions for this CertScore finding.

Selected finding

Semantic labeling accessibility issue

MediumGood evidenceDirect observationAccessibilitySeen on ~17% of scanned top sites

Benchmark frequency is directional market context only. It is not a compliance benchmark, legal conclusion, or severity score. Rare findings may be top-ranked only when retained evidence is strong; common findings may remain medium when evidence is automated or context-dependent. Rarity is not severity, and prevalence is not compliance risk.

Observed

Why this matters

Clear labels, roles, and relationships help screen reader, voice control, keyboard, and cognitive-accessibility users understand what elements are, what they do, and how they relate to surrounding content. For review teams, this signal can help identify component, form, ARIA, or template patterns where visible labels and programmatic semantics may not align.

Detection methodology

CertScore retains representative automated accessibility evidence for semantic labeling and name/role/value checks, including the rule identifier, affected selector or element reference, page URL, impact label when available, and WCAG-oriented references. The finding is surfaced when retained evidence indicates that a control, link, form field, region, heading, ARIA attribute, or interactive element may have missing, ambiguous, invalid, or mismatched programmatic semantics. CertScore treats automated semantic-labeling results as review signals. The scanner does not infer full WCAG conformance or non-conformance from a single automated rule result. Reviewers should consider visible label text, accessible name computation, role, state, value, instructions, grouping, ARIA validity, component behavior, and whether the retained evidence reflects the user-visible and assistive-technology-relevant context.

Confidence semantics: Good when representative automated semantic-labeling evidence includes rule ID, selector or element reference, page context, impact label, and WCAG-oriented references; stronger when retained evidence also includes visible-label context, accessible-name or role context, repeated examples across components, and enough detail for manual verification. Manual review is still needed for semantic intent, assistive-technology behavior, and remediation quality.

Top-finding calibrationWhat must be retained to surface, top-rank, demote, or suppress this finding.

Minimum to surface

Automated label, name, or role rule with selector, page, and WCAG reference.

High confidence requires

Visible-label context.
Accessibility-name context.
Role context.

Top ranking requires

Required or sensitive form field.
Repeated component.
Blocking control.

Demote or suppress when

Selector only.
ARIA attribute only.
No affected element.

These rules describe ranking calibration for already-projected findings. They do not create findings from raw signals.

Example evidence

Semantic labeling example

rule=label
artifact=semantic_001
role=finding_supporting_artifact
url=https://example.com/signup
selector=[data-example-component="signup-form"] input[name="email"]
impact=serious
wcag_refs=1.3.1 Info and Relationships; 3.3.2 Labels or Instructions; 4.1.2 Name, Role, Value
element_type=form_field
detected_signal=missing_or_unassociated_label
visible_label_context=manual_review_recommended
accessible_name_context=manual_review_recommended
review_caveat=manual review should confirm visible label, accessible name computation, instructions, grouping, and whether the field purpose is clear to assistive-technology users

Review context

component=signup_form
possible_source=label_association_or_component_api
states_to_review=default, error, required, disabled, autocomplete
assistive_technology_review_needed=true
manual_review_needed=true

What should not count by itself

selector=input.email [insufficient_without_rule_and_page_context]
aria-label-present [audit_only_without_accessible_name_review]
component_name=TextField [audit_only_without_affected_element]
visual_label_nearby [requires_label_association_review]

View redacted sample JSON

Redacted sample JSON

{
  "findingId": "semantic_labeling_accessibility_issue",
  "label": "Semantic labeling accessibility issue",
  "category": "Accessibility",
  "criticality": "medium",
  "evidenceConfidence": "good",
  "directVsInferred": "direct_observation",
  "evidence": {
    "summary": "Retained automated accessibility evidence showed controls, links, form fields, regions, headings, or ARIA attributes with label, accessible-name, role, relationship, or name/role/value signals that may require semantic accessibility review.",
    "examples": [
      {
        "title": "Semantic labeling example",
        "lines": [
          "rule=label",
          "artifact=semantic_001",
          "role=finding_supporting_artifact",
          "url=https://example.com/signup",
          "selector=[data-example-component=\"signup-form\"] input[name=\"email\"]",
          "impact=serious",
          "wcag_refs=1.3.1 Info and Relationships; 3.3.2 Labels or Instructions; 4.1.2 Name, Role, Value",
          "element_type=form_field",
          "detected_signal=missing_or_unassociated_label",
          "visible_label_context=manual_review_recommended",
          "accessible_name_context=manual_review_recommended",
          "review_caveat=manual review should confirm visible label, accessible name computation, instructions, grouping, and whether the field purpose is clear to assistive-technology users"
        ]
      },
      {
        "title": "Review context",
        "lines": [
          "component=signup_form",
          "possible_source=label_association_or_component_api",
          "states_to_review=default, error, required, disabled, autocomplete",
          "assistive_technology_review_needed=true",
          "manual_review_needed=true"
        ]
      },
      {
        "title": "What should not count by itself",
        "lines": [
          "selector=input.email [insufficient_without_rule_and_page_context]",
          "aria-label-present [audit_only_without_accessible_name_review]",
          "component_name=TextField [audit_only_without_affected_element]",
          "visual_label_nearby [requires_label_association_review]"
        ]
      }
    ]
  }
}

Regulatory review context

Accessibility: semantic labels and programmatic meaning

Retained automated accessibility evidence showed label, accessible-name, ARIA, role, relationship, or name/role/value signals that may be relevant to WCAG-oriented accessibility review. Applicability depends on the affected element, component behavior, semantic intent, user impact, organization type, jurisdiction, and manual accessibility review.

WCAG 1.3.1 Info and RelationshipsWCAG 3.3.2 Labels or InstructionsWCAG 4.1.2 Name, Role, ValueWCAG 2.4.6 Headings and LabelsADA Title II web/mobile accessibility reviewADA Title III public accommodation accessibility reviewMore context in reference notes

View applicability notes

Legal and regulatory frameworks

WCAG 1.3.1 Info and Relationships (A)Visual structure, labels, groups, headings, or relationships are not programmatically determinable.
WCAG 3.3.2 Labels or Instructions (A)Inputs or required user actions lack adequate labels or instructions.
WCAG 4.1.2 Name, Role, Value (A)Custom controls, form elements, or ARIA usage may require name, role, state, or value review.
WCAG 2.4.6 Headings and Labels (AA)Headings or labels may not describe topic or purpose clearly enough for review.

Jurisdictional contexts

ADA Title II web/mobile accessibility reviewState or local government web content or mobile apps may be in scope depending on organization context, service context, and manual review.
ADA Title III public accommodation accessibility reviewA business open to the public provides goods, services, or communications through the website.
Section 508 ICT accessibility reviewFederal agency ICT, federal web content, or federal procurement/vendor review may be in scope depending on organization context, procurement context, and manual review.
EN 301 549 / EU accessibility reviewEU public-sector, procurement, Web Accessibility Directive, or European Accessibility Act service context may be in scope depending on organization context, service context, and manual review.
UK public-sector accessibility reviewUK public-sector website or mobile app may be in scope depending on organization context, service context, and manual review.

WCAG references are technical review references. Legal obligations and incorporated versions may vary by jurisdiction and organization type, including WCAG 2.0, 2.1, 2.2, EN 301 549, ADA Title II, Section 508, EU Web Accessibility Directive / European Accessibility Act, and UK public-sector accessibility rules. This finding does not determine legal status or WCAG conformance. Review the retained selector, visible label, accessible name, role, state, value, ARIA relationship, component behavior, page context, organization type, jurisdiction, and manual accessibility findings.

Evidence standard

Strong

Representative automated semantic-labeling evidence includes rule ID, affected selector or element reference, page URL, impact label, and WCAG-oriented reference.
Retained evidence gives enough context to review visible label, accessible name, role, state, value, instructions, grouping, or ARIA relationship.
Evidence indicates the affected element is meaningful user-visible or assistive-technology-relevant content, such as a form field, button, link, landmark, heading, widget, or custom control.
Repeated examples across components, templates, form patterns, or interactive widgets may strengthen confidence when retained.
Strong evidence does not require live assistive-technology testing unless that is explicitly retained; assistive-technology behavior remains a manual review consideration.

Good

Representative automated rule evidence includes rule ID, selector or element reference, page URL, impact label, and WCAG-oriented references.
The retained example is enough for a reviewer to locate the affected element and inspect its label, accessible name, role, or ARIA relationship manually.
The evidence is likely a label/name/role/value issue, but semantic intent, visible-label alignment, grouping, and assistive-technology behavior require manual review.

Audit-only

Contextual signals suggest labeling or ARIA risk, but retained evidence lacks enough detail to identify the affected element, semantic relationship, or user-facing purpose.
Component names, class names, ARIA attributes, or form patterns appear suspicious, but no retained automated accessibility artifact identifies a specific affected element.
The issue may involve dynamic content, shadow DOM, custom widgets, or stateful controls where automated evidence is incomplete.

Insufficient

Selector alone without rule ID, page context, or retained semantic-labeling evidence.
ARIA attribute names or component names without an affected user-visible or assistive-technology-relevant element.
Visual impression, policy text, or code-style preference without retained automated evidence or manual accessibility verification.
Claims about screen-reader behavior, WCAG status, or legal status based only on automated evidence without manual context review.

Evidence levels explain how CertScore treats retained accessibility artifacts. They are not legal conclusions.

Common causes

Visible labels are not programmatically associated with form fields.
Icon-only buttons, links, or controls lack a meaningful accessible name.
ARIA attributes are missing, invalid, duplicated, or disconnected from the intended element.
Custom components do not expose expected name, role, state, or value.
Headings, landmarks, or grouped controls are visually clear but not semantically represented.

Limitations and cautions

This finding is an automated accessibility review signal, not a legal conclusion, certification, or determination of WCAG conformance or non-conformance.
Automated semantic-labeling checks can identify many missing label, accessible-name, ARIA, role, and relationship issues, but they may miss or misread dynamic content, shadow DOM, custom widgets, state changes, localization, hidden text, and assistive-technology behavior.
Automated evidence may not fully determine semantic intent, whether visible and programmatic labels align, whether instructions are sufficient, or whether remediation improves the experience for assistive-technology users.
Manual review is needed to confirm context, user impact, semantic intent, assistive-technology behavior, and remediation quality.
Remediation should be verified across default, focus, error, required, disabled, expanded, collapsed, selected, and responsive states where relevant.
CertScore retains representative evidence for review and may not list every repeated instance across a template or component library.
Findings should be evaluated with implementation context and applicable accessibility requirements before operational or legal reliance.
Automated findings may contain errors and should be reviewed with the retained evidence.
Not detected means not observed in the scan scope; it is not proof of absence.
Findings are runtime evidence and public-surface observations for review, not legal conclusions.

Reference notes

CertScore uses findings, evidence, signals, and observations consistently: signals are raw runtime or page-surface events, evidence is retained support, observations are interpreted evidence context, and findings are promoted review items.
Findings are runtime evidence and public-surface observations for review. Observed signals may surface possible concerns, but review is recommended before operational or legal reliance.
Finding reference content is reviewed periodically and updated when material guidance changes. CertScore monitors guidance families such as EDPB consent and ePrivacy materials, ICO cookie guidance, CNIL tracker recommendations, FTC privacy and dark-pattern materials, and relevant accessibility guidance where applicable.
Automated accessibility evidence can support WCAG-oriented review, but manual review is needed to confirm context, applicable success criterion, user impact, exception status, assistive-technology behavior, keyboard behavior, and remediation quality.
ADA Title II, ADA Title III, Section 508, EN 301 549, and UK public-sector accessibility contexts may be relevant depending on organization type, procurement context, jurisdiction, and manual review.
Prevalence labels use the Tranco top 1-2500 calibration set, an approximately 2,505-scan directional calibration set.

Semantic labeling accessibility issue