{"id":1318,"date":"2024-09-03T11:58:21","date_gmt":"2024-09-03T11:58:21","guid":{"rendered":"https:\/\/html5accessibility.com\/stuff\/?p=1318"},"modified":"2024-09-03T15:30:05","modified_gmt":"2024-09-03T15:30:05","slug":"a-prayer-for-the-un-entitled-user","status":"publish","type":"post","link":"https:\/\/html5accessibility.com\/stuff\/2024\/09\/03\/a-prayer-for-the-un-entitled-user\/","title":{"rendered":"prayer for the un-entitled user"},"content":{"rendered":"

\"Dr<\/p>\n

I wuz reviewing a best practice issue being developed for TetraLogical<\/a> and wanted to check the verascity of a statement it contained.<\/p>\n

the information provided in the title<\/code>\u00a0attribute is not accessible to users navigating with a keyboard or touch devices, as they cannot hover over elements to view the content.<\/p><\/blockquote>\n

I know this was true in the past, but am also aware that Chrome fixed this so it is largely<\/em> available on interactive content<\/a>, of the rest who knows?<\/p>\n

try it for yourself<\/h2>\n
    \n
  • Open the test page<\/a> in your browser<\/li>\n
  • on desktop device or touch device with external keyboard: focus each interactive element using the tab<\/kbd> key<\/li>\n
  • on touch device: place focus on each interactive control<\/li>\n<\/ul>\n

    See the Pen
    \nUntitled<\/a> by steve faulkner (    @stevef<\/a>)
    \non     CodePen<\/a>.<\/p>\n