Accessibility at BLKDG
We build ecommerce sites for a living, and accessibility is part of that work. This page explains how we approach it on our own site, the standard we hold ourselves to, what we know still needs attention, and how to tell us when something doesn't work for you.
Conformance status
We build blkdg.com against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. By our own assessment this site is partially conformant with that standard: most of it meets Level AA, and the parts we have not finished checking are listed below. No independent third party has audited this site, so we don’t claim full conformance. If that changes, this page will say so and give the date.
How we test
In September 2026 we audited every page on this site rather than a sample. The automated pass ran axe-core through Playwright across all 224 URLs in our sitemap at both desktop and phone widths, 450 page loads in total. Alongside it we ran five manual reviews covering keyboard and focus order, motion and media, forms, semantics and content structure, and color contrast.
We fixed what that audit found and re-scanned production on September 17, 2026. The automated scan now reports zero violations across all 224 URLs at both widths. Automated tools catch only part of what matters, which is why the manual reviews and the list below exist.
We also removed the accessibility overlay this site used to load. Overlays are widely rejected by disabled users, they don’t produce conformance, and they can interfere with the assistive technology someone already relies on. We fixed the markup instead.
What we’ve built in
Keyboard and screen reader use. A “Skip to content” link is the first stop on the page. After you follow a link, focus moves to the new page’s main content instead of leaving you in the header. Menus open and close with the keyboard, Escape closes them, and focus returns to the control you used. While the mobile menu is open, everything behind it is inert, and the close button sits inside the dialog so screen reader users can reach it.
Structure and text. Pages use real headings in order, so a screen reader’s outline matches what a sighted visitor sees. Images carry alt text that describes them, and decorative images are marked as decorative so they’re skipped rather than announced. Links inside body copy are underlined, not signalled by color alone.
Focus and contrast. Focus indicators are visible on every interactive element, with a ring color chosen per background so it stays visible, and no focus stop sits hidden behind the fixed header. Text and interface colors were checked by hand wherever automated tools can’t compute them, including over images and gradients.
Motion. If your device is set to reduce motion, animations, counters and the custom cursor turn off. Moving content has a visible pause control.
Forms. Every field has a visible label, required fields are marked in text and not by color alone, and when a submission fails, the error is announced and focus moves to the field that needs fixing.
Windows High Contrast. The site respects forced-colors mode, and the custom cursor is disabled there.
What we haven’t finished
Being specific here is more useful than claiming to be finished.
A screen reader spot check. Our September review was automated testing plus manual code and page review. A hands-on pass with VoiceOver, NVDA and TalkBack is still outstanding.
A flash and seizure check. We have no content we believe flashes, but we haven’t run a formal analysis on our video.
Some form field types. Consent, checkbox and radio fields in our forms haven’t been verified to the same standard as the text fields.
Older media and posts. We’re working through the alt text on every image in our library. Some older images still describe the file rather than the picture, and a few posts from before our 2026 rebuild carry hand-written markup.
Embedded third-party content. Our forms, bot protection and any embedded video come from outside providers. We choose vendors with accessibility in mind, but we don’t control their code.
PDFs and downloads. Documents we link to aren’t all tagged for screen readers.
Technical information
This site relies on HTML, CSS, JavaScript and WAI-ARIA. It’s built to work with current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, used with a keyboard alone or with assistive technology. Where JavaScript is unavailable, content and navigation still render, though some interactive pieces won’t.
Tell us about a barrier
If any part of this site keeps you from doing what you came to do, email info@blkdg.com with the page address and what happened. We aim to reply within three business days, and we’ll tell you what we plan to do about it and when. If our reply doesn’t resolve it, say so in the same thread and it goes to a partner here rather than back into the queue.
If you need information from a page in another format, ask and we’ll get it to you another way. Our office is at 4383 Tennyson St, Unit 1-B, Denver, CO 80212.
We treat accessibility as an obligation under the Americans with Disabilities Act, and WCAG 2.2 Level AA is the standard we hold ourselves to in meeting it.
About this statement
This statement was prepared on September 17, 2026, and reflects the audit and remediation completed on September 16 and 17, 2026. It was written by the team that maintains this site, and we review it when the site changes structurally and at least once a year.