THE NIGHT WOLFS.

FIELD GUIDE / WEBSITE UX & ACCESSIBILITY

Website accessibility starts with real tasks.

A business website should let people understand its services and complete useful tasks in more than one way. This practical guide helps Mumbai businesses review keyboard access, focus, contrast, mobile layouts, images and enquiry forms using selected WCAG 2.2 guidance. It is a starting checklist, not a conformance audit, certification or legal opinion.

Written by
The Night Wolfs Editorial Team
Published
Updated
Length
9 min read
STRATEGY / PRACTICAL READING / SOURCESREAD THE FIELD GUIDE

What matters most.

Start by testing a real visitor task, such as finding a service and sending an enquiry. Use WCAG 2.2 as a technical reference, then check keyboard operation, visible focus, text contrast, mobile reflow, image alternatives and form labels. Automated scans can find some issues, but manual checks and feedback from people are also important. Fix barriers that block essential tasks first; do not promise accessibility or search rankings based on a single scan.

Key takeaways.

  1. KEY POINT 01Test real tasks such as finding a service, reading its details and completing an enquiry.
  2. KEY POINT 02Make every important control usable with a keyboard and keep keyboard focus visible.
  3. KEY POINT 03WCAG 2.2 AA specifies 4.5:1 contrast for normal text and 3:1 for large text, with defined exceptions.
  4. KEY POINT 04Check that vertical content reflows at a 320 CSS-pixel viewport without unnecessary horizontal scrolling.
  5. KEY POINT 05Give informative images useful text alternatives; mark purely decorative images appropriately.
  6. KEY POINT 06Use visible form labels, clear instructions and specific error messages.
  7. KEY POINT 07Automated scans help, but they do not replace manual review or user feedback.
  8. KEY POINT 08Prioritize barriers that prevent visitors from understanding or completing a key task.

Start with a real visitor task

A checklist is easier to use when it is tied to a real goal. Choose one task a visitor should be able to complete: find a service, understand who it is for, review the next step and send an enquiry. Follow that path on a phone and a desktop rather than checking isolated controls with no context.

People may navigate with a keyboard, screen reader, voice input, magnification, touch or a combination of tools. Temporary situations matter too: someone may be holding a phone in one hand, working in bright sunlight, using a slow connection or reading with enlarged text. A single mouse-and-desktop check will not reveal every barrier.

  • Can a visitor find the main navigation and understand the current page?
  • Can they move through links and controls without a mouse?
  • Can they read and use the page when text is enlarged?
  • Can they identify and correct a form error without losing entered information?

Use WCAG 2.2 as a technical reference

The W3C Web Content Accessibility Guidelines (WCAG) provide testable criteria for making web content more accessible. WCAG 2.2 is the current W3C Recommendation referenced in this guide. It organizes guidance around content that is perceivable, operable, understandable and robust.

The checks below cover practical issues found on business sites, but they are not a complete WCAG evaluation. A page can look polished and still have inaccessible controls; an automated score is not proof that a site conforms. If you need a formal conformance assessment or need to understand legal obligations, arrange a qualified review for the relevant site and context.

Make navigation work without a mouse

Use Tab and Shift+Tab to move through links, buttons, form fields and other controls. Each important action should be possible from a keyboard unless it inherently depends on movement, and the focus indicator should make it clear where the visitor is. A keyboard user should not become trapped inside a menu or dialog.

Test the actual site header, mobile menu, cookie choices, chat launcher and enquiry form. Pay attention to controls that appear after a click: they should receive sensible focus, have an understandable name and let visitors move on or close them. Sticky banners and floating buttons should not hide the item that currently has focus.

  • Tab through the page from the beginning and watch for a clear focus style.
  • Use Enter or Space on controls according to their expected behavior.
  • Check that menus and dialogs open, close and return focus in a predictable way.
  • Avoid removing the browser focus outline unless a clear replacement is provided.

Make text and information easy to perceive

WCAG 2.2 Level AA sets a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, subject to defined exceptions. Check the actual text against its background, including small labels, placeholder text, captions and text placed over images. A brand colour can still be used, but it may need a darker or lighter pairing to keep the wording readable.

Do not use colour alone to communicate status. Pair it with text, an icon or another cue—for example, say which form field needs attention instead of only outlining it in red. Use descriptive headings, meaningful link text and a sensible reading order so visitors can scan and understand the page.

Review pointPractical check
Text contrastUse a contrast checker for text/background pairs; WCAG 2.2 AA uses 4.5:1 for normal text and 3:1 for large text, with defined exceptions.
Status and errorsExplain the status in text and identify the affected field; do not rely on colour alone.
Page structureUse descriptive headings and links so the page makes sense when skimmed or read out of context.
Text resizingEnlarge text and confirm that important content and controls remain available.

Check reflow and touch targets on mobile

WCAG 2.2 includes a Reflow criterion for vertical content at a width equivalent to 320 CSS pixels. The goal is to let people read and use the content without scrolling in two directions, except where a two-dimensional layout is essential. This matters when a visitor zooms in or views the site in a narrow window.

Check navigation, cards, comparison tables, chat controls and cookie banners at a narrow width and enlarged text size. A fixed-width table or floating widget should not cover the main task. WCAG 2.2 Level AA also sets a 24 by 24 CSS-pixel minimum for pointer targets, with defined exceptions. Where practical, make touch targets larger and leave enough space between neighboring controls.

  • Test a narrow viewport and browser zoom; look for clipped text or page-level horizontal scrolling.
  • Confirm that fixed headers, chat launchers and consent dialogs do not cover important content.
  • Make buttons and links easy to distinguish and activate without accidentally selecting a neighbor.
  • Check both portrait and landscape layouts when the task or content needs them.

Give images, icons and motion a clear purpose

