Accessibility Statement

Last updated: June 1, 2025

DevWithDijah ("I", "me", "my") is committed to ensuring digital accessibility for people with disabilities. I aim to provide an inclusive, accessible experience for all users of my website (www.devwithdijah.com) and for all projects I develop.

Table of Contents

  1. My Approach to Accessibility
  2. Conformance Status
  3. Measures I Take
  4. Technical Specifications
  5. Limitations and Alternatives
  6. Feedback and Contact Information
  7. Ongoing Efforts and Future Improvements

1. My Approach to Accessibility

As a frontend developer, I integrate accessibility best practices throughout my development process. When collaborating with UI/UX design partners, I advocate for accessible design principles from the outset. My goal is to create web experiences usable by the widest possible audience, regardless of ability or technology.

2. Conformance Status

I strive to make this Site and my projects conformant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Full conformance is an ongoing process, especially as new content is added or third-party tools are integrated.

3. Measures I Take

To ensure accessibility, I (and my UI/UX design partners, where applicable) undertake the following measures:

  • Semantic HTML: Using correct HTML5 elements to structure content.
  • Keyboard Navigation: All interactive elements are operable via keyboard.
  • Focus Management: Clear focus indicators for keyboard users.
  • Alternative Text: Descriptive alt text for images.
  • Color Contrast: Sufficient contrast between text and background.
  • ARIA Attributes: Used judiciously for dynamic content when semantic HTML is insufficient.
  • Responsive Design: Content adapts to various screen sizes.
  • Readable Fonts: Clear fonts and adequate spacing.
  • Testing: Manual testing (keyboard-only, screen readers like NVDA and VoiceOver), automated tools (Axe DevTools, Lighthouse).
  • Collaboration with Designers: Accessibility discussed early in the design process.

4. Technical Specifications

This site and my projects rely on:

  • HTML
  • CSS
  • JavaScript
  • WAI-ARIA

These standards support accessibility across browsers and assistive technologies.

5. Limitations and Alternatives

Despite my best efforts, some limitations may exist:

  • Third-Party Content/Plugins: Some external content (e.g., embedded videos, social feeds) may not be fully accessible.
  • Complex Visualizations: For highly complex data visualizations, I strive to provide alternative text or summaries.

If you encounter an accessibility issue, please let me know.

6. Feedback and Contact Information

If you experience barriers or have suggestions for improvement, please contact me:

I aim to respond within 5 business days.

7. Ongoing Efforts and Future Improvements

Accessibility is an ongoing commitment. I continue to educate myself on best practices, monitor for updates to guidelines, regularly review the site, and seek feedback from users with disabilities.