Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
39 return (
40 <div className="grid grid-cols-1 md:grid-cols-5 gap-4">
41 {currentContributors.map((contributor, index) => (
42 <div43 key={contributor.login}44 className="bg-white m-2 p-8 rounded-lg shadow-md text-center cursor-pointer transform transition-transform duration-200 hover:scale-105"45 onClick={() => handleProfileClick(contributor.login)}46 >47 <img
48 src={contributor.avatar_url}
49 alt={contributor.login}
Description
Static HTML elements do not have semantic meaning. This is clear in the case of <div> and <span>. It is less so clear in the case of elements that seem semantic, but that do not have a semantic mapping in the accessibility layer. For example <a>, <big>, <blockquote>, <footer>, <picture>, <strike> and <time> -- to name a few -- have no semantic layer mapping. They are as void of meaning as <div>.
The WAI-ARIA role attribute confers a semantic mapping to an element. The semantic value can then be expressed to a user via assistive technology.
In order to add interactivity such as a mouse or key event listener to a static element, that element must be given a role value as well.
Bad Practice
<div onClick={() => {}} />
Recommended
<button onClick={() => {}} className="foo" />
<div className="foo" onClick={() => {}} role="button" />
<input type="text" onClick={() => {}} />