+5.3score from 87 to 93
Give links and buttons accessible names
11 of 13 assessed homepage links and buttons have a nonempty accessible name.
Read prompt
My website m-3yar.com scored 87/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it. I need you to: give links and buttons names recoverable from their HTML. The check it fails is "Links and buttons have accessible names", worth 5.32 points. What the scanner saw: 11 of 13 assessed homepage links and buttons have a nonempty accessible name. An unnamed link or icon button gives a reader little evidence of its purpose. The W3C Accessible Name Recommendation defines how text, referenced labels and native alternatives combine into a control's name; HTML-AAM describes native HTML mappings and remains a draft. Each link or button must: - have a nonempty name describing its actual destination or action; - preserve visible text when that already provides the name; - resolve any `aria-labelledby` references to the intended label elements; - give informative images inside controls useful alternatives; ```html <a href="/docs">Documentation</a> <button type="button" aria-label="Open search"> <svg aria-hidden="true" viewBox="0 0 24 24"><!-- existing icon --></svg> </button> <span id="download-label">Download report</span> <button type="button" aria-labelledby="download-label"></button> ``` Two things to get right, because they are the common failure modes. Text already names ordinary links and buttons, so adding ARIA everywhere is unnecessary. An `aria-describedby` reference supplies a description, not the control's name, and an unresolved `aria-labelledby` cannot supply the missing label. This check computes name presence from the collected homepage markup. It does not judge whether a name is accurate, load stylesheets, evaluate CSS-generated text, or execute widget scripts. Verify the resulting name in a browser as well, especially where CSS or JavaScript changes a control's visibility or contents. The whole report, as markdown, is at https://goodforbots.com/r/m-3yar.com.md?scan=cmvuerwkq6wag01qw9vx2kh1q. Read it first: this prompt covers one finding, and the report has everything the scan saw. When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.