Alternative text depends on what an image does in its context. A useful photo or diagram needs a concise description of the information a visitor would otherwise miss. A decorative flourish can use an empty text alternative so it does not add noise. When an image is a link or button, describe its purpose or destination rather than only its appearance.

Avoid putting essential service details, prices or instructions only inside an image. For video, provide captions when speech carries information and make any important visual information available in another way. Keep animation restrained, do not use flashing effects, and respect reduced-motion preferences where possible.

  • Write alt text for informative images; use an empty alternative for decoration.
  • Give icon-only buttons an accessible name that explains the action.
  • Keep important copy available as text instead of embedding it only in a graphic.
  • Let visitors pause, stop or avoid non-essential movement when the experience calls for it.

Make enquiry forms clear before and after submission

Give each input a visible label that stays available while the visitor fills it in. Add short instructions where a format or choice may not be obvious. Tell people which fields are required before they submit, and do not use placeholder text as the only label.

When a form has an error, identify the field and explain how to fix it in text. Preserve valid answers so the visitor does not have to start again. After a successful submission, provide a clear confirmation. These checks help everyone, including visitors using screen readers, keyboard navigation or magnification.

Ask only for information needed to respond. A shorter form is not automatically accessible, but each extra field adds effort and should have a clear purpose. Test the form on a phone, with a keyboard and with both valid and invalid answers.

Run a short, repeatable accessibility review

Automated tools can point out issues such as some missing names or low-contrast text, but they cannot understand every page intention or complete every user task. W3C guidance recommends combining evaluation tools with human review. Use a repeatable checklist and, where possible, ask people with different access needs to test the journeys that matter.

ACCESSIBILITY / REAL TASKSOne task, more than one way throughHelp visitors navigate, understand the page and complete an important action.
One task, more than one way throughHelp visitors navigate, understand the page and complete an important action. Supporting concepts: Navigate, Keyboard and touch; Understand, Readable content; Complete, Clear form states.THE NEEDNavigateKeyboard and touchUnderstandReadable contentCompleteClear form states
  • Choose one visitor task, such as finding a service and sending an enquiry.
  • Complete it with a keyboard only, then repeat it at a narrow viewport and enlarged text.
  • Check focus order, contrast, image descriptions, labels and the error and success messages.
  • Use an automated accessibility checker to catch additional detectable issues, then review each result in context.
  • Record the page, barrier, impact and fix so the team can check the result later.

Fix barriers by the task they block

Prioritize issues that prevent visitors from understanding the offer, reaching the right page or contacting the business. A missing label on the main enquiry form is usually more urgent than a decorative detail on a low-traffic page. Track fixes with a page, issue, owner and retest result so improvements do not disappear during the next redesign.

PriorityExampleFirst action
Blocks a key taskA form cannot be completed by keyboard or its fields have no usable labels.Fix the control and retest the entire enquiry flow.
Makes information hard to understandLow-contrast text, unclear link names or an image carrying essential copy.Improve the text, contrast or alternative description.
Creates friction on some screensA fixed banner covers a form button at narrow width or enlarged text.Adjust the layout and retest the affected viewport.

A site review is ongoing work. Recheck important templates after design or content changes, and verify that fixes still work on the live page.

Website accessibility checklist

Before you call a page ready, review the main task from start to finish:

  • The purpose of the page and its main action are clear.
  • Links, menus, dialogs and forms work with a keyboard and show visible focus.
  • Text contrast, headings and link names make information easier to understand.
  • The layout remains usable at a narrow width and enlarged text size.
  • Informative images have useful text alternatives and decorative images do not add noise.
  • Forms have persistent labels, helpful instructions and recoverable errors.
  • Non-essential animation does not block or distract from the task.
  • A manual task test has been completed in addition to any automated scan.

Questions worth
asking early.

Clear answers about accessible websites before you choose your next step.

What is a practical first step toward website accessibility?

Choose an important visitor task, such as finding a service and sending an enquiry. Try it with a keyboard, at a narrow viewport and with enlarged text, then record any barrier that blocks or confuses the task.

What text contrast does WCAG 2.2 AA require?

The minimum contrast ratio is 4.5:1 for normal text and 3:1 for large text, with defined exceptions. Check the W3C criterion for details and test the actual foreground and background colors.

Can an automated accessibility scan certify a website?

No. Automated tools can detect some issues, but they cannot judge every context or complete every user task. Combine them with manual checks and, where possible, feedback from people with different access needs.

Does making a website accessible guarantee higher Google rankings?

No ranking result is guaranteed. Accessibility helps more people use a site, but it is not a substitute for useful content, technical SEO, relevant pages or a good service offer.

Does every image need descriptive alt text?

No. Informative images need a text alternative that communicates their useful content. Decorative images can use an empty alternative, while linked or actionable images should explain their purpose.

Is this checklist proof that a site conforms to WCAG?

No. It covers selected practical checks and does not establish conformance, certification or legal compliance. A formal review needs to consider the relevant criteria, pages, content and user journeys.

SOURCES & FURTHER READING

  1. W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
  2. W3C WAI: Understanding Keyboard accessibility (opens in a new tab)
  3. W3C WAI: Understanding minimum text contrast (opens in a new tab)
  4. W3C WAI: Understanding reflow (opens in a new tab)
  5. W3C WAI: Understanding minimum target size (opens in a new tab)
  6. W3C WAI: Images tutorial (opens in a new tab)
  7. W3C WAI: Labeling controls in forms (opens in a new tab)
  8. W3C WAI: Evaluating web accessibility (opens in a new tab)

THE NIGHT WOLFS / NALLASOPARA (E), MUMBAI REGION

Bring us the brief. We will show our reasoning.

Tell us the goal you are working toward. We will explain what we would do first, what it depends on and how progress would be measured.

Start the conversation