--- title: "Mobile accessibility scan" date: "2022-03-16T12:50:00+00:00" summary: "Discover how to set up and use Mobile Accessibility scans for improved website responsiveness and user experience on mobile devices." image: type: "page" url: "/web-governance/mobile-accessibility-scan" id: "4f7e2613-9987-4a31-a8a0-84c943bc9de1" --- Table of contents will be added Introduction ------------ When Mobile Accessibility is enabled, an additional scan of the website is done to simulate how it renders on a mobile device. This data is used to pick up device-specific code that only loads when a website opens on a mobile device. Based on this mobile rendition of the website, we can perform two additional checks in addition to the accessibility checks that already run on the website. These checks determine if a web page is properly responsive. Responsiveness is a basic requirement for an accessible website. The checks are displayed in the user interface and can be filtered out of the other checks. They are also displayed in the web browser extension. * **Check 1: Is pinch-to-zoom disabled?** Some websites have, on purpose, disabled the option for visitors to be able to zoom in on a web page by pinching with their fingers. This is not an accessible experience, as visually impaired users should always have a zoom option, even on a mobile device. This check generates a flag if pinch-to-zoom is disabled. * **Check 2: Does the web page require two-dimensional scrolling?** If a website is not properly responsive, there might be scenarios where a user needs to scroll both vertically and horizontally to read a paragraph of text or view an image. Typically, this happens if a website owner has not defined the image size for mobile devices, and the image displays in the same size as it would on a desktop computer (meaning that the visitor needs to scroll up and down and sideways to view all of the content.) This is not an accessible experience for visually impaired users and users who have motor disabilities (it is very strenuous for your wrist or arm to scroll in two dimensions.) This check generates a flag if a web page requires two-dimensional scrolling. Enable mobile scans ------------------- This section provides instructions on how to enable mobile scans on a website, 1. Contact [support](mailto:support@monsido.com) and request Mobile Scans for the website. 2. Select a Mobile Guideline: * WCAG 2.1 AA mobile * WCAG 2.1 AAA mobile. For more information about accessibility guidelines, visit [Accessibility setup](/node/61656). Disable mobile scans -------------------- This section provides instructions on how to disable mobile scans on a website. 1. Contact [support](mailto:webgovsupport@acquia.com) and make a request to disable mobile scans. Important When the mobile scan is disabled, it applies to **all domains** in the user plan. This feature is closely tied to accessibility scans and the feature must be turned off from the support team end. No accessibility scans are done until the accessibility feature is turned on again and reconfigured. You can set this up, visit the links below for instructions. 2. Turn on and configure accessibility scans for each domain on the account. For more information, visit: * [Domain scan setup](/node/58556) * [Accessibility introduction](/node/58686) Filter for mobile-only error type --------------------------------- To filter for mobile-only issues and errors: 1. Navigate to the **Domain overview** and select your domain. 2. On the domain menu bar, click **Accessibility** (icon of a human figure with outstretched arms). The system opens the _Accessibility_ _summary_ page. ![The location of the Accessibility button on the domain menu bar.](https://acquia.widen.net/content/92f298d5-56bc-4ba1-9520-489b45eeefdf/web/WebGov_DomainToolbar-AccessibilityButton.png?w=720&itok=l8I6lgrC) 3. Click **Checklist** on the left menu. 4. Click **Filter**. The _Filters_ list expands. 5. Select **Accessibility error type**. The _error type_ list expands. ![The location of the Accessibility Error Type option in the filter menu on the Accessibility Checklist page.](https://acquia.widen.net/content/ed47c870-f6db-4f18-aeae-f51557bc6a84/web/WebGov_Accessibility-Checklist-AccessibilityErrorType.png?w=720&itok=9kkEFiGs) 6. Select **Mobile only**. The system opens the Accessibility Checklist page with the filter _Accessibility error type: Mobile only_ applied. The page is divided into the following categories: * **Issues to Fix** * **Warnings** * **Issues to Review** **Each of the categories above contains a list with the following table headers:** * **Check** * **Responsibility** * **Success criteria** * **Help Center** * **Action button** * **Domain Compliance** The filter is only visible if the scan is set to perform the mobile scan. _Tip!_ You can also find mobile accessibility issues in the **Accessibility** > **Pages with Failing Checks** section. **Additional resources** ------------------------ For more information about accessibility requirements, visit: * The official site for [Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/) * Quick Reference: [How to Meet WCAG 2.1 Requirements](https://www.w3.org/WAI/WCAG21/quickref/)