Skip to content
BranchesTags

Repository files navigation

System Check

A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.

Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.

What it tests

StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed

Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.

Requirements

  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input

Getting started

npm install
npm run dev # http://localhost:5173

Production build:

npm run build # outputs to dist/
npm run preview # serve the built bundle locally

dist/ is fully static — host it on any object store, CDN, or static-site service.

Deploying

Heroku (Heroku Pipelines)

This repo is set up to deploy as a Heroku Node.js app:

  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.

Create the app and push:

heroku create system-check --stack heroku-24
git push heroku main
heroku open

For a pipeline:

heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production

Promote staging → production via the dashboard or heroku pipelines:promote.

Anywhere else

Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.

Network thresholds

The network stage's verdict combines latency and bandwidth:

  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps

Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.

Project layout

index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.

License

MIT — see LICENSE.

About

Web application to do basic Chromebook ELI device checking

Resources

Readme
MIT license

Contributing

Contributing
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
GitHub - innovationsforlearning/checks: Web application to do basic Chromebook ELI device checking · GitHub
Skip to content
BranchesTags
Repository files navigation
System Check
A browser-based device readiness check. Walks a user through a sequence of short tests to verify their hardware and connection are good enough for video calls and interactive learning.
Built as a Vite static app — vanilla JavaScript, no framework, deployable anywhere that serves static files.
What it tests
StageChecks
Browser & deviceUser agent, OS, viewport, cookies, local storage
NetworkOnline status, connection type, latency to the app and the public internet, download/upload bandwidth (via Cloudflare's speed.cloudflare.com endpoints)
Video calling (WebRTC)WebRTC support, STUN reachability, ICE candidate types, public IP
WebcamLive preview — user confirms they can see themselves
MicrophoneLive level meter with auto voice detection
SpeakersPlays a tone; user confirms they heard it
TouchscreenTap-the-corners + drag-to-target (skipped on non-touch devices)
Touchscreen (drag)Horizontal drag gesture (skipped on non-touch devices)
Trackpad / MouseClick-the-corners + drag-to-target
KeyboardOn-screen keyboard layout that lights up each key as it's pressed
Each stage produces a pass / warn / fail / skip result, and the final screen summarises the run.
Requirements
  • Node.js 18 or newer
  • A modern browser with permissions for camera, mic, and (if testing) touch input
Getting started
npm install
npm run dev # http://localhost:5173
Production build:
npm run build # outputs to dist/
npm run preview # serve the built bundle locally
dist/ is fully static — host it on any object store, CDN, or static-site service.
Deploying
Heroku (Heroku Pipelines)
This repo is set up to deploy as a Heroku Node.js app:
  • package.json declares engines.node ≥ 18, a heroku-postbuild step that runs vite build, and a start script that serves dist/ via serve on $PORT.
  • Procfile runs npm start.
  • app.json declares the app for Pipelines / Review Apps.
Create the app and push:
heroku create system-check --stack heroku-24
git push heroku main
heroku open
For a pipeline:
heroku pipelines:create system-check -a system-check-staging
heroku pipelines:add system-check -a system-check-production -s production
Promote staging → production via the dashboard or heroku pipelines:promote.
Anywhere else
Run npm run build and upload dist/ to your host of choice (S3, Netlify, Cloudflare Pages, GitHub Pages, nginx, etc.). There are no runtime dependencies.
Network thresholds
The network stage's verdict combines latency and bandwidth:
  • Healthy — latency < 600 ms to both targets, download ≥ 5 Mbps, upload ≥ 3 Mbps
  • Warn — any of: latency > 600 ms, download < 5 Mbps, or upload < 3 Mbps
  • Fail — offline, no network response, app latency > 1500 ms, or download < 1.5 Mbps
Bandwidth uses Cloudflare's public speed-test endpoints (__down, __up) with a 12-second cap per direction, so a stuck connection still produces a result rather than hanging the stage.
Project layout
index.html # static shell — no app logic
src/
main.js # bootstrap + stage runner
results.js # final results screen
lib/ # cleanup bag + small helpers
ui/ # screens, progress, footer, diag, overlay
stages/ # one file per test
styles/ # CSS, split by concern
Procfile # Heroku web process
app.json # Heroku app manifest
vite.config.js # Vite config

See CONTRIBUTING.md for details on the stage contract and how to add a new test.
License
MIT — see LICENSE.
About
Web application to do basic Chromebook ELI device checking 
Resources
Readme
MIT license
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages