Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Link & Button Quality

Action

11 issue(s) across 382 links and 24 buttons

FIX

11 issue(s) across 382 links and 24 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.facebook.com/AROTechnologyUK/; https://www.linkedin.com/company/arotechnology?originalSubdomain=uk; https://x.com/AROTechnologyUK; https://www.youtube.com/@AROTechnology

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://aro.tech/insights/case-study/ai-powered-contact-centre-solution/ ("Read More"); https://aro.tech/insights/case-study/knowsley-metropolitan-borough-council-it… ("Read more"); https://aro.tech/insights/case-study/playtronic-games-secures-microsoft-365-d… ("Read more")

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.js-close-menu (#134 on page); button.js-close-menu (#379 on page); button.js-close-menu (#406 on page); button.hamburger (#427 on page)

375 link(s) with descriptive text

382 links

4 empty

3 generic text

0 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://aro.tech/insights/case-study/ai-…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Ai Powered Contact Centre Solution
https://aro.tech/insights/case-study/kno…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Knowsley Metropolitan Borough Council It Transformation
https://aro.tech/insights/case-study/pla…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Playtronic Games Secures Microsoft 365 Data With Barracudas Total Email Protection
https://www.facebook.com/AROTechnologyUK…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/arotech…	(empty)	empty	Add link text or aria-label
https://x.com/AROTechnologyUK	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@AROTechnology	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

395 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.facebook.com/AROTechnologyUK/; https://www.linkedin.com/company/arotechnology?originalSubdomain=uk; https://x.com/AROTechnologyUK; https://www.youtube.com/@AROTechnology

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://aro.tech/insights/case-study/ai-powered-contact-centre-solution/ ("Read More"); https://aro.tech/insights/case-study/knowsley-metropolitan-borough-council-it… ("Read more"); https://aro.tech/insights/case-study/playtronic-games-secures-microsoft-365-d… ("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

Icon-only buttons need an aria-label so screen readers can announce them.

button.js-close-menu (#134 on page); button.js-close-menu (#379 on page); button.js-close-menu (#406 on page); button.hamburger (#427 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Heading Hierarchy

36 headings, 2 skip(s)

REVIEW

36 headings, 2 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Cloud & Infrastructure
H3 Networking and Secure Connectivity
H3 Cyber Security
H3 Data and AI Transformation
H3 Digital Transformation and Modern Work
H3 Managed Services
H3 Hybrid Cloud Services
H3 Unified Communications
H3 Business Mobiles
H3 Sustainability
H5 Microsoft Ignite 2025: What’s Big and What It Means for Your Business skipped
H3 Resources
H5 Delivering Cost Savings and Service Continuity for Tuntum Housing Association with ARO’s Mobile Solution skipped
H3 About
H3 Cloud & Infrastructure
H3 Networking and Secure Connectivity
H3 Cyber Security
H3 Data and AI Transformation
H3 Digital Transformation and Modern Work
H3 Managed Services
H3 Hybrid Cloud Services
H3 Unified Communications
H3 Business Mobiles
H3 Sustainability
H1 Technology Only Better.
H2 Every organisation can access the same IT, but not the same IT performance.
H3 Our Solutions and Services
H3 Our Partner Accreditations
H3 Our Impact
H2 Your Business. Powered by Smarter IT.
H3 Managed support. Only Better.
H4 Latest Insights
H4 Making Sense of NAC vs SD-WAN vs SASE: Designing Network Security Around Business Outcomes
H4 Hesitation Is a Vulnerability: A 2026 Cyber Threat Briefing for Today’s Security Teams
H4 Rethinking Microsoft 365: Cost Control, Security and AI Readiness
H3 Insights. Only better.

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Tabindex Anti-Patterns

3 positive, 0 -1-on-focusable

REVIEW

3 positive, 0 -1-on-focusable

Positive tabindex on <input id="input_1_1">: tabindex=12

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.

Positive tabindex on <input id="input_1_2_1">: tabindex=13

Positive tabindex on <button id="gform_submit_button_1">: tabindex=14

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - ARO ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 83/100 — 5 failing, 25 passed

REVIEW

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Customer satisfaction is an important KPI for our business and these statistics… `div.statistics-hero__content > div.statistics-hero__content-inner > div.statistics-hero__description > p`
Case studies `div.statistics-hero__wrapper > div.statistics-hero__content > div.statistics-hero__content-inner > a.btn-link`
Customer Satisfaction `div.statistics-hero__stats-wrapper > div.statistics-hero__stats > div.statistics-hero__stat > span.statistics-hero__stat-desc`
Incident Resolution SLA `div.statistics-hero__stats-wrapper > div.statistics-hero__stats > div.statistics-hero__stat > span.statistics-hero__stat-desc`
Incident Response SLA `div.statistics-hero__stats-wrapper > div.statistics-hero__stats > div.statistics-hero__stat > span.statistics-hero__stat-desc`
Resolved within 5 days `div.statistics-hero__stats-wrapper > div.statistics-hero__stats > div.statistics-hero__stat > span.statistics-hero__stat-desc`

These are opportunities to improve the legibility of your content.

Names and labels

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
div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a `div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a`
div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a `div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a`
div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a `div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a`
div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a `div.site-footer__contact-info > ul.site-footer__socials > li.site-footer__social > a`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Solutions Cloud and Infrastructure Networking and Secure Connectivity Cyber Sec… `footer.site-footer > div.container > nav.footer-nav > li.nav-menu-item`
Locations Aberdeen IT Support Cardiff IT Support Chester IT Support Glasgow IT … `footer.site-footer > div.container > nav.footer-nav > li.nav-menu-item`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#gform_fields_1 > div#field_1_1 > div.ginput_container > input#input_1_1 `div#gform_fields_1 > div#field_1_1 > div.ginput_container > input#input_1_1`
Submit > `div.gform-body > div#gform_fields_1 > div#field_submit > button#gform_submit_button_1`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`button`, `link`, and `menuitem` elements have accessible names

●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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○`<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

○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.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○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 Quality

All 36 heading(s) have substantive, well-formed text

PASS

All 36 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 46 images OK

PASS

All 46 images OK

27 decorative image(s) correctly marked

19 image(s) with good alt text

46 images 19 good alt text 27 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#input_1_5	text	LinkedIn	for/id
#input_1_1	email	Email	for/id
#input_1_2_1	checkbox	I have read and understood the Privacy Page *	for/id

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-GB"

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 119 visible text node(s) render at >= 12 CSS pixels

PASS

All 119 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Technology	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Every organisation c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your Business. Power…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cloud & Infrastructu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Networking and Secur…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cyber Security	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Data and AI Transfor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Digital Transformati…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Managed Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hybrid Cloud Service…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Unified Communicatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Business Mobiles	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sustainability	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cloud & Infrastructu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Networking and Secur…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cyber Security	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Data and AI Transfor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Digital Transformati…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Managed Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hybrid Cloud Service…	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.