Accessibility, device and global-use guidance
Choose a workable browser, understand current language and region limits, and request help with an access barrier.
Last updated 2026-08-28
What you'll achieve
- Choose a supported editing workflow
- Recover from an interrupted connection
- Identify current accessibility and region boundaries
Browser IDE and constrained devices
The full browser IDE requires a current desktop Chrome or Edge browser with cross-origin isolation and SharedArrayBuffer. Dependency installation and the development server use the device's memory, CPU and connection. BlinkHost does not publish a minimum RAM guarantee. On a low-memory or metered connection, use local development plus Git import and managed repository previews instead of depending on the browser runtime.
Autosave retries bounded transient failures and reports when a save has not completed. A disconnected tab is not an offline editor: keep it open, restore connectivity and wait for Saved. If a revision conflict appears, reload the current workspace before editing further so another session is not overwritten.
Accessibility
Public pages and common dashboard controls are designed for keyboard focus, semantic labels, zoom and responsive layouts, but BlinkHost does not currently claim conformance to a named accessibility standard or publish a complete assistive-technology test matrix. The code editor and embedded preview can also inherit accessibility limitations from their underlying tools or customer application. Report a keyboard, screen-reader, contrast or zoom barrier to support@blinkhost.me with the page and browser; do not include credentials.
Language and location
The product interface and standard support are currently provided in English. BlinkHost does not currently offer customer-selectable application or database residency regions. The service is intended for lawful use from supported internet locations, but payment-provider availability, sanctions, export controls and local law can restrict use. Contact support before purchasing when country availability or data location is a contractual requirement.
Production traffic uses BlinkHost's configured edge delivery network; no public per-region latency guarantee is currently offered. Test a representative application from the countries and network conditions that matter to its users before launch.
Tested device scope
Public authentication pages and the common dashboard navigation expose named keyboard-focus targets. The authenticated dashboard is exercised at a 390 × 844 viewport for horizontal overflow and focus entry. These tests do not certify every workflow, assistive technology or accessibility standard.
On a phone or tablet, use the dashboard for lightweight review and account navigation; BlinkHost does not currently claim the full IDE, deployment workflow or billing workflow as phone-supported. The browser IDE is a desktop workflow and currently requires Chrome or Edge with cross-origin isolation and SharedArrayBuffer. It performs a browser-capability check before opening. There is no published minimum-RAM guarantee; try the Free plan with a representative repository before purchasing, and prefer local development plus managed Git previews on a constrained device.
Zoom and narrow-screen support is strongest on public pages and common dashboard controls. The code editor, terminal and embedded customer preview may require desktop width and can inherit limitations from their underlying tools or the customer application. Report a blocking keyboard, zoom or screen-reader issue with the exact page and browser so it can be reproduced.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.