Legal

Accessibility Statement

Our commitment to making Network Admin Journey usable by everyone, the WCAG 2.2 AA standard we aim for, known limitations and how to give feedback.

Last updated: October 14, 20264 min read

Network Admin Journey wants everyone to be able to learn networking and use our services, including people with disabilities and people using assistive technologies. This statement explains our accessibility goals for roadtoneteng.com, what we do to meet them, where we know we fall short and how to tell us about a problem.

Last updated: October 14, 2026

Our accessibility target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more perceivable, operable, understandable and robust for a wide range of people, including those with visual, auditory, motor and cognitive disabilities.

Our current status is partially conformant: some parts of the website do not yet fully meet the standard. We are working towards full conformance and describe the known gaps below.

Measures we take

  • Semantic structure. Pages use a logical heading hierarchy, landmarks, lists and tables with header cells so that screen-reader users can navigate efficiently.
  • Keyboard access. Navigation, menus, forms and interactive elements such as expandable FAQ sections are designed to work with a keyboard, with a visible focus indicator.
  • Text alternatives. Informative images and diagrams have text alternatives; decorative images are hidden from assistive technologies.
  • Color and contrast. We aim for text contrast that meets AA requirements and do not rely on color alone to convey meaning.
  • Readable content. We write in plain English where possible, explain acronyms on first use and break long guides into clearly labelled sections.
  • Code examples. Commands and configurations are presented as real text, not images, so they can be read aloud, resized, copied and translated.
  • Responsive layout. The site adapts to different screen sizes and supports zoom up to 200% without loss of content or function.
  • Accessible forms. Forms on the site, including contact forms built with Contact Form 7 and the WooCommerce checkout, use visible labels and provide error messages in text.
  • Reduced motion. We avoid auto-playing media and flashing content.

We check accessibility using a combination of automated testing tools, manual keyboard testing and screen-reader spot checks when we publish new templates or make significant design changes.

Known limitations

Despite our efforts, some content may not yet be fully accessible. Known issues include:

  • Network diagrams. Some complex topology diagrams have a short text alternative but not yet a full long description of every link and device. Where possible, the surrounding text explains the key details.
  • Interactive tools. Some of our network tools, such as the subnet calculator, may not announce updated results to all screen readers consistently. We are improving this.
  • Third-party components. Some features rely on third-party services, such as the CookieYes consent banner and our payment processors’ checkout fields. We choose providers with accessibility in mind, but we do not fully control their markup.
  • Older articles. Some older articles may have imperfect heading structure or link text. These are being updated as part of our regular content reviews, described in our Editorial Policy.
  • External documents. Links to vendor documentation, RFCs and other external sites lead to content we do not control.

Accessible services

Our consulting and mentoring services are delivered remotely. If you need adjustments, such as captions during video sessions, written summaries after a call, extra time, a particular document format or a different communication channel, please let us know when you book or at any point afterwards. We will do our best to accommodate your needs.

Compatibility with browsers and assistive technology

The website is designed to work with current versions of major browsers, including Chrome, Firefox, Safari and Edge, and with common assistive technologies such as screen readers (for example NVDA, JAWS and VoiceOver), screen magnifiers and speech-recognition software. It relies on HTML, CSS and WAI-ARIA, along with a small amount of JavaScript for interactive features. The core content of articles remains readable if JavaScript is disabled. Older browsers and assistive technologies may not display every feature as intended.

Feedback

We welcome your feedback. If you encounter an accessibility barrier on our website, or if you need any content in an alternative format, please contact us. To help us respond, please include:

  • the web address (URL) of the page;
  • a description of the problem you encountered;
  • the browser, device and any assistive technology you were using, if you are comfortable sharing this.

We aim to acknowledge accessibility feedback within 2 business days and to propose a solution or workaround within 10 business days. If we cannot fix an issue immediately, we will try to provide the information you need in another way.

Contact us

This statement is reviewed periodically and whenever we make significant changes to the website.