- From: Jim Homme <jhomme@benderconsult.com>
- Date: Wed, 4 Feb 2026 19:17:37 +0000
- To: "Wai Interest Group (w3c-wai-ig@w3.org)" <w3c-wai-ig@w3.org>
- Message-ID: <PH7PR16MB5216BA3254E4634BC0A25CEBDB98A@PH7PR16MB5216.namprd16.prod.outlook.com>
Hi, I usually think of hyperlinks as going to new pages and buttons as starting a process. For example, fill out a form and click a button, rather than a hyperlink. On a page I'm looking at, the styling looks like a button, and the tag is an anchor with a button role. I know that's symantically incorrect. If the anchor becomes a button tag, the style and tag will agree, but clicking it would go to a new page if the underlying code was changed. How should the anchor and the styling be handled if the developer wants this to look like a button and how should it be handled if they want it to look like a link. I'm assuming that if I were the developer, one choice is to let the browser do what it wants to the link. Thanks. Jim Jim Homme, Senior Accessibility Consultant Bender Consulting Services, Inc. #Bender30 #PaychecksNotPity #CompetitiveJobsMeanFreedom |jhomme@benderconsult.com<mailto:|jhomme@benderconsult.com> |benderconsult.com<https://benderconsult.com/> [Bender Consulting Services, Inc. 30 Years Advancing Disability Talent Investment. Talent Programs | Training | Digital Accessibility | Assessments]
Attachments
- image/png attachment: image001.png
Received on Wednesday, 4 February 2026 19:17:59 UTC