Website accessibility helps Albuquerque customers with disabilities find information, book services, and buy products online. For businesses covered by the Americans with Disabilities Act, accessible online services are also part of providing equal access. This article explains the legal framework, a practical website accessibility checklist, and a manageable approach to testing and repairs—without treating a scanner score as a compliance guarantee. (ada.gov)
What does ADA website compliance require for Albuquerque businesses?
ADA website compliance for Albuquerque businesses means addressing digital barriers that prevent people with disabilities from accessing the goods and services of covered public accommodations. The Department of Justice takes the position that ADA Title III applies to those offerings online. However, DOJ has not established a detailed website technical standard for private businesses under Title III; WCAG provides useful technical guidance rather than a universal legal certification. (ada.gov)
Federal obligations and technical standards
Title III covers businesses such as restaurants, retailers, hotels, and medical offices. A website deserves attention when customers use it to access those businesses’ services—not just when it processes payments. An appointment form, event registration page, or ordering interface can create an access barrier. (ada.gov)
WCAG, the Web Content Accessibility Guidelines, translates accessibility into testable requirements. WCAG 2.2 Level AA is a useful remediation target because it includes established accessibility requirements and newer provisions addressing issues such as obscured keyboard focus and accessible authentication. Level AA conformance includes applicable Level A requirements, too. (w3.org)
Keep government deadlines separate from private-business obligations. Following an April 20, 2026 extension, the Title II web rule requires public entities serving populations of 50,000 or more to meet WCAG 2.1 AA by April 26, 2027; smaller entities and special districts have until April 26, 2028. These are government compliance dates, not a grace period for private businesses. (ada.gov)
New Mexico and Albuquerque protections
The New Mexico Human Rights Act also prohibits discrimination in public accommodations. Albuquerque’s Human Rights Ordinance provides additional local protections, and the city offers businesses free technical assistance and training on public-accommodation responsibilities. These protections should not be described as a separate, verified WCAG certification requirement for every local website. (dws.state.nm.us)
Federal technology contracts can introduce Section 508 requirements, which incorporate WCAG 2.0 A and AA criteria. Check applicable contract terms rather than assuming Section 508 governs every business website. For questions about coverage, complaints, or specific legal exposure, consult qualified counsel; this article is general information, not legal advice. (section508.gov)
Is my website ADA compliant?
You cannot reliably answer “is my website ADA compliant?” from appearance, a plugin badge, or one automated scan. A meaningful assessment combines automated checks, manual inspection, and testing of customer tasks with assistive technology. It should identify the pages, processes, and accessibility criteria examined, along with unresolved barriers and testing limitations. (w3.org)
Start with the tasks that matter to your customers. For a hypothetical Albuquerque restaurant, that might mean reading the menu and completing a reservation. For a local service company, it could mean understanding service options, requesting an estimate, and receiving confirmation. Test the entire journey, including errors and pop-ups, rather than stopping at the homepage.
Automated tools reveal a starting point
Free tools can help you begin without purchasing a monitoring subscription:
- WAVE: Its online checker and browser extensions identify potential barriers and display information that supports human evaluation. Extensions are useful for dynamic or password-protected pages. (wave.webaim.org)
- axe DevTools: The free browser extension performs automated accessibility checks on individual pages. Paid features differ, so confirm what a proposed service includes. (deque.com)
- W3C evaluation resources: These explain assessment methods and help teams plan reviews beyond automated testing. (w3.org)
Save findings by page and component. If the same navigation issue appears throughout the site, record it as a shared defect rather than treating every instance as an unrelated repair. This gives your developer a clearer worklist.
Human testing checks the actual experience
Use the keyboard to move through navigation, forms, dialogs, and checkout. Look for lost focus, unreachable controls, or places where you cannot exit. Arrange screen-reader testing by someone who understands the technology, and involve people with disabilities where possible; inexperienced use alone can produce misleading conclusions. W3C recommends combining evaluation approaches and involving users. (w3.org)
An automated tool may detect missing alternative text, but human judgment is needed to decide whether an image description communicates the right information. Treat scan results as evidence to investigate, not a pass-or-fail legal verdict. (w3.org)
A website accessibility checklist focused on customer tasks
Use this website accessibility checklist to organize an initial review, not to declare complete WCAG conformance. Include representative layouts, mobile views, forms, documents, and third-party interfaces. A formal evaluation should cover all applicable criteria within its defined scope. (w3.org)
Readable content and meaningful structure
- Check text contrast. Most text needs a contrast ratio of at least 4.5:1; qualifying large text generally needs 3:1. Check actual colors, including text over photographs, rather than judging by eye. (w3.org)
- Write useful image alternatives. Describe the information or function an image conveys. Decorative images should generally have empty alternative text so screen readers can skip them; avoid repeating adjacent text unnecessarily. (w3.org)
- Use real headings and descriptive links. Mark headings structurally instead of simply enlarging text. Link wording should make its purpose understandable in context, helping readers navigate without guessing. (w3.org)
- Test enlargement and reflow. Check whether content remains readable and operable when enlarged and on narrow screens. Watch for clipped instructions, overlapping controls, and layouts that force unnecessary horizontal scrolling. (w3.org)
Operable controls, forms, and media
- Complete every action without a mouse. Menus, booking calendars, shopping carts, and dialogs need keyboard operation. A visible focus indicator should show the current location, and sticky banners must not entirely hide the focused component. (w3.org)
- Label fields clearly. Provide programmatically associated labels and instructions. Placeholder text alone is not a dependable substitute for a persistent label that remains available during entry. (w3.org)
- Make errors actionable. Identify which field needs correction and explain the problem in text. Preserve valid entries where possible so customers do not have to restart a long request. (w3.org)
- Review touch targets and login steps. WCAG 2.2 adds requirements addressing target size, with exceptions, and authentication barriers. Check cramped controls and whether login supports assistance such as password managers and pasting. (w3.org)
- Include media and downloads. Check applicable caption and audio-description requirements for video. Review menus, brochures, and forms supplied as documents rather than assuming the surrounding accessible webpage makes the file accessible. (w3.org)
For local businesses, prioritize the information customers need before visiting: hours, service descriptions, menus, booking instructions, and contact options. Include the actual reservation or payment provider in testing. An accessible landing page is not enough if the next required step blocks the customer.
How can a small business improve accessibility affordably?
A manageable approach is to assess the site, prioritize barriers by customer impact, repair shared components, and verify changes before expanding the work. Phasing helps organize resources, but it does not suspend legal obligations or establish that remaining barriers are acceptable. W3C recommends assigning responsibilities, setting budgets, prioritizing issues, and evaluating regularly. (w3.org)
Use this sequence to turn findings into a realistic work plan:
- Inventory the scope. List templates, forms, documents, videos, and outside services. Include content behind logins and components that appear only after interaction.
- Prioritize blocked tasks. Put barriers that stop booking, purchasing, or contacting the business ahead of minor presentation improvements. Record the affected task and proposed repair.
- Repair repeated components. Ask your developer to review shared navigation, buttons, form fields, and design styles. Verify changes across the layouts that use them.
- Separate editorial and development work. Content staff can improve descriptions and document organization; code-level interaction defects generally need technical attention.
- Retest the original problem. Record what changed, who checked it, and whether the full task now works. Do not close an issue merely because code was updated.
This workflow follows W3C’s broader approach of reviewing the environment, assigning tasks, integrating accessibility into production, and tracking progress. Choose milestones that reflect your actual website and resources rather than promising an unsupported completion date. (w3.org)
Ask your tax professional about the Disabled Access Credit and whether particular expenditures qualify. The IRS describes eligibility for certain small businesses and directs taxpayers to Form 8826 for eligible expenses. Its separate architectural and transportation barrier-removal deduction should not automatically be assumed to cover website work. (irs.gov)
Choosing ADA website services with clear deliverables
When comparing ADA website services, ask for a defined scope rather than a sweeping promise of “100% compliance.” A useful proposal should identify the target WCAG version and level, testing methods, sampled pages and processes, remediation responsibilities, and verification approach. W3C’s planning guidance emphasizes clear goals, responsibilities, budgets, and acceptance testing. (w3.org)
Request an example deliverable showing the affected component, the barrier, reproduction steps, and recommended repair. Clarify whether the price covers assessment only or also includes implementation and retesting. Ask who handles third-party booking systems, inaccessible documents, and defects introduced after launch.
Be cautious about services that rely entirely on an overlay, accessibility widget, or automated score. DOJ specifically notes that automated checkers and overlays require care and that a clean report does not necessarily establish accessibility. These tools should not replace evaluation of the underlying customer experience. (ada.gov)
Keep accessibility part of routine website work
Website accessibility in Albuquerque is an ongoing operational responsibility, not simply a launch-day project. New content, platform changes, and staff turnover can introduce barriers. Assign an owner, train publishers, and include accessibility checks in the same workflow used to approve other website changes. (w3.org)
Build a maintenance routine around concrete triggers:
- Before publishing, review headings, image alternatives, link text, and new documents.
- After theme, plugin, or checkout changes, retest affected customer tasks.
- During scheduled reviews, examine automated findings and manually check important interactions.
- When customers report a barrier, record the task, investigate, and communicate the next step.
These practices support W3C’s recommendations to monitor websites, incorporate user feedback, maintain staff capability, and track progress. Publish an accurate accessibility statement with contact options and known limitations rather than an unsupported claim that every feature is fully accessible. (w3.org)
Make the next customer task easier
Start with one important journey: finding information, booking an appointment, or completing a purchase. Assess it, document barriers, assign repairs, and retest the result. That gives your accessibility effort a concrete starting point while you build a broader, ongoing plan for equal access.
