Design Template by Anonymous
Implementation Techniques
Example Site
This is an example site to showcase some inaccessible elements, and how to fix these elements to be more accessible. The elements are marked in the HTML, and the fixes are listed underneath. The fixes are based on the recommended WCAG guidelines.
Before
The before site contains many inaccessible elements. For example, there is one inaccessible element that is not visible in the image below and is not highlighted in the HTML code, but is fixed in the after website. As a part of manual checks, developers need to be able to find elements of their implementation that could be considered inaccessible and therefore more difficult to use.

Inaccessible elements are marked in red. Alternatively, the list of marked issues can be referenced to know which elements are inaccessible and how to fix them.

List of marked issues found in the HTML of the inaccessible site
- Title - Ensure there is a detailed title on your site.
- Semantic HTML - Check that you are using meaningful HTML. Instead of tagging a div as a header, use the header element to allow screen readers to read out the content as intended.
- ALT Text - This image has no ALT text making it innaccessible to those with slow wifi or low vision.
- Color Contrast - Use a color contrast checker to ensure the contrast ratio passes.
- Labeling - Use meaningful labeling. Instead of "Click here" use "Show Full Text".
- Spacing - The site may appear cluttered without breaks inbetween elements, making it difficult for users with cognitive disabilities to interpret.
After
The after site contains fixes to the previously found inaccessible elements. There is more spacing in between sections, higher color contrast, and easier keyboard access.

Accessible elements are marked in green. Alternatively, the list of marked fixes can be referenced to know which elements are now accessible.

The fixes are labeled in the after image.
List of marked accessible features found in the HTML of the accessible site
- Language - Ensure the language is listed.
- Metadata - Setting the initial scale to 1.0 helps users using screens of different sizes to see the expected site.
- Body Element - Using the body element further ensures screen readers will be read the content as expected.
- Skip Links - Adding in Skip Links allows keyboard users to skip to different parts of the site.