https://norriq.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
71
GRADE
C
FIX
10
REVIEW
3
PASS
11
INFO
0
Checks
2411 PASS 3 REVIEW 10 FIX
DLandmark StructureAction6 landmarksFIX
Landmark Structure
Action6 landmarks
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Why this matters
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Why this matters
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Why this matters
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
DLink & Button QualityAction24 issue(s) across 89 links and 23 buttonsFIX
Link & Button Quality
Action24 issue(s) across 89 links and 23 buttons
24 issue(s) across 89 links and 23 buttons
Critical::
22 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: a (#967 on page); a (#987 on page); a (#1007 on page); a (#1027 on page); a (#1047 on page); a (#1067 on page); https://norriq.com/nfs; /competences/enterprise-resource-planning; /competences/product-information-management; /competences/ecommerce-web-development (+12 more)
Warning::
2 link(s) with generic text
Generic link text like 'click here' doesn't describe the destination.
Got: https://tools.google.com/dlpage/gaoptout ("here"); /cases ("Read more")
Warning::
49 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://cookieinformation.com/cookie-and-privacy-policy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://www.cloudflare.com/privacypolicy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://snapengage.com/privacy-policy; https://snapengage.com/privacy-policy (+39 more)
Info::
16 link(s) with descriptive text
89 links
22 empty
2 generic text
49 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://cookieinformation.com/cookie-and… | https://cookieinformation.com/… | new tab | Add '(opens in new tab)' to text |
| https://cookieinformation.com/cookie-and… | https://cookieinformation.com/… | new tab | Add '(opens in new tab)' to text |
| https://www.cloudflare.com/privacypolicy… | https://www.cloudflare.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://cookieinformation.com/cookie-and… | https://cookieinformation.com/… | new tab | Add '(opens in new tab)' to text |
| https://www.cloudflare.com/privacypolicy… | https://www.cloudflare.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://www.cloudflare.com/privacypolicy… | https://www.cloudflare.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://www.cloudflare.com/privacypolicy… | https://www.cloudflare.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://www.cloudflare.com/privacypolicy… | https://www.cloudflare.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://snapengage.com/privacy-policy | https://snapengage.com/privacy… | new tab | Add '(opens in new tab)' to text |
| https://snapengage.com/privacy-policy | https://snapengage.com/privacy… | new tab | Add '(opens in new tab)' to text |
| https://snapengage.com/privacy-policy | https://snapengage.com/privacy… | new tab | Add '(opens in new tab)' to text |
| https://privacy.microsoft.com/en-us/priv… | https://privacy.microsoft.com/… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://optinmonster.com/privacy | https://optinmonster.com/priva… | new tab | Add '(opens in new tab)' to text |
| https://privacy.microsoft.com/en-us/priv… | https://privacy.microsoft.com/… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://optinmonster.com/privacy | https://optinmonster.com/priva… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://www.leadfamly.com/about/privacy-… | https://www.leadfamly.com/abou… | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/legal/privacy-p… | https://www.linkedin.com/legal… | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/legal/privacy-p… | https://www.linkedin.com/legal… | new tab | Add '(opens in new tab)' to text |
| https://www.leadfeeder.com/privacy/ | https://www.leadfeeder.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://www.leadfeeder.com/privacy/ | https://www.leadfeeder.com/pri… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://www.leadfamly.com/about/privacy-… | https://www.leadfamly.com/abou… | new tab | Add '(opens in new tab)' to text |
| https://policies.google.com/technologies… | https://policies.google.com/te… | new tab | Add '(opens in new tab)' to text |
| https://clickdimensions.com/about/privac… | https://clickdimensions.com/ab… | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/legal/privacy-p… | https://www.linkedin.com/legal… | new tab | Add '(opens in new tab)' to text |
| https://clickdimensions.com/about/privac… | https://clickdimensions.com/ab… | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/privacy/explana… | https://www.facebook.com/priva… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy | https://segment.com/docs/legal… | new tab | Add '(opens in new tab)' to text |
| https://www.loom.com/privacy-policy | https://www.loom.com/privacy-p… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy | https://segment.com/docs/legal… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy | https://segment.com/docs/legal… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy | https://segment.com/docs/legal… | new tab | Add '(opens in new tab)' to text |
| https://www.loom.com/privacy-policy | https://www.loom.com/privacy-p… | new tab | Add '(opens in new tab)' to text |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| https://tools.google.com/dlpage/gaoptout | here | generic text | Replace with descriptive text |
Before: here Suggested: Gaoptout | |||
| https://support.microsoft.com/en-us/help… | Internet Explorer | new tab | Add '(opens in new tab)' to text |
| https://support.microsoft.com/en-us/help… | Microsoft Edge | new tab | Add '(opens in new tab)' to text |
| https://support.mozilla.org/en-US/kb/del… | Mozilla Firefox | new tab | Add '(opens in new tab)' to text |
| https://support.google.com/chrome/answer… | Google Chrome | new tab | Add '(opens in new tab)' to text |
| https://www.opera.com/help/tutorials/sec… | Opera | new tab | Add '(opens in new tab)' to text |
| https://support.apple.com/en-us/HT201265 | Safari | new tab | Add '(opens in new tab)' to text |
| https://www.macromedia.com/support/docum… | Flash cookies | new tab | Add '(opens in new tab)' to text |
| https://support.apple.com/en-us/HT1677 | Apple | new tab | Add '(opens in new tab)' to text |
| https://timeread.hubpages.com/hub/How-to… | Android | new tab | Add '(opens in new tab)' to text |
| https://support.microsoft.com/en-us/help… | Windows 7 | new tab | Add '(opens in new tab)' to text |
| https://cookieinformation.com | Cookie Information | new tab | Add '(opens in new tab)' to text |
| https://norriq.com/nfs | (empty) | empty | Add link text or aria-label |
| /competences/enterprise-resource-plannin… | (empty) | empty | Add link text or aria-label |
| /competences/product-information-managem… | (empty) | empty | Add link text or aria-label |
| /competences/ecommerce-web-development | (empty) | empty | Add link text or aria-label |
| /competences/customer-engagement-industr… | (empty) | empty | Add link text or aria-label |
| /competences/bi-analytics | (empty) | empty | Add link text or aria-label |
| /competences/ai-automation | (empty) | empty | Add link text or aria-label |
| /competences/apps-accelerators | (empty) | empty | Add link text or aria-label |
| /cases/business-intelligence-as-a-cataly… | (empty) | empty | Add link text or aria-label |
| /cases/norriq-makes-elindus-financial-de… | (empty) | empty | Add link text or aria-label |
| /cases/strong-platform-prepares-geia-foo… | (empty) | empty | Add link text or aria-label |
| /cases/publicly-listed-pharmaceutical-co… | (empty) | empty | Add link text or aria-label |
| /cases | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Cases | |||
| /articles/danish-german-collaboration-ch… | (empty) | empty | Add link text or aria-label |
| /articles/two-norriq-clients-honored-at-… | (empty) | empty | Add link text or aria-label |
| /articles/norriq-financial-services-aims… | (empty) | empty | Add link text or aria-label |
| /articles/norriq-concludes-2023-with-rec… | (empty) | empty | Add link text or aria-label |
39 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
a (#967 on page); a (#987 on page); a (#1007 on page); a (#1027 on page); a (#1047 on page); a (#1067 on page); https://norriq.com/nfs; /competences/enterprise-resource-planning; /competences/product-information-management; /competences/ecommerce-web-development (+12 more)
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
https://tools.google.com/dlpage/gaoptout ("here"); /cases ("Read more")
Why this matters
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://cookieinformation.com/cookie-and-privacy-policy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://www.cloudflare.com/privacypolicy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://www.cloudflare.com/privacypolicy/; https://snapengage.com/privacy-policy; https://snapengage.com/privacy-policy (+39 more)
Why this matters
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
DMobile Keyboard & AutofillAction1/1 eligible field(s) missing autocomplete or inputmodeFIX
Mobile Keyboard & Autofill
Action1/1 eligible field(s) missing autocomplete or inputmode
1/1 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="text" name="email" id="email">
DTabindex Anti-PatternsAction1 positive, 44 -1-on-focusableFIX
Tabindex Anti-Patterns
Action1 positive, 44 -1-on-focusable
1 positive, 44 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Warning::
Positive tabindex on <button id="Coi-Renew">: tabindex=1
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
D404 Error PageActionHTTP 404, custom pageFIX
404 Error Page
ActionHTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
DFavicon & BrandingAction3 icon(s) detectedFIX
Favicon & Branding
Action3 icon(s) detected
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
BHeading Hierarchy24 headings, 2 skip(s)REVIEW
Heading Hierarchy
24 headings, 2 skip(s)
24 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- H2 You control your data
- H2 Cookie Policy
- H2 What is a cookie?
- H2 How/why the homepage uses cookies
- H2 How long are cookies saved?
- H2 This is how you can reject or delete your cookies
- H2 Deleting cookies
- H2 Do you have any questions?
- H1 Digitize and grow your business
- H2 Embrace the challenges and the opportunities of the future. We'll make it simple for you.
- H2 NORRIQ aims to revolutionize financial consulting
- H2 We are NORRIQ
- H4 Industry knowledge. Business understanding. Technology insight. skipped
- H2 Meet our happy customers
- H2 News from NORRIQ
- H3 Danish-German collaboration challenges habits in Pharma & Medico
- H3 Two NORRIQ clients honored at the 2024 E-Commerce Awards
- H3 NORRIQ Financial Services aims to revolutionize financial consulting amidst industry shifts
- H3 NORRIQ concludes 2023 with record results
- H2 Want to know more?
- H4 Please contact us skipped
- H4 Why complicate things?
- H4 Get in touch
- H4 Legal
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Color Contrast (Screenshot)
Action20 text elements analyzed, 20 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
0 pass 20 fail WCAG AA
h1 Digitize and grow your business
1.23:1#000000
on#201B17
needs 3.0:1 (large text)32px · bottom of viewport
h2 You control your data
1.15:1#000000
on#11151A
needs 3.0:1 (large text)24px · top of page (header area)
h2 Cookie Policy
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 What is a cookie?
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 How/why the homepage uses cookies
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 How long are cookies saved?
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 This is how you can reject or delete you…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 Deleting cookies
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 Do you have any questions?
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 Embrace the challenges and the opportuni…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 NORRIQ aims to revolutionize financial c…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 We are NORRIQ
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 Meet our happy customers
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 News from NORRIQ
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h2 Want to know more?
1.23:1#000000
on#201B17
needs 3.0:1 (large text)24px · bottom of viewport
h3 Danish-German collaboration challenges h…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)19px · bottom of viewport
h3 Two NORRIQ clients honored at the 2024 E…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)19px · bottom of viewport
h3 NORRIQ Financial Services aims to revolu…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)19px · bottom of viewport
h3 NORRIQ concludes 2023 with record result…
1.23:1#000000
on#201B17
needs 3.0:1 (large text)19px · bottom of viewport
title We are the NORRIQ Group | Welcome
1.11:1#000000
on#0C1116
needs 4.5:1 (normal text)16px · top of page (header area)
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Digitize and grow yo… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 You control your dat… | 1.15:1 | 3.0:1 | #000000 | #11151A | Fail |
| h2 Cookie Policy | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 What is a cookie? | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 How/why the homepage… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 How long are cookies… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 This is how you can … | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 Deleting cookies | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 Do you have any ques… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 Embrace the challeng… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 NORRIQ aims to revol… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 We are NORRIQ | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 Meet our happy custo… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 News from NORRIQ | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h2 Want to know more? | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h3 Danish-German collab… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h3 Two NORRIQ clients h… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h3 NORRIQ Financial Ser… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| h3 NORRIQ concludes 202… | 1.23:1 | 3.0:1 | #000000 | #201B17 | Fail |
| title We are the NORRIQ Gr… | 1.11:1 | 4.5:1 | #000000 | #0C1116 | Fail |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
BLighthouse Accessibility AuditsScore 84/100 — 5 failing, 26 passedREVIEW
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 26 passed
84
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.lg:flex > div.flex > div.relative > div#headlessui-popover-button-v-0-2 div.lg:flex > div.flex > div.relative > div#headlessui-popover-button-v-0-2 |
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
toggle-for-Strictly necessary div.coi-banner-consent-field > div#switch-cookie_cat_necessary > div.coi-checkboxes > div.checkbox-toggle |
toggle-for-Functional div.coi-banner-consent-field > div#switch-cookie_cat_functional > div.coi-checkboxes > div.checkbox-toggle |
toggle-for-Statistical div.coi-banner-consent-field > div#switch-cookie_cat_statistic > div.coi-checkboxes > div.checkbox-toggle |
toggle-for-Marketing div.coi-banner-consent-field > div#switch-cookie_cat_marketing > div.coi-checkboxes > div.checkbox-toggle |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.flex > div.relative > div#headlessui-popover-button-v-0-2 > button.focus:outline-none div.flex > div.relative > div#headlessui-popover-button-v-0-2 > button.focus:outline-none |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link |
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static div.swiper-wrapper > div.swiper-slide > div.case-item > a.static |
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static div.swiper-wrapper > div.swiper-slide > div.case-item > a.static |
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static div.swiper-wrapper > div.swiper-slide > div.case-item > a.static |
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static div.swiper-wrapper > div.swiper-slide > div.case-item > a.static |
div.swiper-wrapper > div.swiper-slide > article.relative > a.static div.swiper-wrapper > div.swiper-slide > article.relative > a.static |
div.swiper-wrapper > div.swiper-slide > article.relative > a.static div.swiper-wrapper > div.swiper-slide > article.relative > a.static |
div.swiper-wrapper > div.swiper-slide > article.relative > a.static div.swiper-wrapper > div.swiper-slide > article.relative > a.static |
div.swiper-wrapper > div.swiper-slide > article.relative > a.static div.swiper-wrapper > div.swiper-slide > article.relative > a.static |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Industry knowledge. Business understanding. Technology insight. div.flex > div > div.text-editor > h4 |
Please contact us div.lg:max-w-[475px] > div > div.text-editor > h4 |
These are opportunities to improve keyboard navigation in your application.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+Heading Text QualityAll 24 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 24 heading(s) have substantive, well-formed text
All 24 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
AAlt Text Quality2 of 18 images have issuesPASS
Alt Text Quality
2 of 18 images have issues
2 of 18 images have issues
Warning::
2 image(s) with generic alt text
Info::
16 image(s) with good alt text
18 images 16 good alt text 2 generic
| Issue | Count |
|---|---|
| generic | 2 image(s) |
A+Form AccessibilityAll 11 controls labeledPASS
Form Accessibility
All 11 controls labeled
All 11 controls labeled
Info::
11 control(s) properly labeled
11 controls
11 labeled
0 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #cookie_cat_necessary | checkbox | Strictly necessary | aria-label |
| #cookie_cat_functional | checkbox | Functional | aria-label |
| #cookie_cat_statistic | checkbox | Statistical | aria-label |
| #cookie_cat_marketing | checkbox | Marketing | aria-label |
| #firstname | text | First name* | for/id |
| #lastname | text | Last name* | for/id |
| #field[37] | text | Company* | for/id |
| #field[1] | text | Job title* | for/id |
| #phone | text | Phone* | for/id |
| text | Work email* | for/id | |
| #field[39] | textarea | Tell us, how we can help you? | for/id |
AForm Input Types2 input(s) using type=text where a specific type would helpPASS
Form Input Types
2 input(s) using type=text where a specific type would help
2 input(s) using type=text where a specific type would help
Info::
Input "phone" should use type="tel" (currently type="text")
Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+Form Input Quality11 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
11 form control(s) checked, no input-semantic issues
11 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Document LanguageLang attribute set to "en-US"PASS
Document Language
Lang attribute set to "en-US"
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+Iframe AccessibilityAll 1 iframe(s) have descriptive titlesPASS
Iframe Accessibility
All 1 iframe(s) have descriptive titles
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+Mobile-Readable Font SizesAll 17 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 17 visible text node(s) render at >= 12 CSS pixels
All 17 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.