Website accessibility checklist for New York service businesses.
Audit a New York service-business website for accessibility across navigation, forms, media and third-party journeys with a practical testing and remediation plan.
Website design · Accessibility planningBy Orbital Content Team · Published October 25, 2026
AI-assisted research and drafting with editorial review. Legal and technical statements were checked against current U.S. Department of Justice, NYC Business and W3C Web Accessibility Initiative resources on October 25, 2026. The workflow, scorecards and business recommendations are Orbital analysis. Orbital did not audit a client website, test assistive technologies for a client, certify WCAG conformance, verify any legal defense, interview disabled users for this article or review a business's contracts, insurance, demand letter or legal obligations.
Website accessibility is not a one-click score. A useful program asks whether people with different disabilities can complete the real tasks a business offers online: understand a service, navigate without a mouse, submit a form, schedule an appointment, review an error, watch a video, pay, and ask for help.
For a New York service business, that means testing the whole customer journey—including third-party forms, booking and payment—not merely scanning the home page. This checklist turns that work into a bounded project with ownership, evidence, priorities and regression controls.
Know the legal and technical boundary
The U.S. Department of Justice says Title III of the Americans with Disabilities Act applies to businesses open to the public and that inaccessible website features can limit access to the goods, services and privileges those businesses offer online. DOJ's guidance also says it does not have a regulation setting detailed website standards for those private businesses; they have flexibility in how they meet general nondiscrimination and effective-communication requirements, while still needing to provide accessible online goods and services.
DOJ points to the Web Content Accessibility Guidelines as helpful technical guidance. WCAG is developed by W3C and organizes testable success criteria under four principles: content should be perceivable, operable, understandable and robust. WCAG 2.2 includes A, AA and AAA conformance levels, and W3C encourages use of its latest version.
Keep those statements distinct:
- Law and contracts determine a particular organization's obligations, deadlines, defenses and risk.
- WCAG provides a technical standard for evaluating accessible web content.
- A scan can identify some potential issues but cannot determine accessibility or legal compliance by itself.
- A remediation project improves a defined scope; it does not guarantee that every page, update, vendor or future release remains accessible.
The 2024 DOJ rule with a specific WCAG 2.1 Level AA standard applies to state and local governments under Title II. Do not copy its deadlines or exceptions into a private-business plan without qualified legal advice. For private businesses open to the public, use current Title III guidance, applicable New York requirements, contracts and facts reviewed by qualified counsel.
NYC Business tells local businesses to make their websites accessible, points them to the most current WCAG and notes that many NYC businesses have faced website-accessibility lawsuits. That is a reason to treat accessibility as a managed business responsibility—not proof of what law applies to a particular company or whether any specific website satisfies it.
If a demand letter or complaint has arrived, do not rely on this checklist. Preserve documents, note the response deadline, contact qualified counsel and insurers as appropriate, and follow their instructions. Remediation and legal response are related but different workstreams.
Inventory journeys and dependencies before testing
A page list is not enough. Build a journey inventory that shows what a visitor needs to accomplish and which systems make that possible.
| Journey | Views and components | Dependency | Owner | Evidence |
|---|---|---|---|---|
| Learn about a service | Service hub, detail page, navigation, accordion, comparison table. | CMS, theme, component library. | Content and web owner. | Heading structure, keyboard path, zoom and screen-reader review. |
| Choose a provider | About, team profiles, credentials, case material. | CMS, image gallery, video host. | Marketing owner. | Text alternatives, captions, transcripts and link purpose. |
| Request help | Contact form, validation, confirmation, error recovery. | Form provider, spam control, CRM. | Sales or intake owner. | Labels, instructions, errors, focus movement and submission test. |
| Schedule | Calendar, time selector, authentication, confirmation. | Scheduling platform. | Operations owner. | Keyboard completion, status messages, time-zone clarity and fallback. |
| Pay | Price, consent, hosted checkout, result page. | Payment processor. | Finance and web owners. | Focus, labels, error recovery, receipt and support route. |
| Get support | Phone, email, chat, FAQ, document downloads. | Chat, phone, help desk, PDF library. | Service owner. | Multiple contact methods, document review and escalation test. |
Add language variants, mobile layouts, logged-in areas, PDFs, maps, embedded reviews, popups, cookie controls and campaign landing pages. Record which party can change each component. A defect in a vendor widget is still part of the visitor's experience even when the business cannot fix the vendor's code directly.
Reuse the system map from Orbital's tech stack audit checklist. It helps expose duplicate forms, old widgets, unclear owners and vendors that sit between a visitor and the requested service.
Define the evaluation scope and evidence
W3C's WCAG Evaluation Methodology uses five broad steps: define the scope, explore the product, select a representative sample, evaluate that sample and report findings. Apply that discipline even when the first project is smaller than a formal conformance evaluation.
Write a one-page scope before testing:
- the domain, subdomains, apps and third-party services included;
- the target standard and level used as technical acceptance criteria;
- the devices, browsers and assistive technologies in scope;
- the key customer journeys and business-critical views;
- templates, components and content types to sample;
- authenticated, personalized, error and empty states;
- languages, documents, audio and video included;
- testing methods and evaluator expertise;
- known exclusions and why they are excluded;
- report format, severity definitions and evidence required; and
- who may make a conformance claim or legal conclusion.
For a large site, select both structured and random samples. Structured samples cover the home page, each template, each critical journey, shared navigation, forms, interactive components and known high-risk content. Random samples help reveal issues outside the pages the team expects to be important.
Do not call a partial sample a whole-site audit. The report should state exactly what was tested, when, by whom, with which methods and what was not tested. W3C notes that applying WCAG-EM successfully requires knowledge of WCAG, accessible design, assistive technologies and how people with different disabilities use digital products.
Run a first screen without mistaking it for an audit
W3C's Easy Checks provide a practical first review. They explicitly are not a complete accessibility evaluation: a page can appear to pass and still contain significant barriers.
| Check | What to look for | Evidence to save |
|---|---|---|
| Page title | A unique title that identifies the page and website. | Rendered title and template source. |
| Image alternatives | Meaningful images have useful text alternatives; decorative images do not add noise. | Image purpose, accessible name and screen-reader output. |
| Headings | Headings describe sections and reflect a logical content structure. | Heading outline and affected component. |
| Contrast and color | Text and controls remain distinguishable; color is not the only cue. | Measured value, state and screenshot. |
| Resize and reflow | Content remains readable and functional when text or viewport changes. | Viewport, zoom or text setting and any lost content. |
| Keyboard and focus | Every action works without a mouse, focus is visible and order is logical. | Keyboard path, trapped focus and obscured controls. |
| Forms | Fields have labels, instructions and programmatically conveyed errors. | Accessible name, error message and recovery path. |
| Movement | Moving or blinking content has appropriate controls and avoids harmful flashing. | Component, timing and available pause or stop control. |
| Audio and video | Appropriate captions, transcripts or descriptions support the content. | Media URL, alternative provided and review notes. |
| Structure | Landmarks, reading order and labels communicate relationships. | Accessibility tree and screen-reader sequence. |
An automated tool can accelerate repeatable checks and catch regressions. W3C warns that tools cannot automatically check every accessibility aspect, require human judgment and can return false or misleading results. Record the tool, version, rules, viewport, pages and date; retain the raw findings; then verify each issue manually before assigning remediation.
Test real tasks manually
Component checks can pass while a journey fails. Ask a knowledgeable evaluator to complete realistic tasks using keyboard-only navigation and appropriate assistive technologies.
For each task, record:
- Starting state. Page, viewport, browser, technology, account status and test data.
- Goal. The exact outcome, such as submitting an inquiry or choosing an appointment.
- Expected route. The steps and feedback the business intends.
- Observed route. Focus order, labels announced, errors, status messages and workarounds.
- Barrier. What prevents, delays or confuses completion.
- Impact. Which user and business outcome is affected.
- Evidence. URL, component, code reference, screenshot or recording, without unnecessary personal data.
- Owner and retest. Who fixes it, release target and result after repair.
Include unhappy paths: missing required fields, invalid formats, expired sessions, failed payments, unavailable appointment slots, duplicate submissions and network interruptions. Ensure an error is conveyed in text and programmatically, focus moves to a useful location, entered data is not needlessly lost, and a visitor can recover without starting over.
Test persistent banners, chat launchers and sticky controls against keyboard focus. WCAG 2.2 added criteria addressing focus not being obscured, dragging alternatives, minimum target size, consistent help, redundant entry and accessible authentication. These are especially relevant to modern service sites with overlays, booking widgets and repeated forms.
Where the budget and scope permit, include disabled users in evaluation. W3C says this can identify usability issues that conformance evaluation alone may miss, while also warning that a few participants cannot represent every disability. Combine user evaluation with standards-based review, state the participant and task scope, use informed consent and compensate people appropriately.
Control third-party forms, booking, chat and checkout
A service business often does not own the code for its most consequential interactions. Maintain a dependency register:
| Field | Question |
|---|---|
| Business purpose | Which customer task requires this service? |
| Vendor and version | Which product, plan, embed mode and release is actually used? |
| Accessibility evidence | What current conformance report, documentation or tested behavior supports the claim? |
| Configured experience | Do branding, fields, scripts or integrations change the tested result? |
| Issue route | Who accepts defects, what evidence is required and what response target applies? |
| Fallback | Can a visitor complete the same task through an accessible alternative without extra cost or delay? |
| Monitoring | How will the business detect a vendor release or configuration change? |
| Exit | Can the journey move to another provider or a first-party form if barriers persist? |
Do not accept “the vendor says it is compliant” as complete evidence. Test the business's configured flow. A vendor statement may cover a different product, version, theme, feature set or responsibility. Put accessibility evidence, defect response and remediation responsibilities into procurement and renewal decisions.
Map form, scheduling and payment dependencies with the lead intake workflow checklist and conversion tracking checklist. Accessibility fixes should preserve the intended handoff and measurement while eliminating barriers.
Prioritize by blocked outcomes, not raw issue count
A scan may produce hundreds of instances of one template defect while a single unlabeled payment field blocks a critical task. Deduplicate findings by root cause and prioritize with a consistent model.
| Factor | Questions |
|---|---|
| User impact | Does the issue block, materially delay or merely inconvenience completion? |
| Journey criticality | Does it affect emergency contact, service access, booking, payment or support? |
| Reach | Is it in shared navigation, a common template or one rarely visited page? |
| Frequency | Does every visitor encounter it or only a specific state? |
| Workaround | Is there an equally effective accessible route, clearly presented? |
| Release risk | Could the fix disrupt another journey, integration or content pattern? |
| Evidence | Is the barrier manually confirmed and tied to a reproducible case? |
Suggested operating bands:
- Immediate: a visitor cannot complete a critical task, access essential information, recover from an error or contact the business.
- High: a common journey is substantially harder, shared components spread the issue or no reasonable alternative exists.
- Planned: the issue affects a narrower context but still fails the technical acceptance criteria.
- Investigate: automated or user-reported evidence needs knowledgeable confirmation before a code change.
Fix shared design-system and template defects before one-off pages when that safely removes more barriers. Retest the exact issue, nearby interactions and representative pages that reuse the component. Record the release and evidence; do not close a finding because code changed.
Put accessibility into design and development acceptance
A website proposal should define accessibility deliverables before work starts. Add the following to the statement of work:
- target WCAG version and level as technical acceptance criteria;
- included domains, templates, components, third-party tools, documents and media;
- design reviews for contrast, focus, states, errors, motion and responsive layouts;
- semantic implementation and keyboard acceptance for every interactive component;
- content responsibilities for headings, links, images, documents, captions and transcripts;
- automated checks in development plus manual testing of key journeys;
- named browsers, devices and assistive technologies;
- representative sample and user-evaluation expectations;
- defect severity, remediation timelines, retest evidence and warranty period;
- handoff documentation, training and regression controls;
- third-party limitations, escalation and fallback responsibilities; and
- who may make technical conformance or legal statements.
Reject vague promises such as “ADA compliant plugin included,” “100 accessibility score” or “automated overlay guarantees compliance.” Ask the provider to show the scope, methods, manual evidence, known limitations and the exact experience tested.
Use Orbital's NYC website design proposal checklist to compare ownership, acceptance, change control and post-launch support alongside accessibility requirements. If a redesign or platform change is involved, pair it with the website redesign SEO migration checklist so accessibility fixes do not accidentally remove valuable content or break discovery.
Create a feedback, content and monitoring loop
DOJ includes a way to report accessibility issues among the practices businesses should consider. Provide a visible contact method and make the reporting path accessible itself. Ask only for information needed to investigate: affected page, task, barrier, browser or assistive technology if the person wishes to share it, and preferred contact method.
An accessibility statement can identify the scope and standard the business is working toward, known limitations, recent review date and contact route. It should be accurate and maintained. Do not claim full conformance, certification or a legal safe harbor unless qualified people have evidence and authority for that statement.
Establish an operating rhythm:
- check critical templates and journeys before every release;
- review new images, video, documents and forms before publication;
- run automated checks as a regression signal, not a final verdict;
- sample live pages after CMS, theme and vendor updates;
- triage user reports with a named owner and response target;
- retest closed defects and watch for recurrence;
- review third-party evidence at renewal and after material releases;
- train content editors and developers on their assigned controls; and
- repeat a broader evaluation on a defined schedule or after major redesigns.
W3C's planning guidance treats accessibility as an ongoing capability: set objectives, assign responsibilities and resources, evaluate early and regularly, track progress, monitor changes and incorporate user feedback. This is more durable than a one-time cleanup.
Include accessibility tasks in the operating plan from the website maintenance checklist. The maintenance owner should know which checks run automatically, which require human review and when a specialist is needed.
A bounded 30-day action plan
- Days 1–5 — map and scope. Name the accountable owner. Inventory domains, templates, critical journeys, documents, media and third-party services. Choose technical acceptance criteria with qualified input. Document legal and contractual questions separately for counsel.
- Days 6–10 — screen and remove obvious barriers. Run representative automated checks and W3C-style initial checks. Manually confirm findings. Repair shared issues that can be fixed safely, such as missing labels, keyboard traps, invisible focus, unclear errors or unusable contrast.
- Days 11–18 — evaluate tasks. Test service discovery, contact, scheduling, payment and support with keyboard and relevant assistive technologies. Include error states, mobile layouts and third-party transitions. Add user evaluation if the defined scope supports it.
- Days 19–24 — remediate and retest. Group issues by root cause, prioritize blocked outcomes, assign owners and release fixes. Retest the original case and related components. Escalate vendor defects and confirm a practical fallback.
- Days 25–30 — operationalize. Publish an accurate feedback route, finalize the issue register, place checks in content and release workflows, train owners and schedule the next review. Give leadership a report that states scope, evidence, remaining barriers and decisions—not only a score.
Use a compact dashboard:
- critical journeys tested and successfully completed;
- confirmed barriers by severity and root cause;
- critical barriers open, owner and age;
- third-party barriers with escalation status and fallback;
- defects reopened after retest;
- user reports received, acknowledged and resolved;
- templates changed since the last representative review; and
- staff training and vendor evidence due for renewal.
Do not turn issue count into a compliance percentage. Counts vary by scanner, rules, page sample and duplicate handling. Report the methods and scope next to every metric.
Orbital's business take
The strongest accessibility program starts with customer outcomes and evidence. A business should know whether someone can learn, contact, schedule, pay and get support—not simply whether a tool produced a green badge.
Accessibility also improves the discipline of a website operation. Clear labels, understandable errors, keyboard-compatible controls, stable focus, usable media and documented ownership reduce friction for many visitors. But that broad benefit should not erase the specific goal: people with disabilities must be able to use the website's information and functions.
For a New York service business, begin with the journeys closest to access and revenue, fix verified shared barriers, and create release controls that prevent recurrence. Bring in qualified accessibility and legal professionals when the evaluation, conformance statement, contract, complaint or business risk requires expertise beyond ordinary website work.
Explore Orbital's website design services, business consulting, tech stack consulting, connected-business planning, New York City services and service-business planning. A 60-minute consultation can turn the journey inventory into a scoped website-improvement brief; accessibility evaluation, legal advice, specialist testing, user research, third-party remediation, development and ongoing monitoring are separately scoped.
Sources and editorial limits
Primary sources were checked October 25, 2026. DOJ's March 18, 2022 Title III guidance says businesses open to the public must provide accessible online goods and services, have flexibility in how they meet general requirements and can use WCAG as helpful technical guidance; it also says DOJ does not have a regulation setting detailed website standards for those private businesses. NYC Business recommends current WCAG and accessibility review to local businesses. W3C defines the WCAG technical standard and explains that initial checks and automated tools cannot determine accessibility by themselves; knowledgeable human evaluation, a representative scope and, where appropriate, input from disabled users add essential evidence. Laws, standards, guidance and individual business facts can change. Orbital did not determine which laws apply to a reader, audit a website, certify conformance, reproduce a specialist evaluation, inspect a demand letter, review insurance or provide legal advice. This guide does not guarantee accessibility, compliance, lawsuit prevention, rankings, leads, conversions or business results.
Primary source links
- U.S. Department of Justice: Guidance on Web Accessibility and the ADA
- NYC Business: Accessibility Compliance
- W3C WAI: WCAG 2 Overview
- W3C WAI: Easy Checks — A First Review of Web Accessibility
- W3C WAI: WCAG Evaluation Methodology
- W3C WAI: Selecting Web Accessibility Evaluation Tools
- W3C WAI: Involving Users in Evaluating Web Accessibility
- W3C WAI: Planning and Managing Web Accessibility