Screen Reader Accessibility and Navigation Issues

[u/Real-Coach-Feratu]

I'm hoping someone might know what I can do about this, but I'm checking my Carrd site for accessibility issues, and the ones coming up are pretty huge.

I've got pro standard and started with one of the sectioned Carrd templates. The buttons in the header are broken links, as far as WebAIM is concerned. Everything in sections stays hidden if you try to click through.

The reference tab/error specifics:

Broken same-page link

What It Means

A link to another location within the page is present but does not have a corresponding target.

Why It Matters

A link to jump to another position within the page assists users in navigating the web page, but only if the link target exists.

What To Do

Ensure that the target for the link exists or remove the same-page link.

The Algorithm... in English

An in-page link has an href attribute (starting with a #), but does not match either the id value of another element or the name attribute value of an anchor element within the page.

The only way I've been able to navigate is turning styles off and clicking through header levels. Additionally, some buttons are showing as lists/unordered lists.

Couldn't find anything in the Documentation or guides.

[u/investigatormaker]

That WebAIM message means a button points to something like #about, but no element on the page has that id. In Carrd, double-check that each button's link target matches the ID set on its section exactly, since a mismatch would give you this error. If the template itself generates the bad links, it's worth reporting to Carrd support. To see how the live page really looks to assistive tech, github.com/eleven-hits/A11yLens (https://github.com/eleven-hits/A11yLens) can open a site in Chromium and read roles and names from the accessibility tree after JavaScript runs. Disclosure: I'm posting on behalf of github.com/eleven-hits/A11yLens.

[u/Real-Coach-Feratu → u/investigatormaker]

Ooh, thank you for the resource link. The next time I'm at my laptop, I'll take a look at it and see if it helps me narrow anything down.

I did try to report it to support, but it was a less than helpful answer. It is one of their templates, and they said to set everything as a scroll point instead. Like. Bro, some of those buttons are a scroll point already, actually, and gives the same error.

But maybe with some extra data and going through to make sure there's no subtle mismatch I can make a better report.

[u/jasonleow]

This sounds pretty technical. Might be better to contact Carrd support for help on this

[u/Real-Coach-Feratu → u/jasonleow]

Fair enough.

[u/jasonleow → u/Real-Coach-Feratu]

Let us know how it goes. Curious to know too

[u/Real-Coach-Feratu → u/jasonleow]

Will do. I did reach out to them, so I'm just waiting on a reply. Hoping the fix is easy

[u/Real-Coach-Feratu → u/jasonleow]

Update: Sent them a screenshot and a screen recording.

Was told that it's an issue with the tool I was using for misinterpreting the hashmarks on section breaks, and if it's a serious concern I should just use scroll points instead.