Tired of the same trivial accessibility discourse?
» Time for some authentic conversations! «

Use the arrow keys to navigate between menu items.

Accessibility Statement

I want everyone, no matter their background or abilities, to feel welcome and enjoy a comfortable experience on my website. I believe we have to make room for everyone and I prioritise accessibility above all other efforts.

Last updated on: Jul 12th, 2024

Key points:

  • I'm aiming for the WCAG2.2 standard at the AA level.
  • I use a combination of automated and manual testing to do this.
  • Sometimes I mess up. I'm sorry about that, I want to do better and you can help me.

I've put a great deal of effort into making sure my website is accessible and friendly to all. I'm using the Web Content Accessibility Guidelines (WCAG) 2.2(Opens external link) to guide my efforts. These guidelines are meant for designers and developers and explain how to ensure web content is generally accessible. To make a long story short, they contain 87 success criteria split at three levels (A, AA and AAA) and while I've done my best to meet every one where applicable, I'm going for the Level AA here. As far as I'm aware, I've not found instances where I've failed to meet this level of conformance.

What about Level AAA?

In some cases, I went ahead and made sure my website conforms fully or partially with Level AAA.

  • 1.3.6 Identify Purpose. I used regions and landmarks to identify page regions. Where appropiate, I relied on ARIA to identify the purpose of certain interface components.
  • 1.4.8 Visual Presentation. I tried to keep my paragraphs to around 80-85 characters wide, not justified with adequate line spacing.
  • 1.4.9 Images of Text (No Exception). I don't use images of text.
  • 2.1.3 Keyboard (No Exception). You can access all functionality on this website with a keyboard.
  • 2.2.3 No Timing. I have not implemented any time limits or other constraints.
  • 2.3.2 Three Flashes. No content flashes more than three times per second.
  • 2.3.3 Animation from Interactions. You can disable all non-essential animations.
  • 2.4.9 Link Purpose (Link Only). You can figure out the purpose of the link from the link text alone.
  • 2.4.10 Section Headings. I separate the page content with headings.
  • 2.4.12 Focus Not Obscured (Enhanced). When elements have keyboard focus, they are entirely visible.
  • 3.1.3 Unusual Words. I try to define every weird word.

I wanted to make sure the web content is accessible for all recent versions of popular screen readers, your OS screen magnifiers, speech recognition software and any speech packages provided by your operating system. That seems like a mouthful; ultimately you should be able to enjoy the reading experience on my website no matter what web browser and plugins and assistive technologies you might be using.

My process

In order to achieve full Level AA conformance, I am routinely going through the following steps:

  • I scan every page using Deque's axe tools
  • I manually test each page using VoiceOver on mac and NVDA on Windows
  • I test the following browser/screen reader combinations:
    • NVDA with Edge and Chrome on Windows,
    • VoiceOver with Chrome, Firefox and Safari on mac
  • I run automated accessibility tests every time I change anything on my website
  • I have a CI process that runs a set of automated tests before every deploy

I prioritise all accessibility issues that result from this process above all other development work. In the future, I wish to include people with disabilities in my testing process.

Technologies used

I'm using the following web technologies on my website and all the tests I'm running rely on their presence:

  • HTML
  • CSS
  • SVG

I use the following technologies to improve accessibility and to progressively enhance the user experience for everyone. Most things should work fine without them.

  • Javascript

Help me do better

Despite my best efforts, there may be things that don't work the way you might expect them to. For example, I have not tested my website on mobile devices with assissitive technologies. There may also be instances where it won't work with your assistive technology or in your current situation.

I sincerely apologise for that. If you can't access specific materials or content on my website, please email me at bogdan@bogdanlazar.com, so that I can make it better for you and everyone else.

Should that happen, my first step will be to provide you immediately with an alternative that you can access depending on your specific situation. I will then try to remediate the original problem so that the people coming after you will benefit from your effort.

Accessibility Conformance Report (ACR)

You can also get a copy of my ACR that describes in detail how my website supports the recognized global accessibility standards of the Web Content Accessibility Guidelines (WCAG), ETSI EN 301 549 and Section 508 of the US Rehabilitation Act of 1973 here.

Version history

You can read through the entire changelog for my accessibility statement.