Bugs, ideas, and accessibility
Contact Us
Email is the only channel — there is no form, no account, and no ticket queue. Tell us what you tried and what happened, and we will look into it.
Include the page you were on, your device and browser, and what you expected versus what happened. Those three things resolve most reports in one reply.
The details that actually help
A useful report is short and specific: the URL, the device (phone, tablet, laptop, external monitor), the browser and rough version, the button or gesture you used, and what happened instead. A screenshot helps for an interface problem — although it will not capture a physical display fault, since the camera and the panel both interfere.
Please do not send passwords, payment details, private documents, or anything sensitive. Nothing about a browser utility needs them, and we would rather not receive them.
Fullscreen problems
Fullscreen is controlled by the browser, not by this site. On desktop, pressing Open Black Screen or clicking the preview requests it directly; if nothing happens, check that your browser has not blocked fullscreen for the site, and try disabling a recently added extension.
On iPhone and iPad, Safari does not offer the fullscreen API to web pages at all — that is an Apple platform decision, and every iOS browser inherits it because they all use WebKit. The iPhone black screen page works around it with a full-viewport view and Add to Home Screen. If you cannot exit fullscreen anywhere, press Escape, or use the browser's own exit control.
Colour, brightness, and pixel questions
If a colour looks wrong, tell us what you expected and what you saw. Before you write, it is worth ruling out the usual causes: night mode, HDR handling, a custom colour profile, reduced white point, a manufacturer reading mode, or a browser extension that tints pages. These change the result far more often than the page does.
If your concern is a pixel, band, tint, or cloudy patch on your display, that is your panel rather than the site — but we are happy to help you interpret it. Say where on the screen it appears and whether it survives across the black, white, blue, and yellow screens, since a mark that shows on every colour is physically on or in the panel.
Zoom lighting feedback
For a lighting problem, the useful details are the selected temperature in kelvin, the brightness percentage, the type and size of screen, and what the room lighting is doing. Every panel emits light differently, and your webcam's automatic exposure and white balance will change the result again — so what you saw in the camera preview is more informative than the word "wrong" on its own.
If you are suggesting a preset or a feature, describe the setup you are trying to improve: a call, a class, a stream, an interview, or a product shot. That distinguishes a missing feature from a bug.
Accessibility
Accessibility reports are the ones we most want to receive. Tell us if a control cannot be reached or operated with a keyboard, a button has no clear name, focus disappears, text breaks when enlarged, contrast is insufficient, or an instruction depends on seeing a colour. Mention your assistive technology and browser only if you are comfortable doing so — the description of the barrier matters more than the setup.
Because these pages show bright, saturated colours, use a comfortable brightness and stop if the light causes discomfort. If a default here is causing that, we would like to know.
What happens next
Messages are read and answered as time allows, usually with a follow-up question if a report is not reproducible yet. We use what you send to reply, fix a page, correct an instruction, or understand a recurring compatibility problem — nothing else. The Privacy Policy covers how email and the supporting infrastructure are handled.