Accessibility

Built for everyone.

Accessibility is part of the build, not an afterthought. Here is how this site measures up, what I commit to, and how to tell me if something is broken for you.

Effective: April 13, 2026 · Last reviewed: April 13, 2026

1. My commitment

Will C. Web Design is committed to making this website, and every website I build for clients, accessible to the widest possible audience — regardless of ability, technology, or network. I believe accessible design is simply good design. I work actively to improve the user experience for everyone and apply the relevant accessibility standards to all new work.

2. Measure of accessibility

This website aims to conform to Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium. WCAG 2.2 is the current international standard and is used as the basis for accessibility laws in the United States (ADA Title III), the European Union (European Accessibility Act), the United Kingdom, Canada, and most other jurisdictions that regulate digital accessibility.

In plain terms, the standard requires websites to be:

  • Perceivable — visible and audible to people using screen readers, screen magnifiers, captions, and other assistive technology
  • Operable — usable with a keyboard alone, without relying on a mouse, touchscreen, or voice
  • Understandable — predictable layout, clear language, and clear error messages
  • Robust — compatible with current and future browsers and assistive technologies

3. Current conformance status

This website is partially conformant with WCAG 2.2 Level AA. Most content meets the standard; the known limitations below are either being addressed or are outside my direct control.

4. Accessibility features on this site

  • Skip to main content link at the top of every page for keyboard and screen-reader users
  • Semantic HTML — proper use of <nav>, <main>, <article>, <section>, <header>, <footer>, <figure>, and heading elements for structure
  • Visible focus indicators — keyboard focus is always visible with a distinct outline
  • Alt text on all meaningful images; decorative images use empty alt attributes so assistive technology skips them
  • Sufficient color contrast — body text and interactive elements meet the 4.5:1 contrast ratio required by WCAG 2.2 AA (verified against cream background #fbf6eb and ink text #0f0d0b)
  • Responsive layouts that reflow gracefully on small screens and when text is zoomed to 200%
  • Keyboard-only navigation — every interactive element is reachable and operable with Tab, Shift+Tab, Enter, Space, and Escape
  • Reduced-motion support — animations (scrolling gallery, heartbeat pulse, reveal animations) are disabled when the operating system requests reduced motion (prefers-reduced-motion: reduce)
  • Form labels explicitly associated with their inputs, with visible required markers and clear validation feedback
  • Plain-language copy written at roughly an 8th-grade reading level; legal pages use headings and short paragraphs rather than dense blocks of text
  • Consistent navigation — the top nav and footer are identical across every page

5. Known limitations

I am aware of the following issues and working to fix them. Target completion dates are approximate.

  • Auto-advancing carousels on the home page and the scrolling gallery on the work page animate without a manual pause control. The animations do respect the prefers-reduced-motion operating system setting, but a visible pause/play button is not yet exposed. Target: July 2026.
  • Complex 3D transforms on the portfolio wall (desktop only) may feel disorienting for some users even with reduced motion enabled. I am evaluating whether to disable the 3D effect entirely under reduced motion. Target: July 2026.
  • Some decorative tap targets on mobile (blog "Read →" chips, portfolio "Live →" micro-links) meet the WCAG 2.2 AA minimum of 24×24 CSS pixels but are below the recommended 44×44 threshold. I am reviewing these. Target: June 2026.
  • Embedded third-party content — client portfolio screenshots displayed on the work page are static WebP images with descriptive alt text, so the content itself is accessible. However, when users click through to live client sites, those sites are not controlled by me and may have their own accessibility issues. I note this limitation but cannot fix third-party sites.

6. Compatibility

This site has been designed and tested to work with current versions of:

  • Browsers: Google Chrome, Mozilla Firefox, Safari (macOS and iOS), Microsoft Edge, Samsung Internet
  • Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
  • Zoom and magnification: browser zoom up to 200% without content loss; OS-level screen magnification
  • Input methods: keyboard, mouse, touchscreen, voice control (Dragon NaturallySpeaking, Apple Voice Control, Windows Speech Recognition)
  • Operating systems: Windows 10 and later, macOS 11 and later, iOS 15 and later, Android 10 and later, modern Linux distributions

This site may not be fully usable in legacy browsers such as Internet Explorer 11 or earlier, which do not support modern HTML and CSS features the site relies on. Upgrading to a current browser is recommended.

7. Technical specifications

Accessibility on this site relies on the following technologies, which must be supported by your browser and any assistive technology you use:

  • HTML
  • WAI-ARIA where HTML semantics are insufficient
  • CSS
  • JavaScript (progressive enhancement — core navigation and content work with JavaScript disabled)

8. Assessment methods

This site's accessibility has been evaluated using a combination of:

  • Automated testing — axe, WAVE, and Pa11y against WCAG 2.2 AA criteria
  • Manual keyboard testing — every page navigated with keyboard alone
  • Screen reader testing — spot-checked with NVDA on Windows and VoiceOver on macOS
  • Color contrast analysis — all text and essential UI elements verified against WCAG minimums
  • Reduced motion testing — behavior verified with OS-level reduced-motion preference enabled

I do not claim certification by a third-party accessibility auditor. This is a self-assessment made in good faith.

9. Feedback and how to report a barrier

If you run into an accessibility barrier on this site, please tell me. I take accessibility complaints seriously and will respond within 5 business days with either a fix, a timeline to fix, or an alternative way to get the information you needed.

When reporting a barrier, it helps if you include:

  • The page URL where the problem happened
  • What you were trying to do
  • What went wrong
  • Your browser, operating system, and any assistive technology you were using (if you know)

Submit feedback any of these ways:

10. Accessibility for sites I build for clients

Every website I build for a client is designed and coded to the same WCAG 2.2 AA standard as this site, unless the client explicitly requests otherwise. Accessibility is included in every package at no additional cost — not sold as an upgrade. For clients in industries with specific legal requirements (healthcare, education, government, finance), I document conformance and provide an accessibility statement template for their site as part of the handoff.

11. Enforcement

If you believe this site does not meet the accessibility requirements of the Americans with Disabilities Act (ADA) or any other applicable law, I would appreciate the chance to fix the issue directly first. I respond to accessibility concerns quickly and at no charge to you.

If you are not satisfied with my response, you may file a complaint with:

  • The US Department of Justice Civil Rights Division, at ada.gov
  • Your state attorney general's office

12. Updates to this statement

I review this statement quarterly and update it whenever I ship an accessibility improvement or learn about a new barrier. The "Last reviewed" date at the top of this page always reflects the most recent review.

13. Contact

Will C. Web Design
Las Vegas, Nevada, USA
Email: Williamwcrabb@hotmail.com
Subject line for accessibility feedback: "Accessibility Issue"
Contact form: willcwebdesign.com/contact/

This statement was prepared following the W3C Web Accessibility Initiative's accessibility statement guidance. It was written for humans, not compliance software.