IS TELETEXT-TOOLS ACCESSIBLE?

It aims to be predictable, tap-friendly, and TV-safe.
The no-scroll frame helps many users because nothing “moves away”.

WHY DOES “NO SCROLL” HELP?

• You never lose your place by accident
• Header and footer stay consistent
• Navigation stays the same everywhere

If content grows, it becomes another screen.

WHAT IS COVERED HERE?

Devices, browsers, swipe/touch behaviour, keyboards, zoom/text size, colour/contrast, screen readers, reduced motion, and quick fixes.

DOES IT WORK ON iPHONE?

Yes. iPhone is a primary target.
Expect: one-column layouts and internal screens for longer pages.

DOES IT WORK ON iPAD?

Yes. iPad portrait and landscape are supported.
Wider layouts may show more throughput (more content at once).

ANDROID / WINDOWS / MAC?

Yes in modern browsers.
Older devices may feel slower, but layouts should stay stable.

SMALL SCREENS

Very small screens may need more internal screens.
That is normal Teletext behaviour.

SAFARI (iOS / macOS)

Supported. iOS Safari has unique touch quirks (see next pages).

CHROME / EDGE

Supported. Usually the most consistent for desktop and Android.

FIREFOX

Supported. If anything behaves oddly, try Chrome as a comparison.

BRAVE / PRIVACY BROWSERS

Supported, but aggressive privacy settings can block local storage.
Result: some “remembered settings” may not stick.

SWIPE = INTERNAL SCREENS ONLY

Swipe left/right to move between (1/3), (2/3), etc.
Swiping does not change page numbers.

WHY DO TAPS SOMETIMES FAIL AFTER A SWIPE?

iPhone/iPad can trigger a “ghost tap” after swiping.
Teletext-Tools blocks taps briefly after swipes to prevent accidental jumps.

BEST PRACTICE

• swipe
• pause for a moment
• then tap

This makes navigation feel consistent.

PAGE BOX (3 DIGITS)

The PAGE box expects a 3-digit Teletext number.
If nothing happens, check you entered all 3 digits.

DECIMALS (UK TIP)

Use a dot for decimals (1.5).
Some keyboards show commas — commas may not behave as decimals.

KEYBOARD HIDING CONTENT

On mobile, the keyboard can hide the bottom of the page.
Tap outside the input to dismiss it and reveal the rows again.

WHY DOES BIG TEXT SOMETIMES CLIP?

Teletext-Tools uses a fixed frame (like a TV).
Extremely large system text or browser zoom can push content beyond the frame.

BEST SETTINGS

• keep browser zoom near 100% (desktop)
• use moderate OS text sizing (mobile/tablet)
• avoid “Display Zoom” if it causes clipping

IF TEXT LOOKS TOO BIG

Reduce OS text size slightly and reload the page.

WHY THESE COLOURS?

The Teletext palette is deliberately high-contrast and readable on many screens.
Colour is used to separate sections quickly.

COLOUR MEANING (GENERAL)

Yellow often highlights emphasis and navigation.
Cyan often marks labels and structure.
Red is used for warnings or urgent notes.

BACKGROUND IMAGES (CLOCK PAGES)

For best readability: use darker, simpler photos with fewer bright areas.

DO SCREEN READERS WORK?

Many areas are structured as standard links and sections.
The PAGE box and navigation controls are designed to be discoverable.

BEST WAY TO NAVIGATE

• use “Links list” to jump quickly
• use landmarks/regions where supported
• page numbers in rows are usually links

A NOTE ON DENSITY

Teletext is intentionally dense. If it feels “busy”, it may help to use internal screens and the index (P199) to reduce scanning.

IS THERE FLASHING CONTENT?

Teletext-Tools aims to avoid flashing effects.
Transitions are kept short and functional.

REDUCED MOTION

If you use “Reduce Motion” at OS level, the best experience is to keep movement minimal and rely on paging rather than animation.

WHY TRANSITIONS EXIST

Screen transitions are a navigation cue (like flipping pages).
They are kept brief for clarity.

TAPS NOT RESPONDING?

If you just swiped, wait a moment and tap again.
Then try a single reload.

SETTINGS NOT SAVING?

Private browsing or strict privacy settings may block storage.
Try normal mode or a different browser.

TEXT OVERLAPS HEADER/FOOTER?

That is a layout fault (not your device).
Please report it via Contact (P104).

WHAT TO INCLUDE IN A REPORT

• page number
• device + orientation
• browser name
• what you expected vs what happened