Nowadays, accessibility overlays are all the rage - a "silver bullet" single line of code to make your website accessible. But the sad truth is that they make websites less accessible by overriding system defaults customized by the user. Despite this, why have only grown in popularity? The main reason is that, unless accessibility was a consideration at the start of development, it is time-consuming to implement. This project attempts to lend a hand to other projects at late-stage development to meet Level A of the WCAG 2.0 specification.
The above numbers are taken from the 2021 ADA DIGITAL ACCESSIBILITY LAWSUITS report. These lawsuits cost significant money to companies, and a significant number of websites aren't AA compliant. This also potentially costs businesses around 1 billion users who have barriers to entry as they have special requirements in some form. Apart from the direct financial losses, it also affects the brand reputation when a company is sued for failing accessibility standards.
The above graph is plotted in MATPLOT in the chart.m file
This is a draft of technical documentation created in Figma that lays out some of my ideas about a project that:
- Scrapes a given URL
- Analyzes the code
- Identifies elements that require modifications
- Flags those elements with possible solutions
- Compiles these changes in a checklist
Note: The code was not ready to be submitted, so only the prep documentation is submitted for the hackathon. The docs used Figma and MatLab
- Angular (Frontend)
- Node (Backend)
- Puppeteer (Webscraper)
- Express
- Firebase (Storage & Deployment)