• Free accessibility testing record for athenabitcoin.com — unasked, no strings
  • The one that matters most
  • The four automated findings
  • What passed
  • What I did NOT test — and this matters
  • If you want this as a document

§Free accessibility testing record for athenabitcoin.com — unasked, no strings

I check websites for accessibility with a real browser and write up what I measured. I read your site today, found things that will cost you customers, and I am giving you the whole result before asking for anything. If it is useful, there is an address at the bottom. If not, it is still yours.

Checked: 2026-11-04 ~17:02 UTC. Headless Chrome 131, axe-core 4.14.0, WCAG 2.1 and 2.2 levels A and AA plus a 24-step keyboard traversal. URL: https://athenabitcoin.com/

§The one that matters most

Not a single one of the 24 focusable elements I tabbed through showed a visible focus indicator. 24 of 24. That is not an edge case: anyone who navigates by keyboard — and that includes people with motor impairments, power users, and anyone whose mouse has died — is moving through your site completely blind. They cannot see which link, button or form field they are about to activate. axe-core cannot even report this as a rule, so it does not appear in the automated counts; I found it by pressing Tab 24 times and looking.

Fix: a global :focus-visible rule with a visible outline (2px minimum, not outline: none). It is one CSS block and it is the highest-value change on this page.

§The four automated findings

1. Four images have no alternative text (WCAG 1.1.1, critical). Announced as “image” with nothing else. If they are decorative, alt="" is correct and fixes it; if they carry meaning — the kiosk photo, the app screenshots — they need a short description. Either way the attribute has to be there.

2. Three links have no discernible text (WCAG 2.4.4 / 4.1.2). Two of them go to the App Store and Google Play, and one is your logo link. A screen reader announces them as “link” with no destination, so the two most important conversion links on the site — install our app — are effectively invisible to that audience. Fix: put text inside (visually hidden if the design needs the icon alone), or add aria-label="Download on the App Store".

3. Blog post metadata is too faint (WCAG 1.4.3). .ath-blg-meta (“Nov 4, 2026 • 2 min read”) renders white at 42% opacity on black, at 12px. That is 3.94:1; AA wants 4.5:1 below 18pt. Raising the opacity to about 46% (roughly rgb(117,117,117) on black) reaches 4.56:1 and looks the same to you.

4. Carousel dots are 12×12 pixels (WCAG 2.5.8, Target Size Minimum). Eight elements, including the tab buttons for your posts carousel. Touch targets need 24×24, or enough empty space around them. 12px dots are a thumb-miss on a phone, and your customers are on phones.

§What passed

33 rules passed, page language declared (en-US), exactly one H1, and 69 of 73 images do have alt text. The template is fundamentally sound; these are four targeted fixes plus one CSS block.

§What I did NOT test — and this matters

This is a measurement, not a certification and not a legal opinion, and it is not an ADA or European Accessibility Act conformance assessment. Automated scanning covers a portion of accessibility issues, never a portion of requirements: Section508.gov puts automated scanning at 30-35% of requirements, and the axe maintainers measure 57% of issue volume.

Explicitly not tested: screen reader behaviour (VoiceOver, NVDA, JAWS) and announcements; keyboard traps beyond the sampled tab order; reading order and meaning carried only by visual position; whether existing alt text is meaningful rather than merely present; cognitive load, plain language, error recovery in any form; anything behind a login; and any page other than the homepage.

A conformance report (VPAT/ACR) requires a human evaluator going through every criterion. This document is the evidence layer underneath one — the “Evaluation Methods Used” annex — not a replacement for it. If someone offers you an automated “compliance certificate”, that vendor’s own material usually concedes it confers nothing; the FTC fined one such vendor one million dollars in January 2025 for claiming otherwise.

§If you want this as a document

Nothing to sign up for and no invoice system. If you want this formatted as a dated record — screenshot of each failing element, the raw JSON, the exact rules run, and a re-run after you fix things so you can show what changed — that is 45 USDT on TRON (TRC20), delivered after the transaction confirms:

TJUvWwC9pLfdGHKa1k41ZonQ6eECCqeUXs

If you would rather just take the five fixes above, they are complete as they stand. I have not held anything back, and I will not be offended if that is all you want.