Web Accessibility Statement
Our commitment to WCAG 2.2 Level AA conformance, how we are actively improving accessibility, known limitations, and how to contact us with accessibility feedback.
Our Commitment
Qcom Ltd is committed to making our website accessible to as many people as possible, including people with disabilities, people who use assistive technologies, and people who depend on keyboard, switch, or voice navigation.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). These guidelines define how to make web content perceivable, operable, understandable, and robust for people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.
We treat accessibility as an ongoing responsibility, not a one-time fix. We are actively working to identify and address gaps, and we welcome feedback from users who encounter barriers on our site.
Conformance Status
Partially Conformant - Actively Improving
The Qcom Ltd website partially conforms to WCAG 2.2 Level AA. This means that some parts of the content do not yet fully meet the standard. We are actively working to address the specific limitations listed in the Known Limitations section below.
Formal colour contrast testing and a full interactive component audit, including the live chat widget and the multi-level Services navigation menu, have not yet been conducted. All other criteria have been assessed through self-evaluation and automated browser tools.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
What WCAG 2.2 Level AA Requires
WCAG 2.2 is organised around four principles. Each principle groups the specific requirements (called success criteria) that a website must meet. The following is a summary of Level AA requirements and how they apply to this site.
WCAG 2.2 vs 2.1: WCAG 2.2 (published October 2023) extends WCAG 2.1 with six new success criteria at Level A and AA. These additions focus specifically on users with low vision, cognitive limitations, and motor disabilities. All WCAG 2.1 Level AA criteria are included within WCAG 2.2. This statement covers the full WCAG 2.2 Level AA set.
1. Perceivable - Visual Presentation & Contrast
Users must be able to perceive all information presented on the page regardless of which of their senses they use.
- Colour contrast (1.4.3): Body text and images of text must achieve a minimum 4.5:1 contrast ratio against their background. For large text (18pt or 14pt bold and above), the minimum is 3:1.
- Non-text contrast (1.4.11): User interface components (such as input field borders, checkbox outlines, and focus rings) and meaningful graphical elements must achieve at least 3:1 contrast against adjacent colours.
- Text resize (1.4.4): Users must be able to resize text up to 200% using browser zoom without losing content or functionality.
- Images of text (1.4.5): Text must be rendered as real text in HTML, not as images of text, unless the specific presentation is essential (logotypes are exempt).
- Reflow (1.4.10): Content must reflow at 400% zoom (320 CSS pixels wide) without requiring two-dimensional scrolling.
- Text alternatives (1.1.1): All meaningful images must have descriptive alternative text. Decorative images must be hidden from assistive technologies.
- Input purpose (1.3.5): The purpose of form inputs collecting personal information must be programmatically identifiable so browsers and assistive technologies can autofill or relay context to users.
2. Operable - Navigation & Interaction
Users must be able to operate all interface components and navigate all content.
- Keyboard access (2.1.1): All functionality must be accessible using a keyboard alone, with no keyboard traps.
- Bypass blocks (2.4.1): A mechanism to skip repeated navigation blocks (such as a skip link) must be available on every page.
- Visible focus (2.4.7): A clearly visible focus indicator must be present whenever a user navigates by keyboard.
- Multiple ways (2.4.5): More than one way must be available to locate a page within the site (e.g. navigation menu plus a site search or sitemap).
- Consistent navigation (3.2.3): Navigation menus that repeat across pages must appear in the same relative order each time.
- Focus not obscured - WCAG 2.2 (2.4.11): When an element receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers or cookie banners.
- Dragging movements - WCAG 2.2 (2.5.7): Any feature that requires a dragging gesture must also be operable by a single pointer click or tap, with no dragging required.
- Target size minimum - WCAG 2.2 (2.5.8): Interactive targets (buttons, icons, links) must measure at least 24×24 CSS pixels, or have sufficient spacing so targets do not overlap.
3. Understandable - Readability, Forms & Error Handling
Users must be able to understand both the information and how to operate the interface.
- Page language (3.1.1): The lang attribute on the <html> element must correctly identify the primary language of each page.
- Error identification (3.3.1): When a form error is detected automatically, the field in error must be identified and the error described in text.
- Labels or instructions (3.3.2): Labels or instructions must be provided for all user inputs.
- Error suggestion (3.3.3): Where an input error is detected, and a correction is known, a suggestion must be provided to the user unless doing so would compromise security.
- Consistent help - WCAG 2.2 (3.2.6): Help mechanisms (such as contact details or a support link) that repeat across pages must appear in the same relative location on every page.
- Redundant entry - WCAG 2.2 (3.3.7): Information already entered by a user within the same session or process must not be requested again unless re-entry is essential or for security reasons.
- Accessible authentication - WCAG 2.2 (3.3.8): Where a user must authenticate, the process must not rely solely on a cognitive function test (such as remembering a password or solving a puzzle) unless an alternative method or assistance is provided.
4. Robust - Technical Compatibility
Content must be robust enough to be interpreted reliably by current and future assistive technologies.
- Name, role, value (4.1.2): All user interface components must expose their name, role, and current state or value programmatically so assistive technologies can interpret and relay them correctly.
- Status messages (4.1.3): Status messages (such as form submission confirmations or error alerts) must be programmatically determined through role or properties (for example aria-live) so they are announced to screen reader users without requiring focus to move to the message.
Media Requirements
Pre-recorded video content must include audio descriptions for visual elements. Live audio content must provide real-time captions. The Qcom Ltd website does not currently host embedded synchronised media (pre-recorded video with audio, or live streams). Should video or live audio content be added in the future, captions and audio descriptions will be provided in accordance with WCAG 2.2 criteria 1.2.4 and 1.2.5.
How We Address These Requirements
The following measures are currently in place across the Qcom Ltd website:
Perceivable
- Meaningful images, including partner logos, accreditation badges and case study photography, carry descriptive alternative text following the alt attribute standard.
- Decorative background graphics and icons use alt="" and role="presentation" to be skipped by screen readers.
- The site is fully responsive; content reflows correctly across viewport widths including 320 px.
- Typography uses relative units; text resizes correctly to 200% browser zoom without overflow.
- No images of text are used for informational content; the Qcom Ltd logo is a logotype (see Exceptions below).
- The site does not autoplay audio or video content.
- Colour is not used as the sole means of conveying information, indicating an action, or distinguishing elements.
- An on-page accessibility toolbar provides high-contrast colour inversion and four colourblind simulation modes (deuteranopia, protanopia, tritanopia, achromatopsia), with preferences saved across sessions.
Operable
- A skip-to-main-content link is provided at the start of every page, allowing keyboard users to bypass the header and navigation menu.
- Primary navigation links, footer links and standard form controls are reachable and operable by keyboard.
- More than one way is available to locate a page within the site: the primary navigation menu, including its sub-menus, and a dedicated sitemap page.
- Keyboard focus indicators are visible on standard interactive elements via focus styles in the site stylesheet.
- All pages have unique, descriptive <title> elements.
- Headings follow a logical hierarchy on all pages.
- HTML landmark regions (<header>, <nav>, <main>, <footer>) are used throughout.
- The sticky site header is compact; keyboard-focused elements below it are not entirely obscured (WCAG 2.2 §2.4.11).
- No drag-only interactions are used; all interactive controls use standard pointer or keyboard events (WCAG 2.2 §2.5.7).
- Social icon links in the footer include accessible names beyond visual icon presentation.
Understandable
- All pages declare <html lang="en"> for correct language identification.
- Header and footer navigation appear in the same order on every page (WCAG §3.2.3).
- Interactive controls with the same function are named consistently across pages (WCAG §3.2.4).
- The contact form identifies required fields and displays error messages in text when validation fails (WCAG §3.3.1).
- Contact details (email and phone number) appear in the footer on every page in a consistent position (WCAG 2.2 §3.2.6).
- No multi-step process on the site requires a user to re-enter information already provided in the same session (WCAG 2.2 §3.3.7).
- The main website has no user authentication; no login, password, or cognitive-test step exists on qcom.ltd itself (WCAG 2.2 §3.3.8 not applicable to this domain).
- User preferences set through the accessibility toolbar (font size, colour mode) persist across pages using localStorage.
Robust
- WAI-ARIA roles, states, and properties are applied to standard interactive components, including navigation and form controls.
- HTML is written to semantic standards; landmark elements are used in preference to generic <div> containers where possible.
- Compatibility is targeted at current versions of Chrome, Firefox, Safari, and Edge with commonly used assistive technology combinations (NVDA + Chrome, JAWS + Chrome, VoiceOver + Safari on macOS and iOS).
Known Limitations
Despite the measures above, the following known limitations remain. We are actively working to resolve them:
Live chat widget - accessibility not yet audited
The Contact Us page includes a third-party live chat widget, accessed via the “Chat Online” icon. This widget is provided by an external vendor, and its full keyboard operability, focus management and screen reader compatibility have not yet been formally audited against WCAG 2.2.
Impact: Screen reader and keyboard-only users may find the chat interface difficult to open or operate reliably.
WCAG 2.2 §2.1.1 Keyboard (A) | §4.1.2 Name, Role, Value (A)
Multi-level Services menu - keyboard and screen reader behaviour not fully verified
The main “Services” navigation item expands into a list of sub-services. Full keyboard operability and correct aria-expanded and aria-haspopup announcements have not yet been formally tested across all browser and assistive technology combinations.
Impact: Keyboard and screen reader users may have difficulty discovering or reaching individual service pages listed under the Services menu.
WCAG 2.2 §2.1.1 Keyboard (A) | §4.1.2 Name, Role, Value (A)
Colour contrast - not formally tool-verified
Visual review suggests the site's primary text and background colours meet the 4.5:1 minimum for body text, and the brand accent colour used for buttons and links is estimated to meet the 3:1 minimum for large text and interface components. However, a formal audit using an automated contrast checker (such as WCAG Contrast Analyser or axe) has not been completed across all colour pairings on all pages, including the hero banner overlays and dark footer background.
Impact: Some colour combinations, particularly text set over photographic banner backgrounds, may not formally meet 4.5:1 without verified measurement.
WCAG 2.2 §1.4.3 Contrast Minimum (AA) | §1.4.11 Non-text Contrast (AA)
Contact form - field labelling and error handling not fully verified
The Contact Us page includes a contact form for general enquiries. It has not yet been formally confirmed that every field carries a programmatically associated <label> element, rather than placeholder-only text, or that validation errors are announced in text and correctly associated with their corresponding field.
Impact: Screen reader users may not receive a clear field description once typing begins, and may not be reliably informed which field an error relates to.
WCAG 2.2 §1.3.1 Info and Relationships (A) | §3.3.1 Error Identification (A) | §3.3.2 Labels or Instructions (A)
Embedded Google Maps and Google Tag Manager iframes - accessible titles not fully verified
Location details are supported by an embedded Google Maps panel, and Google Tag Manager <noscript> iframes are present on every page for analytics. It has not been confirmed that every iframe on the site carries a descriptive title attribute.
Impact: Screen reader users navigating by landmark or iframe may encounter unlabelled or ambiguously labelled embedded content.
WCAG 2.2 §4.1.2 Name, Role, Value (A)
Animated statistic counters - accessibility not confirmed
The “Service Delivery Results” section on the homepage displays key statistics, including call waiting time, resolution rate, tickets resolved, SLA performance, and customer satisfaction, using an animated count-up effect. It has not been confirmed that the completed figures are exposed to screen reader users as static, readable text once the animation finishes.
Impact: Screen reader users may not reliably receive the completed statistic values.
WCAG 2.2 §4.1.2 Name, Role, Value (A)
Touch target size - not fully verified
WCAG 2.2 requires interactive targets to be at least 24×24 CSS pixels, or have sufficient offset spacing from adjacent targets. Social media icon links and accreditation badge links in the footer have not been formally measured against this criterion.
Impact: Users with motor impairments or those using touchscreens may find some small targets difficult to activate accurately.
WCAG 2.2 §2.5.8 Target Size Minimum (AA)
External client support portal - outside the scope of this statement
The “Raise support ticket” link in the footer directs to a separate client portal hosted and operated independently of the main Qcom Ltd website. As a third-party system outside our direct control, its accessibility is not covered by this statement. Users who experience difficulty with the client portal are welcome to contact us directly using the details below, and we will assist through an alternative channel.
Google Tag Manager noscript iframe - missing title attribute
All pages include a hidden Google Tag Manager <noscript> iframe with zero dimensions and display: none styling. This iframe does not yet carry a title attribute. A title="Google Tag Manager" attribute has already been added to this accessibility statement page and is being rolled out across the full site.
Impact: Negligible; the element is invisible, but it is technically a non-conformance.
WCAG 2.2 §4.1.2 Name, Role, Value (A)
If you encounter an accessibility barrier not listed above, please report it. We treat all accessibility reports as priority issues and aim to respond within five working days.
Exceptions - Where Contrast Requirements Do Not Apply
WCAG 2.2 explicitly excludes the following from the colour contrast requirement (criteria 1.4.3 and 1.4.11). These are not limitations; they are specified exceptions in the standard:
Disabled interface elements
Components that are disabled, such as a greyed-out submit button when a form is incomplete, are exempt from contrast requirements. Their reduced contrast is intentional, signalling to users that the component is not yet interactive. No contrast minimum applies to inactive or disabled state styling.
Decorative text and purely decorative elements
Text that is purely decorative and conveys no information, as well as text hidden from view or not visible to any user, is exempt. On this site, background overlay text used purely for visual texture is treated as decorative and is not relied upon to convey any meaning.
Logotypes
Text that forms part of a logo or brand name is exempt from the contrast requirement. The Qcom Ltd logo, which includes the brand wordmark as an image, is considered a logotype under WCAG 2.2 and is therefore not subject to the 4.5:1 text contrast minimum.
Feedback and Contact
We welcome feedback on the accessibility of the Qcom Ltd website. If you experience a barrier, find something difficult to use, or have a suggestion for how we could improve, please contact us:
- Email: admin@qcom.ltd
- Phone: +44 (0) 203 150 1401
- Contact form: qcom.ltd/contact-us
We aim to respond to accessibility enquiries within five working days. If the issue requires development changes, we will provide an estimated timeframe for resolution.
Technical Specifications
The Qcom Ltd website is built with HTML5, CSS3, and JavaScript, and is managed through a content management system. The site relies on the following technologies for accessibility:
- HTML5 semantic elements and landmark roles (<header>, <nav>, <main>, <footer>).
- CSS3 for layout, responsive behaviour, and focus styles.
- JavaScript for interactive components: the primary and mobile navigation menus, the live chat widget, and the cookie consent banner.
- Google Tag Manager for analytics and tracking.
- An embedded Google Maps panel used to display office locations.
- A skip-to-content link provided at the start of every page.
Assessment Approach
Qcom Ltd assessed the accessibility of this website using self-evaluation and automated browser tools. The specific methods used include:
- Self-evaluation against WCAG 2.2 Level AA success criteria - each criterion was reviewed manually by the development and marketing team.
- Automated browser tools - structural issues, including missing alternative text, absent form labels, improper heading hierarchy, and missing ARIA attributes, were identified using browser-based accessibility inspection tools.
- Keyboard navigation testing - primary pages tested for keyboard operability, logical focus order, and visible focus indicators.
- Screen reader spot-checks - key pages reviewed with VoiceOver on macOS and Safari.
- Responsive and reflow testing - key breakpoints tested from 320 px upwards.
No formal accredited third-party audit has been conducted. We plan to commission an independent evaluation in the future. The W3C provides a full reference at How to Meet WCAG (Quick Reference).
Date of This Statement
This accessibility statement was created in August 2026 and reflects the state of the Qcom Ltd website at that date. It will be reviewed and updated whenever significant content or structural changes are made to the site, and at least once annually.
Unlimited possibilities
Global IT Solutions at your fingertips
Find out more >>