Guessistan

Accessibility at Guessistan

We want Guessistan’s daily puzzles to be playable by as many people as possible, regardless of device or ability. This page describes the accessibility practices currently built into the site, where support still has limits, and how to tell us when something gets in your way.

How can I play with a keyboard?

Guessistan uses focusable buttons, links, and text inputs for its main controls. A visible focus indicator shows where keyboard input will go. On puzzle boards, arrow keys can move between cells or cards where that direction makes sense, and Enter or Space can activate the focused control.

Games that support dragging also provide another way to act. Rasta paths can be built one tile at a time, System Jam vehicles can be selected and moved with arrow keys or separate move buttons, and Badshah squares can be marked from the keyboard. Lafzon Ka Jaal accepts a physical keyboard as well as its on-screen keys. The instructions inside each game describe the controls available there.

What does Guessistan provide for screen readers?

Interactive controls have names that describe their current purpose or state. Puzzle boards use grid, cell, group, selection, and pressed-state semantics where they fit the interaction. Some spatial games also describe board dimensions, positions, and goals in text so that their layout is not available only as a picture.

Status and error messages announce meaningful changes such as a submitted result, a completed puzzle, or a loading problem. When a transition removes the control a player was using, the replacement result or recovery surface receives focus deliberately. Decorative images stay out of the reading order, while gameplay artwork that carries meaning has a text description. These patterns improve access, but individual screen-reader and browser combinations can still behave differently.

Does a puzzle rely on color alone?

Where color communicates puzzle state, Guessistan also uses text, symbols, borders, patterns, or accessibility states. Examples include crowns and X marks in Badshah, selected and matched descriptions in the memory games, labelled selected cells in Rasta and Lafzon Ka Jaal, and textual feedback after guesses or moves.

The site includes light and dark themes, visible focus styles, and targeted support for forced-colors mode on complex boards. We test important states for legibility and distinction, but we do not claim that every color pairing or every device has been certified to a particular contrast standard. If a state is difficult to distinguish, please report the exact screen and theme you were using.

What happens when I prefer reduced motion?

Guessistan responds to the reduced-motion preference provided by your operating system or browser. Transitions and decorative animations are shortened or removed, and gameplay or completion motion in games such as Badshah, Rasta, System Jam, Yaad Hai, and Lafzon Ka Jaal is skipped when necessary.

Removing motion must not remove the result. A static board state, message, symbol, result heading, or screen-reader announcement remains available when an animation is suppressed, and changing the preference should not replay an effect that has already finished.

How does Guessistan work on phones, touchscreens, and with zoom?

The games use responsive layouts designed for narrow phone screens as well as larger displays. Interactive cards and many board controls are sized to at least 44 by 44 CSS pixels. Dense grids sometimes use smaller cells so that the complete puzzle remains visible, so those games also provide keyboard or labelled-control alternatives instead of depending on a precise tap alone.

Touch interactions avoid requiring a mouse, and drag-based games provide tap or button alternatives. Guessistan does not disable browser zoom. We test representative narrow viewports, touch input, responsive reflow, and targeted zoom cases, but cannot reproduce every combination of screen size, browser controls, text settings, and magnification.

How do puzzle timers behave?

A puzzle timer begins when the current game is ready to play in a visible, focused page. It pauses when you move to another route, switch away from the tab, or leave the browser in the background, and it freezes when the puzzle ends. Saved elapsed time can resume when you return to the same current puzzle in that browser.

The displayed clock remains readable to assistive technology, but its once-per-second changes are not announced as a live message. Hint and reveal cooldowns are separate: a cooldown may continue while you are away even though active playing time is paused. The final result reports the recorded active-play time.

What accessibility limitations are we still working on?

This is a description of current practices, not a formal accessibility certification. Automated checks and browser tests cannot cover every assistive technology, input method, browser, operating system, or personal setting. Dense spatial and visual puzzles can also require more effort to understand with magnification or a screen reader than a conventional form or article.

Accessibility work continues as the games and platform change. We review keyboard flow, names and announcements, focus movement, motion preferences, color modes, phone layouts, and touch behavior when relevant features change. Real reports show us barriers that our test setup may not reveal.

How do I report an accessibility problem?

Tell us what you expected, what happened instead, and the steps that led to the problem. If you can, include the game or page, your device and browser, the input method or assistive technology you were using, and whether the issue happens every time. A screenshot can help after you remove personal information.

Email admin@guessistan.com or use the accessibility-help section on our Contact page. We cannot promise that every barrier can be removed immediately, but we will make an honest effort to investigate and address the concerns and issues you report.