www.safetotalk.nz

Ministry of Social Development

June 2026 scan

Rank
#23 of 489 websites, #1 = worst
Avg. issues
11.70 issues/page
Issues found
515
Pages scanned
22 22 with issues
Issue types
6

Trend

Avg. issues per page for this website, by quarter.

Supporting figures

How this quarter's 515 issues divide by severity and by viewport. Every page is scanned twice, once at each viewport.

Critical issues
130
Serious issues
385
Moderate issues
0
Minor issues
0
Pages scanned (mobile)
22
Pages scanned (desktop)
22
Mobile issues
258
Desktop issues
257

Top 10 repeated issues

Ranked by how many issues each causes, out of 13 elements at fault.

Fixing these would resolve 430 of this website's 515 issues — a 83% reduction.

1. color-contrast

WCAG Success Criterion 1.4.3 Contrast (Minimum) (Level AA)

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

<a class="btn btn-quickexit js-quickexit stagger" href="https://www.google.co.nz/search?q=todays+wea…

44 issues on 22 pages · Seen on Sexual Harm. Do you want to talk? | Safe to talk

2. color-contrast

WCAG Success Criterion 1.4.3 Contrast (Minimum) (Level AA)

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

<a class="btn btn-your-digital-safety stagger" href="/your-digital-safety" title="/your-digital-safe…

44 issues on 22 pages · Seen on Sexual Harm. Do you want to talk? | Safe to talk

3. color-contrast

WCAG Success Criterion 1.4.3 Contrast (Minimum) (Level AA)

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

<a class="btn full-width jsHealthPointSearch" href="javascript:void(0)" title="Search">Search</a>

44 issues on 22 pages · Seen on Sexual Harm. Do you want to talk? | Safe to talk

4. select-name

WCAG Success Criterion 4.1.2 Name, Role, Value (Level A)

Ensure select element has an accessible name

<select name="App\SV\Models\Region" id="App_SV_Models_Region" class="dropdown jsRegion select-wrappe…

44 issues on 22 pages · Seen on Sexual Harm. Do you want to talk? | Safe to talk

5. select-name

WCAG Success Criterion 4.1.2 Name, Role, Value (Level A)

Ensure select element has an accessible name

<select name="App\SV\Models\Service" id="App_SV_Models_Service" class="dropdown jsService select-wra…

44 issues on 22 pages · Seen on Sexual Harm. Do you want to talk? | Safe to talk

6. aria-input-field-name

WCAG Success Criterion 4.1.2 Name, Role, Value (Level A)

Ensure every ARIA input field has an accessible name

<ul class="optionset" id="PageFeedbackForm_getPageFeedbackForm_Rating" aria-required="true" role="li…

42 issues on 21 pages · Seen on About Us | Safe to talk

7. aria-required-children

WCAG Success Criterion 1.3.1 Info and Relationships (Level A)

Ensure elements with an ARIA role that require child roles contain them

<ul class="optionset" id="PageFeedbackForm_getPageFeedbackForm_Rating" aria-required="true" role="li…

42 issues on 21 pages · Seen on About Us | Safe to talk

8. listitem

WCAG Success Criterion 1.3.1 Info and Relationships (Level A)

Ensure <li> elements are used semantically

<li class="even val2 pagefeedback"> <input id="PageFeedbackForm_getPageFeedbackForm_Rating_2" cla…

42 issues on 21 pages · Seen on About Us | Safe to talk

9. listitem

WCAG Success Criterion 1.3.1 Info and Relationships (Level A)

Ensure <li> elements are used semantically

<li class="even val4 pagefeedback"> <input id="PageFeedbackForm_getPageFeedbackForm_Rating_4" cla…

42 issues on 21 pages · Seen on About Us | Safe to talk

10. listitem

WCAG Success Criterion 1.3.1 Info and Relationships (Level A)

Ensure <li> elements are used semantically

<li class="odd val1 pagefeedback"> <input id="PageFeedbackForm_getPageFeedbackForm_Rating_1" clas…

42 issues on 21 pages · Seen on About Us | Safe to talk