Accessibility Statement
Statement prepared and last reviewed: . Target: WCAG 2.2 Level AA, partial conformance.
thatdeveloperguy.com is committed to making this website usable by as many people as possible, including people with disabilities. This statement describes how accessibility is approached, where the site currently falls short, and how to reach the operator if you encounter a barrier.
Our Commitment
We build websites for a living, so this site is held to the same standard we recommend to clients: every visitor — regardless of vision, hearing, motor ability, cognitive style, or assistive technology — should be able to read what we publish, contact us, and evaluate whether to hire us. Accessibility is treated as a baseline quality requirement on this site, not an optional add-on, and it is revisited whenever the site changes.
Conformance Status
The Web Content Accessibility Guidelines (WCAG) define how to make web content more accessible to people with disabilities. The conformance target for thatdeveloperguy.com is WCAG 2.2 Level AA.
thatdeveloperguy.com is in partial conformance with WCAG 2.2 Level AA. Partial conformance means that most of the site meets the standard, but some content or functionality does not yet fully conform. The known gaps are listed under “Known limitations” below. The site does not claim conformance to Level AAA and has not yet been audited by an independent third party.
Compatibility with Browsers and Assistive Technology
The site is designed and tested to be compatible with current versions of the following browsers and assistive technologies:
- Chrome, Firefox, Safari, and Edge on desktop, latest two major versions
- Safari and Chrome on iOS and Android, latest two major versions
- VoiceOver on macOS and iOS
- NVDA on Windows with Firefox or Chrome
- TalkBack on Android
- Browser zoom up to 400% and operating-system text-size settings
- Keyboard-only navigation, no pointing device required
- Reduced-motion and high-contrast operating-system preferences
The site is not specifically tested with Internet Explorer, with JAWS earlier than version 2023, with Dragon NaturallySpeaking, or with browser versions more than two releases behind current. It may still work in those environments but compatibility cannot be guaranteed.
Technical Specifications
Accessibility on thatdeveloperguy.com relies on the following technologies working in combination with the browser and any assistive technology installed on your device:
- HTML5 with semantic landmarks, headings, lists, and native form controls
- CSS, authored using a utility-first approach
- WAI-ARIA, used only where native HTML semantics are insufficient
- JavaScript, used minimally and progressively — core content and contact paths work with JavaScript disabled
- JSON-LD structured data for machine-readable metadata
- SVG and raster images with text alternatives where they convey meaning
The site is hand-coded and served as static HTML from nginx. There is no content management system, no client-side rendering framework, and no required login.
Known Limitations
Despite our efforts, the following limitations are known. They are being actively worked on, and reports of any limitations not listed here are welcome.
- Color contrast on accent and secondary text. The site uses a dark background with a gold accent. Some accent links, muted captions, and decorative subtitles may not yet meet the 4.5:1 contrast ratio required for normal text at AA. Primary body text and primary navigation meet the ratio.
- Focus indicators. Visible keyboard focus is provided on all interactive elements, but on a small number of components the indicator may not yet meet the stronger appearance and non-obscuring requirements introduced in WCAG 2.2 (success criteria 2.4.11 and 2.4.13).
- Image alternative text. Meaningful images carry alt text and decorative images are marked empty, but some alt text is currently more generic than it should be and is being rewritten to describe purpose rather than appearance.
- Third-party embeds. Where the site embeds external content — for example calendar booking widgets, video players, or analytics dashboards — those embeds are controlled by their providers and may not fully meet WCAG 2.2 AA. Where an embed creates a barrier, an alternative way to accomplish the same task is provided, such as an email address or phone number alongside any booking widget.
- PDFs and other documents. Some older PDFs linked from this site were produced before the current accessibility process and may not be fully tagged for screen readers. If you need the content of a specific document in an accessible format, contact us and it will be provided.
- Animation and motion. Decorative motion respects the
prefers-reduced-motionoperating-system setting. A small number of subtle transitions may still play; if any cause discomfort, please report them and they will be removed.
Assessment Approach
The accessibility of thatdeveloperguy.com was evaluated by self-assessment. The site has not yet been audited by an independent third party. Self-assessment uses a combination of:
- Manual keyboard-only navigation testing
- Manual screen-reader testing with VoiceOver and NVDA
- Automated checks using axe DevTools, Lighthouse, and the WAVE evaluation tool
- Color-contrast verification using the WebAIM Contrast Checker and APCA tooling
- Testing at 200% and 400% browser zoom and with operating-system text-size scaling
- Review against the WCAG 2.2 success criteria checklist
Self-assessment is not a substitute for a formal audit by certified accessibility professionals, and that limitation is acknowledged here.
Feedback and Contact
If you encounter a barrier on this site, need information in a different format, or want to report something we got wrong, please contact us:
- Email: accessibility@thatdeveloperguy.com
- Subject line that helps triage: “Accessibility — [page or issue]”
Acknowledgement of accessibility feedback is sent within two business days and a substantive plan or fix is sent within ten business days. If a fix will take longer, the reason and an estimated timeline are provided. Where a barrier cannot reasonably be removed, an equivalent alternative is offered — for example, sending information by email, taking a phone call, or meeting in person.
Formal Complaints
Please contact us directly first so we can fix the problem. If you are not satisfied with the response, you may also file a formal complaint.
United States. Title III of the Americans with Disabilities Act (ADA) and, for federal-facing services, Section 508 of the Rehabilitation Act apply to web accessibility. Complaints can be filed with the U.S. Department of Justice, Civil Rights Division, Disability Rights Section, at ada.gov/file-a-complaint.
European Union. Visitors in the EU are covered by the European Accessibility Act (Directive 2019/882), which applies to relevant private-sector services from 28 June 2025. EU residents who believe this site is not meeting its obligations may contact the accessibility enforcement body in their member state. A list is maintained by the European Commission.
United Kingdom. The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations in the UK.
Preparation and Review
- This statement was prepared on April 30, 2026.
- It was last reviewed on April 30, 2026.
- It was prepared in line with the W3C Web Accessibility Initiative (WAI) guidance “Developing an Accessibility Statement” and references WCAG 2.2.
- This statement is reviewed at least every twelve months and whenever a significant change to the site is shipped.
Frequently asked questions
Is thatdeveloperguy.com accessible?
The site targets WCAG 2.2 Level AA conformance and is in partial conformance with that standard. Most of the site meets the standard, but some components do not yet fully conform. Known gaps are listed in the statement above. The site does not claim Level AAA and has not yet been audited by an independent third party.
What assistive technologies are tested?
VoiceOver on macOS and iOS, NVDA on Windows with Firefox or Chrome, TalkBack on Android, keyboard-only navigation, browser zoom up to 400%, and operating-system reduced-motion and high-contrast preferences. The site is not specifically tested with JAWS earlier than 2023, Internet Explorer, or Dragon NaturallySpeaking.
How do I report an accessibility issue?
Email accessibility@thatdeveloperguy.com with the URL of the page and a brief description of the barrier. Acknowledgement within two business days, substantive plan or fix within ten business days. If a fix will take longer, an estimated timeline is provided. Equivalent alternatives are offered when a barrier cannot reasonably be removed.
How was the site assessed?
By self-assessment, not by an independent third-party audit. Self-assessment combines manual keyboard-only navigation, manual screen-reader testing with VoiceOver and NVDA, automated checks (axe DevTools, Lighthouse, WAVE), color-contrast verification (WebAIM, APCA), and a review against the WCAG 2.2 success criteria checklist.