NewOffensive AI & LLM penetration testing is now available —Learn more →
xtreme.infosec
Book a call30 min · free · Google Meet
QASoftware testing

Accessibility Testing — a website and app that everyone can use, and that stands up to a WCAG audit

We test your website and app against WCAG with screen readers, keyboard-only use, zoom and automated tools. You get every barrier listed with the WCAG criterion, a screenshot and the exact fix for your developers.

WCAG 2.1 / 2.2 based auditReal screen reader testingExact fix for every issue
Free quoteWe reply within 1 hour

Get an accessibility testing quote

Share a few details and get clear next steps, a timeline and a fixed quote.

ConfidentialISO 27001 certifiedNo spam, ever
30 minAverage response time
FixedQuote after scoping call
100%Client satisfaction

Trusted by teams at

Brand logoBistos logoCensys logoHeedkeep logoMyntra logoTaledge logoVelvu logoVerify logoTVS logoIOTECH logo

    Overview

    If some people cannot use it, they cannot buy from you.

    Many users rely on screen readers, a keyboard, larger text or voice control. When a button has no label or a form cannot be reached without a mouse, those users simply leave. We find these barriers, map each one to WCAG, and tell your team how to fix it. It also helps you answer customer and tender requirements.

    AUTOMATED SCAN ONLYXTREME INFOSEC ACCESSIBILITY TESTING
    Automated WCAG scan✓✓
    Manual screen reader testing✕✓
    Keyboard-only testing✕✓
    Zoom, contrast and text-size checksLimited✓
    Forms, labels and error messages✕✓
    Fix for every issue, mapped to WCAG✕✓

    Without accessibility testing, you risk:

    • ●Users who cannot sign up or buy
    • ●Forms that screen readers cannot read
    • ●Pages that need a mouse
    • ●Failing customer, tender or legal requirements
    • ●A smaller audience than you think
    Get an accessibility testing quote

    or call +91 98183 63944

    Testing types

    What we test for accessibility

    Seven areas, mapped to the WCAG principles: perceivable, operable, understandable and robust.

    01SR

    Screen reader testing

    What a blind or low-vision user hears.

    • NVDA, JAWS, VoiceOver and TalkBack
    • Reading order and page titles
    • Text alternatives for images
    • Button and link names

    Use it: For every key journey.

    02KEY

    Keyboard and focus

    Using everything without a mouse.

    • Tab order and visible focus
    • No keyboard traps
    • Menus, dialogs and carousels
    • Skip links

    Use it: For all interactive elements.

    03VIS

    Contrast, zoom and text

    Readable for low vision and colour blindness.

    • Colour contrast ratios (4.5:1 and 3:1)
    • Zoom to 200% and reflow at 400%
    • Text spacing and resizing
    • Colour never the only signal

    Use it: For every page and component.

    04FORM

    Forms, errors and inputs

    Everyone can complete and correct a form.

    • Labels, hints and required fields
    • Clear, specific error messages
    • Autocomplete and input purpose
    • Time limits and warnings

    Use it: For sign-up, checkout and applications.

    05MEDIA

    Images, video and audio

    Content that is not text still reaches everyone.

    • Alt text that describes the purpose
    • Captions and transcripts
    • Audio description where needed
    • No flashing or auto-playing media

    Use it: For media-rich sites.

    06STRUCT

    Structure, semantics and ARIA

    The code that assistive tools read.

    • Headings and landmarks
    • Correct HTML and ARIA use
    • Tables and lists
    • Page language and titles

    Use it: For custom components and single-page apps.

    07MOB

    Mobile accessibility

    Android and iOS apps with assistive tools.

    • TalkBack and VoiceOver
    • Touch-target size and spacing
    • Gestures with simple alternatives
    • Orientation and dynamic text

    Use it: For mobile apps and mobile websites.

    Tools

    Tools we work with

    Automated tools find part of the problems. Assistive technology finds the rest.

    Screen readers

    Test the way blind users do.

    NVDAJAWSVoiceOverTalkBackNarrator

    Automated scanners

    Fast checks for common WCAG failures.

    axe DevToolsWAVELighthousePa11yAccessibility Insights

    Contrast and visual

    Colours, text and zoom.

    Colour Contrast AnalyserWebAIM Contrast CheckerStarkBrowser zoom and reflow tests

    Voice and alternative input

    Beyond the mouse and keyboard.

    Voice Control (iOS and macOS)Voice Access (Android)Windows Voice AccessSwitch-style navigation tests

    Code and structure

    See what assistive tools see.

    Browser accessibility treeW3C HTML validatorARIA Authoring PracticesLandmarks and heading outline tools

    Mobile accessibility

    Check apps on real devices.

    Android Accessibility ScannerXcode Accessibility InspectorTalkBack and VoiceOver on devices
    Metrics

    What we measure

    Clear numbers against the WCAG standard.

    WCAGCriteria passedWCAG success criteria that pass, by level.
    LEVELIssues by levelLevel A and AA issues, by severity.
    KEYKeyboard task successKey journeys finished with the keyboard alone.
    SRScreen reader task successKey journeys finished with a screen reader.
    CONTRContrast failuresText and controls below the required ratio.
    ALTMissing text alternativesImages and controls with no useful label.
    FORMForm issuesFields, labels and errors that block users.
    FIXFix verification rateReported issues confirmed fixed on retest.
    Process

    How we test accessibility

    Six clear steps, from agreeing the standard to proving the fixes.

    01
    STEP 1

    Agree the standard and scope

    Choose the WCAG version and level, and the pages and journeys to cover.

    02
    STEP 2

    Run automated scans

    Scan every page to find the common failures quickly.

    03
    STEP 3

    Test by hand with assistive tools

    Go through each journey with screen readers, keyboard, zoom and voice control.

    04
    STEP 4

    Map every issue to WCAG

    Link each issue to its criterion, severity and the people it affects.

    05
    STEP 5

    Report with exact fixes

    Share the issues with screenshots, code and a clear fix.

    06
    STEP 6

    Retest and confirm

    Verify the fixes and update the conformance summary.

    Deliverables

    What you get at the end

    • Accessibility audit reportEvery issue mapped to its WCAG criterion.
    • Issue list by severityLevel A and AA issues, ranked by user impact.
    • Screenshots and code snippetsWhere the problem is, and the element affected.
    • Exact fix for each issueWritten for your developers and designers.
    • Journey test resultsKey journeys with screen reader and keyboard.
    • Quick-win listThe few fixes that help the most users.
    • Retest reportProof that each fix works.
    • Conformance summaryInput for your accessibility statement or customer questionnaire.
    Engagements

    Pick the engagement that fits

    Every engagement is scoped to your product and release plan. Tell us what you need and we’ll send a fixed quote.

    ESSENTIAL

    Key pages review

    Accessibility review of your main pages.

    • Page and journey list
    • Automated and manual checks
    • Audit report mapped to WCAG
    • Fix verification
    Get a quote
    MOST POPULAR

    Full site or app audit

    Review of all main journeys with assistive tools.

    • Everything in Essential
    • Screen reader and keyboard testing
    • Mobile app checks
    • Prioritised fix plan
    • Conformance summary
    Get a quote
    CONTINUOUS

    Every release

    Accessibility checks before each release.

    • Checks each release
    • New-page review
    • Re-testing
    • Dedicated QA lead
    Talk to us
    FAQ

    Questions before you start

    What is accessibility testing?−

    Checking that people with disabilities can use your website or app, for example with a screen reader, only a keyboard, larger text or voice control.

    Which standard do you test against?+

    WCAG 2.1 or 2.2, usually at level AA. If a customer or tender asks for another standard, such as GIGW, Section 508 or EN 301 549, we map the findings to it.

    Is an automated scan enough?+

    No. Scans catch only a part of the issues. Testing with a screen reader and a keyboard finds many more, such as confusing reading order and unreachable menus.

    Do you test mobile apps too?+

    Yes. We test Android and iOS apps with TalkBack and VoiceOver, and check touch targets, gestures and text scaling.

    Can you give us a certificate?+

    We give a detailed audit report and a conformance summary that you can use for customer or tender questionnaires. We do not issue a legal certificate of compliance.

    Can you fix the issues too?+

    We give exact fixes for developers and verify them. If you want help with the code changes, we can discuss it.

    Get started

    Make your product work for everyone.

    Book a free scoping call. You’ll get clear recommendations, a timeline and a fixed quote — whether you go ahead with us or not.

    +91 98183 63944

      Message Us

      Tell us what you need — we’ll reply with clear next steps and a fixed quote.

      Your details stay confidential and are used only to respond to your enquiry.

      Privacy Overview

      This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

      Chat on WhatsApp