https://github.com/abidullahafridi/Automation-Engine

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 8 REVIEW 1 FIX

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 ✗

Heading Hierarchy

22 headings

REVIEW

22 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Navigation Menu
H2 Repository navigation
H2 About
H3 Resources
H3 Stars
H3 Watchers
H3 Forks
H2 Latest commit
H2 History
H2 Folders and files
H2 Repository files navigation
H2 Local MongoDB Replica Set
H2 About
H3 Resources
H3 Stars
H3 Watchers
H3 Forks
H2 Releases
H2 Contributors1 (1)
H2 Languages
H2 Footer
H3 Footer navigation

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

Action

7 issue(s) across 206 links and 25 buttons

REVIEW

7 issue(s) across 206 links and 25 buttons

1 link(s) with no accessible text

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

Got: /abidullahafridi/Automation-Engine

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://docs.github.com; https://github.blog; https://github.blog/changelog; https://skills.github.com; https://docs.github.com; https://support.github.com; https://securitylab.github.com; https://maintainers.github.com; https://stars.github.com; https://archiveprogram.github.com

6 button(s) with no accessible text

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

Got: button.Primer_Brand__Button-module__Button___scH9Z (#265 on page); button.Primer_Brand__Button-module__Button___scH9Z (#683 on page); button#icon-button-7736d428-9cf8-414e-8f39-f5f33ddb8f9c; button#_R_4idahlik5_; button[data-testid="checks-status-badge-icon"]; button[data-testid="latest-commit-details-toggle"]

195 link(s) with descriptive text

206 links

1 empty

0 generic text

10 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.github.com	Documentation	new tab	Add '(opens in new tab)' to text
https://github.blog	Blog	new tab	Add '(opens in new tab)' to text
https://github.blog/changelog	Changelog	new tab	Add '(opens in new tab)' to text
https://skills.github.com	GitHub Skills	new tab	Add '(opens in new tab)' to text
https://docs.github.com	Documentation	new tab	Add '(opens in new tab)' to text
https://support.github.com	Customer support	new tab	Add '(opens in new tab)' to text
https://securitylab.github.com	Security Lab	new tab	Add '(opens in new tab)' to text
https://maintainers.github.com	Maintainer Community	new tab	Add '(opens in new tab)' to text
https://stars.github.com	GitHub Stars	new tab	Add '(opens in new tab)' to text
https://archiveprogram.github.com	Archive Program	new tab	Add '(opens in new tab)' to text
/abidullahafridi/Automation-Engine	(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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

214 links and buttons have descriptive text

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

/abidullahafridi/Automation-Engine

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

Add '(opens in new tab)' to link text or aria-label.

https://docs.github.com; https://github.blog; https://github.blog/changelog; https://skills.github.com; https://docs.github.com; https://support.github.com; https://securitylab.github.com; https://maintainers.github.com; https://stars.github.com; https://archiveprogram.github.com

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

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

button.Primer_Brand__Button-module__Button___scH9Z (#265 on page); button.Primer_Brand__Button-module__Button___scH9Z (#683 on page); button#icon-button-7736d428-9cf8-414e-8f39-f5f33ddb8f9c; button#_R_4idahlik5_; button[data-testid="checks-status-badge-icon"]; button[data-testid="latest-commit-details-toggle"]

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

Tap Target Adequacy

Action

9 tap target(s) too small or too close together

REVIEW

9 tap target(s) too small or too close together

9 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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 · GitHub · GitHub ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

13 icon(s) detected

REVIEW

13 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1e2327

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta light dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title GitHub - abidullahafridi/Automation-Engi…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Navigation Menu	19.73:1	3.0:1	#000000	#F6F8FA	Pass
h2 Repository navigatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest commit	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 History	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Folders and files	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Repository files nav…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Local MongoDB Replic…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Footer navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title GitHub - abidullahaf…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	1.00:1	4.5:1	#000000	#000000	Fail
span Sign in	19.73:1	4.5:1	#000000	#F6F8FA	Pass
div Appearance settings	19.73:1	4.5:1	#000000	#F6F8FA	Pass
button Platform	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span AI CODE CREATION	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span GitHub Copilot	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Write better code wi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span GitHub Copilot app	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Direct agents from i…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span MCP Registry	21.00:1	4.5: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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #start-of-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	Go to file	aria-label

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

8 explicit tabindex attribute(s) checked, no anti-patterns

PASS

8 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

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

PASS

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

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

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: GitHub

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name GitHub ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name GitHub Display Mode standalone Icons 11 icon(s)

PWA Depth

2 PWA signal(s) surfaced

PASS

2 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

iOS smart-banner opt-in present (`apple-itunes-app`)

The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 29 passed

PASS

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Privacy `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Security `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Status `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Community `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Docs `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Contact `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Manage cookies `ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary`
Do not share my personal information `ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Notifications `div > ul.list-style-none > li > a.prc-Button-ButtonBase-9n-Xk`
Fork0 (0) `div > ul.list-style-none > li > a.prc-Button-ButtonBase-9n-Xk`

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA `progressbar` elements have accessible names

●Elements use only permitted ARIA attributes

●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

●Links have a discernible name

●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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

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

○Form elements have associated labels

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

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

○Identical links have the same purpose.

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