Those are just “potential” problems. An automated accessibility checker is very limited in what it can check for. There are many accessibility checks that can’t be automated. Thus, the checker is recommending you check those issues manually because it can’t do that for you. That doesn’t mean that they are issues. It’s just pointing out that they “might” be issues, but is has no way of knowing.
Also, some of these potential issues are pretty ridiculous, for example:
Success Criteria 2.3.1 Three Flashes or Below Threshold (A)
Check 87: [`script` may cause screen flicker.](https://achecker.achecks.ca/checker/suggestion.php?id=87)
Including a script tag in no way implies there is a possible failure of 2.3.1. You are much more likely to have that with an animated image or embedded video.
Also, this checker only appears to go up to WCAG 2.0 when the current standard has been 2.1 for years now (with 2.2 coming in the next few months). I would suggest you use a more current accessibility checker. A few of the most popular are:
aXe DevTools
WAVE (web accessibility evaluation tool)
Lighthouse (this is built into the Chrome dev tools and uses aXe as the engine)
IBM Equal Access Accessibility Checker
ARC Toolkit
These are all browser extensions which allow you to run the check on any page you are currently viewing in your browser. But just like the AChecker, they will only be able to test for a small amount of accessibility issues. It is generally agreed upon that the best automated checkers can only catch perhaps 25-35% of accessibility issues. You will always need to do manual checks to catch the remaining issues.
I checked your code and I found some accessibility issues that you need to fix. Here are some tips:
You need to add a lang attribute to the html element, to specify the language of the document. This helps screen readers and other assistive technologies to understand the content better. For example:
<html lang=“en”>
You need to add a title element inside the head element, to give a brief description of the document. This helps users to identify the page in their browser tabs or bookmarks. For example:
<title>My Portfolio</title>
You need to add an alt attribute to the img element, to provide a text alternative for the image. This helps users who cannot see the image, such as those who use screen readers or have low bandwidth. The alt text should describe the content or function of the image. For example:
<img src=“profile.jpg” alt=“A photo of me smiling”>
You need to use semantic elements, such as header, nav, main, section, footer, etc., to structure your document. This helps users and assistive technologies to navigate and understand the layout and purpose of each part of the page. For example: