BuildBLK — Accessibility Statement

Public page.

Effective Date: [DATE]

Last Reviewed: [DATE]

---

Our commitment

BuildBLK is built to be usable by everyone, including people who use screen readers, keyboard navigation, screen magnification, voice control, or other assistive technology.

We are committed to conforming to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

This is not a future goal. Accessibility requirements are built into our development standards and checked before anything ships, because a directory that exists to help people find businesses fails at its purpose if some people can't use it.

Conformance status

Status: [Fully conformant / Partially conformant] with WCAG 2.1 Level AA.

Partially conformant means some parts of the content do not fully conform. Where that is true, we list it below and give a target date.

Last evaluated: [DATE]

Evaluated by: [internal team / third-party auditor name]

Method: [automated testing (axe / Lighthouse) + manual keyboard and screen reader testing / third-party audit]

What we've done

• Semantic HTML structure with proper heading hierarchy and landmark regions
• All functionality operable by keyboard alone, with a visible focus indicator on every interactive element
• Text contrast of at least 4.5:1, and at least 3:1 for large text and interface components
• Meaningful alternative text on images; decorative images correctly hidden from assistive technology
• Form fields with persistent visible labels, and errors identified in text rather than by color alone
• Never using color as the only way to convey information
• Support for text resizing to 200% without loss of content or functionality
• Reflow to a single column at 320px width without horizontal scrolling
• Respect for the prefers-reduced-motion setting
• "Skip to main content" link at the top of every page
• Accessible names on all controls, including icon-only buttons
• Map content paired with an equivalent accessible list view

Known limitations

We list these honestly rather than claim perfection.

Tell us about a barrier

If any part of BuildBLK is difficult or impossible for you to use, we want to hear about it.

Email: [ACCESSIBILITY EMAIL]

Phone: [PHONE]

Mail: [LEGAL ENTITY NAME], [ADDRESS]

Please tell us the page, what you were trying to do, and what got in the way — plus the browser and assistive technology you're using, if you know.

Our commitment on response:

• We acknowledge within 2 business days
• We give you a substantive response, including a plan and timeline, within 10 business days
• We will provide the information or complete the transaction for you by another means — phone, email, or in whatever format works — while we fix the underlying issue
• Critical barriers that block core functionality are treated as priority-one defects

There is no cost, and you don't need to use any particular language or format. Just tell us what happened.

Assessment and maintenance

• Automated accessibility testing runs in our build pipeline; failures block deployment
• Manual keyboard and screen reader testing before each significant release
• Full review of this statement at least annually
• Accessibility is part of the definition of done for every feature — not a cleanup pass

Technical specifications

Accessibility relies on HTML, CSS, JavaScript, and WAI-ARIA, and on the compatibility of your browser and assistive technology.

Tested with:

• NVDA with Firefox and Chrome (Windows)
• VoiceOver with Safari (macOS and iOS)
• TalkBack with Chrome (Android)
• Keyboard-only navigation across all supported browsers
• Browser zoom to 200% and 400%

Formal complaints

If you are not satisfied with our response, you may contact:

U.S. Department of Justice, Civil Rights Division — ada.gov/file-a-complaint

California Department of Fair Employment and Housing (Civil Rights Department) — calcivilrights.ca.gov

We would much rather resolve it with you directly, and we will make a genuine effort to.