Accessibility

Accessibility means developing software that people, including those with physical disabilities, can use. This website welcomes everyone. My effort to make it accessible focuses both on the web performances, aesthetic, and content sides.

Web Performances

What does make a website “fast”? In my opinion, a speedy website loads quickly and provides a smooth UX. A program could have great UIs, but a slow loading would be an obstacle. On the other hand, the software could load instantly, but an awful UX would prevent a user from coming back.

This website is static. It’s blazing fast, and poor access to the network is not a big deal. Being built from scratch, I wrote every bit of code behind these Web pages, without libraries nor frameworks.

The number of web requests is another fundamental factor in web performances. This website stays away from calling resources like fonts, frameworks, and libraries. The absence of JavaScript code provides to show the bareness of this “home on the Web.” The compression of the source code further reduces the size of the pages. Web-safe fonts suit well.

This site can even work offline. A service worker ensures the “downasaur” will never annoy you. This characteristic contributes to makes this website a full-fledged PWA: it’s fast, reliable, and installable.

Aesthetic

This website is responsive, so it fits any screen size. It uses HTML’s semantic elements:

Content

The content follows a hierarchical composition; every page presents an H1 element, followed by a potential H2, H3, etc. Images are described with text equivalents, and colors guarantee adequate contrast.


Everything I wrote on this website reflects my personal views. Do you have questions, ideas, or suggestions? Do you want to get in touch with me? Do it!