Skip to main content

Web Accessibility

At Riley I Design, I believe good design is only truly good if it’s accessible.

I build websites so that as many people as possible can use them, regardless of device, ability, or context. Accessibility isn’t an “add-on” at the end of a project—it’s part of how I think about structure, content, and visual design from the start.

This page outlines my approach, what I currently do in my builds, and how I’m continuing to improve.

My Accessibility Approach

When I design and develop websites, I aim to follow recognized best practices from the Web Content Accessibility Guidelines (WCAG) 2.1/2.2 at the AA level. In practical terms, that means I focus on:

  • Clear structure: logical headings, consistent page layouts, and easy-to-follow navigation.
  • Readable content: sufficient font sizes, good line spacing, and plain language wherever possible.
  • Keyboard and screen reader usability: making sure core site functions can be used without a mouse and that interactive elements are announced clearly.
  • Color contrast and visual clarity: choosing colors that meet contrast guidelines and avoiding design choices that make text hard to read.
  • Mobile-first thinking: designing for smaller screens and touch interactions as a default, instead of as an afterthought.

Accessibility isn’t a one-time checkbox; it’s an ongoing practice that evolves as standards, tools, and my own skills grow.

What I Build Into My Websites

While every project is different, I generally include the following accessibility considerations in my work:

1. Structure & Semantics

  • Logical heading hierarchy (H1, H2, H3, etc.) so pages make sense to assistive technologies.
  • Proper use of semantic HTML where possible (navigation, main content, sections, lists, buttons, and form labels).
  • Meaningful page titles and meta descriptions that reflect the content.

2. Color & Typography

  • Color and type choices that support legibility, with contrast checked against WCAG standards.
  • Avoiding using color alone to communicate important information (for example, pairing color indicators with icons or labels).
  • Text that can be resized using browser settings without breaking the layout.

3. Images, Icons & Media

  • Descriptive alt text for meaningful images and icons.
  • Decorative images marked appropriately so they’re not read out as clutter by screen readers.
  • Captions or transcripts recommended for video/audio content where clients provide media.

4. Navigation & Interactions

  • Clear, consistent navigation across the site.
  • Buttons and links that look and behave like interactive elements (not hidden as “mystery meat”).
  • Focus states that are visible when using a keyboard to move through the site.
  • Avoiding animations or parallax that may cause motion sensitivity issues, or providing ways to reduce them.

5. Forms & Error Handling

  • Labels that are clearly connected to each form field.
  • Helpful inline error messages that explain what went wrong and how to fix it.
  • Logical tab order when moving through forms and interactive elements via keyboard.

Tools & Testing

I use a combination of:

  • Automated tools (such as browser-based checkers and contrast analyzers)
  • Manual checks (keyboard navigation, zooming, screen reader spot-checking where possible)

These help identify common accessibility issues early and allow me to correct them before launch. Automated tools can’t catch everything, so I also rely on thoughtful design decisions and ongoing learning.

Ownership & Ongoing Improvements

Accessibility is a shared responsibility.

  • During the build: I design and develop with accessibility in mind, and I advise clients when a content or design choice could create a barrier.
  • After launch: Clients are responsible for maintaining accessible content over time (for example, adding alt text to new images, writing clear headings, and providing captions for new video content).

I also recognize that accessibility work is never “finished.” As I learn more, I update my processes and apply improvements to future projects.

Known Limitations

Because I often work on existing websites, there may be platform or third-party plugin constraints that limit what can be changed. When this happens, I:

  • Flag the limitation clearly.
  • Suggest alternative solutions where possible.
  • Prioritize improvements that create the biggest positive impact for users.

If you encounter any accessibility barriers on a site I’ve built, I want to know about it.

Feedback & Contact

If you have trouble using any website designed or developed by Riley I Design, or if you have suggestions to improve accessibility, please get in touch:

Email: [email protected]

Please include:

  • The website URL
  • The page or feature you were using
  • A brief description of the issue and the device/browser or assistive technology you’re using (if you’re comfortable sharing)

I’ll review your message and do my best to address the issue or provide a suitable alternative.