Our commitment
Eric Rounds LLC, doing business as Eric Rounds Agency, builds this site to be usable by everyone, including people who navigate by keyboard, use a screen reader, need larger text, rely on captions, or find motion difficult.
We build client sites the same way. It would be a strange thing to sell and not practice.
Updated July 2026.
The standard we build to
Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is the benchmark referenced by the Americans with Disabilities Act in practice, adopted by Section 508 for federal procurement, and used by the California Unruh Civil Rights Act cases that follow from ADA claims.
Conformance status: partially conformant. We choose that phrase deliberately. No honest operator of a real, changing website claims full conformance, and any vendor who offers you a compliance certificate is selling you something that does not exist. Parts of this site meet the standard fully. The known exceptions are listed below rather than omitted.
What we have actually done
- Automated audit. Every page tested with axe DevTools in July 2026. Every contrast failure, missing label, and ARIA error it surfaced was fixed rather than suppressed.
- Keyboard navigation. The whole site is operable without a mouse. The slide-out menu traps nothing, closes on Escape, and is removed from the tab order and the accessibility tree while shut.
- Visible focus. Focus indicators are present and meet the 2.2 focus appearance criteria. We have not disabled the browser’s outline anywhere.
- Reduced motion. Every animation on the site, including the hero transitions and the button effects, is skipped when your system requests reduced motion.
- Semantic structure. Real headings in order, real landmarks, real buttons for actions and real links for navigation. Screen reader users can navigate by heading and by region.
- Text alternatives. Images carry alternative text; decorative artwork is hidden from assistive technology rather than announced as noise.
- Resizing. Text scales to 200 percent, and the layout reflows to a 320 pixel width without horizontal scrolling.
- Self-hosted type. Fonts are served from this domain, so text renders even when a font request is blocked, rather than falling back to invisible text.
- The privacy notice. Consent banners are one of the most common accessibility failures on the web: focus traps, mouse-only dismissal, and unreadable contrast. Ours is a region landmark rather than a modal, does not steal focus when it appears, closes with the Escape key, and every control in it is a real button.
Known exceptions
Two, and both are deliberate.
Large decorative gold type. Display headlines and oversized numerals use the brand gold on a cream ground. At those sizes the pairing does not reach 4.5 to 1. It is retained under the large-text and decorative provisions, and every instance is duplicated by text that does meet the standard, so nothing is only available in gold. Small gold text, where it appears, uses a darker bronze that passes at 4.58 to 1.
Ghost numerals. The oversized section numbers behind some headings are decorative. They are hidden from assistive technology and are not the only way to know where you are.
If either of these blocks you in practice rather than in theory, tell us. A documented exception is still a barrier if it is a barrier to you.
Why there is no accessibility overlay
An earlier version of this site ran a third-party accessibility widget. We removed it.
Overlays do not fix an inaccessible site. They inject a toolbar over one, they frequently interfere with the screen reader the visitor already knows how to use, and they have become a documented trigger for litigation rather than a defense against it. The National Federation of the Blind and hundreds of accessibility practitioners have said so publicly.
We fixed the underlying markup instead. It is slower, it is the only thing that works, and it is what we would tell a client to do.
Where we are still working
Accessibility is not a project that finishes. Currently open:
- Reviewing older migrated articles for heading order and image alternative text carried over from the previous site.
- Manual screen reader passes on the interactive diagrams, beyond what automated tooling can assess.
- Captions and transcripts for any video we publish.
Third-party content
Some pages embed or link to content we do not control, including client websites and external tools. We cannot guarantee those meet the standard. When an embedded component fails and cannot be fixed, we will replace it or provide the same information another way.
Tell us when something does not work
This is the part that matters more than the rest of the page.
If any content here is difficult or impossible for you to use, write to eric@ericrounds.com with the page address and what happened. You do not need to know the technical name for the problem. “The menu will not open with my keyboard” is a perfect report.
What you can expect: a reply from a person within two business days, the information you were after supplied in a format that works for you, and a fix or a scheduled fix for the underlying problem. There is no form to fill in and no ticket queue.
If our response does not resolve it, say so directly and it will be escalated to Eric personally rather than closed.
Technical notes
This statement covers www.ericrounds.com. The site relies on HTML, CSS, and JavaScript, and is built to work with current versions of screen readers and browsers, including JAWS, NVDA, VoiceOver, and TalkBack. It degrades to readable, navigable content when JavaScript is unavailable.
Assessment approach: automated testing with axe DevTools, plus keyboard and manual review by the developer. No third-party certification has been sought, because none is recognized.