Free tools Windows power users keep installed
One-click scans. No signup required.
Improve mobile accessibility by preserving the same information and functionality at narrow widths and high zoom, making controls usable with different input methods, and giving forms clear labels, instructions, and error feedback. A responsive layout is a starting point, not proof of accessibility. Evaluate the page against WCAG 2.2; W3C’s mobile guidance explains how its criteria apply in mobile contexts, rather than defining a separate mobile standard.
Use WCAG 2.2 as the standard for mobile websites
W3C says it does not maintain separate guidelines for mobile accessibility. The web page itself is evaluated against the normative success criteria in the Web Content Accessibility Guidelines (WCAG); W3C’s Mobile Accessibility material is informative guidance for applying those criteria in mobile contexts. WCAG2Mobile discusses mobile applications and related contexts; it is not a separate conformance standard for websites.
For a practical review, consider whether content and functionality survive zoom and narrow reflow, whether controls work with touch, keyboard, speech, and assistive technology, whether form structure and feedback are programmatically exposed and visually clear, and whether the page can be checked across relevant viewport sizes and orientations.
Keep content usable at narrow widths and high zoom
WCAG 2.2 Success Criterion 1.4.10, Reflow, sets a benchmark for vertically scrolling content at a width equivalent to 320 CSS pixels, and for horizontally scrolling content at a height equivalent to 256 CSS pixels. At those dimensions, information and functionality should remain available without requiring scrolling in two dimensions, except where a two-dimensional layout is essential to the content’s meaning or use. WAI explains that 320 CSS pixels corresponds to a 1280 CSS-pixel starting viewport at 400% zoom. These are conformance conditions, not survey statistics. See the WCAG 2.2 Reflow criterion.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
Make the narrow layout a complete experience
- Let text, controls, and page sections reflow instead of clipping or forcing a fixed desktop-width canvas.
- Preserve the same meaningful information and available functions; do not make the mobile layout a stripped-down version that removes important content.
- Allow content to enlarge without overlapping, hiding controls, or making forms impossible to complete.
- Keep two-dimensional scrolling only for content whose use or meaning genuinely depends on it, such as a spatial diagram or data table.
- Check meaningful responsive states, including navigation, dialogs, forms, and error messages, rather than only the home page at one phone size.
Support orientation, touch, keyboard, and gestures
Do not lock a page to portrait or landscape unless a particular orientation is essential. W3C’s mobile guidance highlights relevant WCAG criteria including Orientation (1.3.4), Reflow (1.4.10), Pointer Gestures (2.5.1), Motion Actuation (2.5.4), Dragging Movements (2.5.7), Target Size (Minimum) (2.5.8), and Redundant Entry (3.3.7). This list is useful, but not exhaustive.
Make controls apparent and operable
- Use visible styling and understandable text to identify links, buttons, and other interactive elements. Do not make a subtle hover effect the only indication that something is interactive.
- Ensure interactive functions are available to keyboard users as well as touch users, and provide a single-pointer alternative when an operation otherwise depends on a complex gesture or dragging.
- Consider both target dimensions and the spacing between nearby controls, especially for frequent or consequential actions.
- Check WCAG 2.2 SC 2.5.8, Target Size (Minimum), and its exceptions directly before making a numeric compliance claim. Do not present 44 by 44 CSS pixels as the WCAG 2.2 AA threshold: that commonly cited size comes from WCAG 2.1 SC 2.5.5, Target Size, a Level AAA criterion with exceptions. See WAI’s explanation of WCAG 2.1 Target Size and the WCAG 2.2 Target Size (Minimum) criterion.
Make mobile forms understandable and easier to complete
Associate each field with a real label
Use a visible <label> associated with the control’s id. For example:
Rank #2
<label for="email">Email address</label>
<input id="email" name="email" type="email" autocomplete="email">A correctly associated label helps assistive technology identify the field and gives users a larger clickable area. Keep the label understandable to sighted readers too. A label placed above its field can reduce horizontal pressure on a narrow screen, depending on the layout. WAI’s tutorial explains labels for form controls.
Use appropriate input types and explain expectations
Choose suitable HTML5 input types, such as email or date, when they match the information requested. Browsers can use these types to present an appropriate virtual keyboard or native picker. Do not rely on a placeholder as the field’s only label: placeholder text disappears during entry, may have low contrast, and is not consistently interpreted as a label by assistive technology.
State which fields are required, what formats are expected, and any relevant constraints. Keep instructions available while the user enters a response. When there is an error, identify the affected field and explain how to correct it; do not communicate the problem by color alone. See WAI’s guidance on form instructions.
Improve visual clarity and navigation
- Use sufficient contrast and do not rely on color alone to convey meaning or status.
- Make links and controls easy to distinguish from surrounding content, and provide clear feedback when an action succeeds or needs attention.
- Use headings and spacing to group related content so people can scan a page and understand its structure.
- Keep navigation consistent. Where useful, offer more than one way to find content, such as search or a site map.
WAI’s designing for web accessibility tips cover these visual and navigation considerations.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Evaluate manually as well as with tools
A first-pass review can surface common barriers, but it cannot by itself establish WCAG conformance. WAI’s Easy Checks include keyboard access and form labels, instructions, and error handling. Build on those checks with representative mobile browsers and devices: try mobile screen readers, keyboard access where available, zoom and reflow, portrait and landscape, and form completion including errors. Check both visible presentation and whether structure and feedback are exposed to assistive technology.
Automated checks can help identify some issues, but they do not replace manual evaluation with different input methods and user contexts. Review important page types and responsive states, not just one viewport or a single successful path.
Or skip the browser setup
For screenshots of responsive page states during review, ScreenshotNeo is a website screenshot API and MCP server. It can capture a URL with a GET request; a screenshot can help inspect visual layout at a chosen viewport, but it does not determine whether a site conforms to WCAG or replace assistive-technology testing. Its API supports viewport and device options, full-page capture, and custom CSS and JavaScript. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The API supports PNG, JPEG, WebP, and PDF output.
Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for API options. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
