vg.no Accessibility Report

Accessibility audit of vg.no — scanned on Feb 21, 2026

Technology
0 /100
D Poor

5 issues found across 3 categories

2 Critical 2 Major 1 Minor

WCAG Compliance Overview

Perceivable 1 issues
Operable 1 issues
Understandable 0 issues
Robust 3 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
2 element(s) affected
  • <a href="(no href)">
  • <a href="https://www.vg.no">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
5 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
1 element(s) affected
  • id="Annonse_-_sort_svg__Layer_2"
How to fix

Make each id attribute value unique within the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
24 element(s) affected
  • <svg role="graphics-symbol">
  • <vg-dynamic-widget role="section">
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Incorrect list structure

Minor

List items must be contained within <ul>, <ol>, or <dl> elements.

WCAG 1.3.1
8 element(s) affected
  • <dt> outside <dl>
  • <dd> outside <dl>
How to fix

Ensure <li> elements are direct children of <ul> or <ol>.

Top Priority Fixes

Here are the most impactful changes vg.no should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  3. #3
    Invalid ARIA attributes Major

    Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Frequently Asked Questions

Is vg.no accessible?

vg.no scored 51/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is vg.no WCAG compliant?

Our scan found 5 accessibility issues on vg.no. Full WCAG compliance requires addressing all critical and major issues identified above.

Is vg.no EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see vg.no's compliance status.

What accessibility issues does vg.no have?

See the full issue list above with severity levels, affected elements, and recommended fixes for vg.no.

Scan Your Own Website

Get a free accessibility report for your website in seconds.