Something that is taken into huge consideration when designing websites is how accessibility plays into it. Especially for larger corporations like Amazon having an accessible webpage for many different demographics is essential to their business.
How did Amazon do?
I first ran a LightHouse Report using a webtool called web.dev.
It came up with these metrics:
Performance: 44
Accessibility: 88
Best Practices: 86
SEO: 92
(Max 100)
As you can see the latter 3 categories scored fairly well. The performance category, however, did not fare so well. When I analyzed some of the details that the report had generated this is what I found.
- Large amounts of unused JavaScript
- Time to Interactive was at 7.7seconds (meaning that's how long you had to wait to interact with the webpage)
- Images improperly formatted.
All of these things were found in the performance category. You might be asking, weren't we talking about accessibility not performance? Yes, but no.
By reading in between the lines of this report, you can make the assumption that when your performance takes such a large hit it will trickle over into your accessibility inevitably. Accessibility covers not only physical capabilities but also network capabilities as well. In the case of people with slower internet connection this webpage would be a horrible experience to browse.
Secondly I also ran a WAVE Audit. This kind of audit gets more into the nitty gritty details of accessibility and what you can do to fix the issues in your design. For example I found that ARIA menus were broken on the webpage. For people browsing the web that navigate via keyboard controls instead of a mouse, this would severely impact their experience. For example a user with tremors in their hands would use keyboard navigation instead of mouse for ease of access, but with a broken menu that would cause issues.
Video: https://youtu.be/pdrFRWhtK2Y
Channel: https://www.youtube.com/channel/UCDRkz-mU0NWAZTgN9kVc0Ag
Top comments (0)