Tablet motion permissions: what to check

You are reviewing whether a tablet can provide motion input for an accessible app, but the page shows no movement data or a permission prompt never appears. A missing reading can mean access is blocked, the browser does not support that sensor, or the tablet does not have it.

Use the Sensors Test to check the tablet's available motion sensors in its browser. Then review permissions and accessibility settings separately, so you do not mistake a browser limitation for a hardware fault.

Check motion access on the tablet

1. Open the Sensors Test on the tablet you are reviewing. Use the same browser and profile as the accessibility app, because permissions can differ between browsers.
2. When the browser asks for access, choose Allow if you are comfortable granting it for this check. If no prompt appears, continue with the available sensor controls rather than assuming the tablet has no sensors.
3. Hold the tablet still, then tilt it gently in each direction. Look for changing motion or gyroscope readings. Keep the tablet over a clear, stable surface and avoid sudden movements.
4. Check the other sensor readings you need for the review, such as compass, light, location, or vibration. Location is a separate, more sensitive permission, so grant it only if location access is part of the test.
5. Repeat the check after reviewing the browser's site permissions. Note the tablet model, operating system, browser, permission choice, and which readings changed.

For a fair accessibility review, test more than one browser if the tablet supports them. A site can work with motion input in one browser and show no readings in another, even on the same device.

What the result means

Motion readings change when you tilt the tablet

The browser is receiving motion data. This confirms that the sensor and browser path can provide readings to a web page. It does not prove that a particular app handles those readings accessibly, so test the actual app's controls, instructions, and alternatives too.

Readings stay still while the tablet moves

Access may be blocked, the browser may not expose that sensor, or the device may not provide the reading. Check site permissions, then try another supported browser on the same tablet. If the result changes, the difference points to browser support or settings rather than a failed sensor.

A permission prompt appears, but the test still shows no useful data

A permission allows access where the browser and operating system support it. It cannot add a sensor that the tablet lacks, and it does not guarantee that every sensor type is available to web pages. Check the sensor separately in the test and compare with another browser or a known device.

Motion works, but the accessibility app behaves differently

The sensor is producing readings, but the app may not be requesting them, may interpret them differently, or may have its own permission setting. Check the app's instructions and test its response with small, repeatable movements. A browser test cannot confirm how another app processes sensor data.

Location or vibration is missing

These are separate capabilities from motion and gyroscope readings. Location needs its own permission and can be unavailable when location services are off. Vibration support varies by device and browser, so a missing vibration response alone does not show that the motion sensor is faulty.

How to fix a blocked or missing permission

1. Check the page's permission. In the browser, open the site information or permissions control beside the address bar. If motion access is listed as blocked, change it to allow and reload the page. The control's name and available permissions vary by browser.
2. Review motion access in Android Chrome. Open Chrome Settings › Site settings › Motion sensors and allow access if that option is available. Then return to the page, reload it, and respond to any new prompt.
3. Check Safari on iPad. Open Settings › Apps › Safari › Motion & Orientation Access and turn it on if the option appears. On older iPadOS versions, look under Settings › Safari. Return to Safari and reload the page.
4. Allow location only when needed. On Android, check Settings › Location, then check Chrome's location permission under Settings › Apps › Chrome › Permissions › Location. On iPad, check Settings › Privacy & Security › Location Services and review Safari Websites. Menu names can vary by operating system version.
5. Start the test after a tap. Some browsers require a direct tap on the page before motion access can be requested. Reload the test, interact with it, and look for a permission prompt. Do not repeatedly tap through prompts if the browser says access is unavailable.
6. Restart the browser and tablet. Close the browser fully, reopen it, and repeat the test. Restart the tablet if permissions appear correct but readings remain unavailable.

On an iPad, Settings › Accessibility › Motion contains options that change animation and movement effects. These are not the same as a website's sensor permission. Leave accessibility settings as the user needs them, and record their state if it may affect the app experience.

When to suspect a device limitation

If the same motion reading is unavailable across multiple browsers, check the tablet's model specifications and system updates before requesting repair. Some tablets do not include every sensor, and some operating systems intentionally limit sensor access from browsers. If a sensor that the device is meant to have also fails in other apps after permissions and updates are checked, contact the tablet maker or a repair service.

Keep the review focused on consent

For an accessibility review, document whether the page explained why it needed motion access, whether refusing access left a usable alternative, and whether the app continued working after permission was withdrawn. The Sensors Test runs in the browser. Only grant location access when you need to check that specific feature.