Project: an accessible service enquiry page
Open HTML exercise ↗Expected visual result
A structured enquiry page with a labelled message field
ACADEMY · DEVICE CHECK
Open combined testing dashboard ↓
Complete programming, AI & IT test guides ↓
Check real exercises, saved code and compiler waiting in Chrome on Android or Safari on iPhone.
ONE VIEW · ALL LEARNING PATHS
70 courses · 350 lessons across computer skills, programming, AI and IT technical. Read your saved detailed checklists in one place. Recorded progress includes Pass, Fail and Blocked; it does not mean every check passed.
Results stay in the browser where you entered them. Selecting iPhone here does not fetch results from your physical iPhone. Open this dashboard on each device to see its local records. Older general and course-level summaries are preserved but excluded from detailed totals to avoid counting the same test twice.
Each computer course has 18 lesson checks and 3 practical checks. Programming, AI and IT courses have 7 checks per lesson. Each platform has 2,450 detailed checks. Missing records are Not tested. The dashboard reads existing records; use a course link to edit them.
Record the restore test you actually performed. These are manual observations, not an automatic check of a file. Saving here does not change course results. Export a new combined JSON backup afterwards to include this history; older backups cannot contain records saved later.
Click Save verification record to keep this form. Unsaved fields are not stored.
History is saved in this browser and included in all platform export scopes. New imports keep existing records; any differing version is retained in the conflict archive.
Export a private JSON backup on your Android phone and iPhone, transfer the files yourself, then preview and merge them here. This does not use cloud sync. Files include notes and device details; keep them private.
If a download is blocked, copy the exported JSON into a .json file. Only checklist records are read; account credentials, provider settings and saved learning code are outside this backup. Anything you typed in notes is included.
Finish edits in other checklist tabs before merging. Empty values never clear current results. Differing existing values stay unchanged; both versions are kept in a conflict archive for review. Review the archive and edit the course checklist yourself if needed. Older general checklists are transferred but remain excluded from detailed dashboard totals.
Recovery restores the last pre-import snapshot only when no later edits would be overwritten. A recovery snapshot is saved before every import; storage must have enough room. Refresh or reload any checklist after importing on another tab.
Nothing has been imported.
Test Android Chrome with TalkBack and iPhone Safari with VoiceOver separately. Automated browser checks cannot confirm spoken announcements. Keep notes identifying the device, browser, screen reader, date, page and exact issue. Do not mark a test passed unless you performed it.
Save observations: use Backup verification below with a reference such as “TalkBack accessibility review” or “VoiceOver accessibility review.” Put each tested step and result in Notes; leave unrelated restore/safeguard results Not tested. Save, reload to check, then export a fresh backup. Notes stay in this browser and are included in your private exports.
Save an accessibility observation →ALL PROGRAMMING, AI & IT COURSES
52 tracks · 296 lessons. Follow the steps, compare the expected outputs and record what you actually see. No live AI requests are needed. The older general checklist below remains unchanged.
Compare values and meaning, not just formatting. These expectations come from the course material. Record mismatches; do not automatically mark a lesson passed.
Results stay only in this browser on this device. They do not sync across phones. Use normal browsing, not private mode. Existing device checklists and learning progress are separate and are not reset.
Results and notes are saved only in this browser. Android and iPhone have separate checklists.
Your checklist is ready.
Each link opens a separate tab, keeping this checklist available. Tap Check task or Check exercise after the page loads.
90 | 60
SQL · Inventory project ↗Expected: 12, 0, 0 on separate rows; SQL headers may appear.
Python · Data project ↗Expected: 12, 0, 0 on separate lines.
Go · Inventory project ↗Expected: 12, 0, 0 on separate lines.
PHP · Inventory project ↗Expected: 12, 0, 0 on separate lines.
First use downloads runtime files. Keep the tab open and allow time for loading. These finite checks do not prove that every program is correct.
All 28 programming, markup and data-format tracks, with 51 advanced lessons and 8 additional TODO exercise links. Open a language below to choose a lesson.
Console outputs retain their line breaks. SQL can also show column headers. HTML and CSS have visual results; JSON and XML show the value checked by the lesson, which may differ from the formatted validation display.
28 tracks
Visual preview
Expected visual result
A structured enquiry page with a labelled message field
Visual preview
Expected visual result
One column on narrow screens and three on wider screens
Browser runtime
Expected example output
2
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Browser runtime
Expected example output
2
Expected example output
12 0 0
Browser runtime
Expected example output
90 | 60
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
3
Expected example output
12 0 0
Data validation
Expected checked value
true
Data validation
Expected checked value
49
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Expected example output
1:7 emptyOpen runnable TODO exercise ↗
Expected output after solving the TODO
8 checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Expected example output
09:00-10:30 15:00-15:30 Total: 120 minutesOpen runnable TODO exercise ↗
Expected output after solving the TODO
12 project checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Expected example output
2147483648 -3 -3 2 0Open runnable TODO exercise ↗
Expected output after solving the TODO
417 checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Expected example output
Offset -11s -> bucket -2 Offset -10s -> bucket -1 Offset -1s -> bucket -1 Offset 0s -> bucket 0 Offset 9s -> bucket 0 Offset 10s -> bucket 1Open runnable TODO exercise ↗
Expected output after solving the TODO
15 project checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Expected example output
1 -1 2Open runnable TODO exercise ↗
Expected output after solving the TODO
605 checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Expected example output
205 -> Mouse 999 -> Not foundOpen runnable TODO exercise ↗
Expected output after solving the TODO
10 project checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Expected example output
éc 🦀ruOpen runnable TODO exercise ↗
Expected output after solving the TODO
12 checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Expected example output
Suggested prefix: invoice_2026_0 Unicode prefix: 🦀ruOpen runnable TODO exercise ↗
Expected output after solving the TODO
15 project checks passed
The starter is intentionally incomplete. Implement the TODO helper, then run Check exercise. The worked solution is available in the lesson.
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
3
Expected example output
12 0 0
Browser compiler / runtime
Expected example output
2
Expected example output
12 0 0
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
Beginner subset interpreter · Guided problem-solving; full advanced language features are unsupported.
Expected example output
Approved
No matching track. Try a language name such as C#, Rust or SQL.
Select Pass only after observing the result on your phone. Use Fail or Blocked if you could not complete a step.
Open one of the links above, run its check and compare the actual output with the expected result. Repeat with the other links you want to test.
Add a blank line to the code, then run it again. Confirm the result still passes. Note which language you tested below.
Reload that same exercise tab. Confirm your added blank line remains. Run the check again and confirm the expected output. Repeat in both the academy and compiler lab.
In SQL Inventory, add INSERT INTO items VALUES(1,-1); and run. Expect a quantity constraint error. Remove that line and run again; the original exercise should pass.
Open Go and SQL or PHP in separate tabs. Add a new comment such as // phone test 1 at the end of the Go source, then start it. Quickly run SQL or PHP in the other tab. While Go is active, expect “Waiting for another academy runtime”. A saved Go build may finish too quickly; use a different comment for the next attempt.
Let Go finish. Confirm the waiting SQL or PHP exercise starts and produces its expected result. If your phone suspends a background tab, return to Go so it can finish, then return to the waiting tab. Record this behaviour below.
Start a fresh Go build and queue the second exercise again. Tap Stop in the waiting tab. Confirm it says the run stopped and the run/check controls become available. Stop Go too if you no longer need it.
Confirm code, output, loading messages and Run, Check and Stop controls remain readable and usable in portrait and landscape. The code editor itself may scroll.
Nothing is submitted automatically. Copy the report yourself when you want to share it.