Accessibility
Accessibility Statement
MobileTechWorld should be usable by as many people as possible, whatever their abilities or the technology they use. This statement sets out our commitment, the standard we work to, what we have done, where we know we fall short, and how to get help or report a problem.
Our commitment
We are committed to making mobiletechworld.com accessible to as many people as possible, including readers who use screen readers, keyboard navigation, screen magnification, speech input or other assistive technology. We treat accessibility as part of building the site properly, not as an afterthought, and we consider it alongside the Equality Act 2010 as good practice even though, as a private publisher, we are not a public-sector body.
The standard we aim for
We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) version 2.1 at level AA — the standard widely recognised in the UK as the benchmark for accessible websites. Most of the site meets this standard; the known exceptions are listed below, and we treat them as work in progress rather than as acceptable.
What we have done
Pages are built with semantic HTML5 — proper headings, landmarks and lists — so assistive technology can navigate them in a logical order.
Navigation, search and forms are operable by keyboard alone, and a skip-to-main-content link lets keyboard and screen-reader users jump past the header.
Body text uses readable type with generous line height, and we test our colour palette for contrast against WCAG 2.1 AA thresholds.
Informative images carry descriptive alternative text, and decorative images are marked so screen readers skip them.
The site is responsive and can be zoomed to 200% without loss of content or function, and we avoid auto-playing media. Video is hosted on platforms that support captions.
Known limitations
We are an independent publisher with a small team, and there are areas we are still improving. Some older articles imported from earlier versions of the site may have images without full alternative text; we add it as we re-edit those pieces. Some embedded third-party components — price-comparison widgets and retailer links — carry their own accessibility characteristics that we cannot fully control, and we choose partners with the best record available to us. A small number of older comparison and specification tables predate our current accessible-table work. If you hit any of these, please tell us and we will prioritise a fix.
Get help or report a problem
If any part of this site is difficult to use, or you need information in a different format, please tell us — we treat accessibility feedback as a priority. Email [email protected] with the page address and a short description of the problem, and we will aim to respond within five working days and to provide the content you need in an accessible form.
If you raise an accessibility complaint and are not satisfied with our response, you can contact the Equality Advisory and Support Service (EASS) for England, Scotland and Wales, or the Equality Commission for Northern Ireland (ECNI). We engage with every complaint and use it to improve the site.
How we test, and review date
We test the site using automated tools (including axe DevTools and Lighthouse accessibility audits) together with manual keyboard-only navigation and checks with assistive technology. Automated testing alone cannot catch every issue, which is why reader feedback matters to us.
This statement was last reviewed on 17 June 2026. We review it at least once a year and whenever we make a significant change to the site.