E-mail List Archives
Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?
From: Joseph Sherman
Date: Jul 30, 2018 10:39AM
- Next message: Birkir R. Gunnarsson: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Robert Fentress: "Is it okay to change ARIA role with JavaScript after page load?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread
I saw the exchange, that the Title element is no longer part of the accessible name calculation. We have been using the following code for some font icons- the plug in we are using allows only the addition of the Title element to the font icons repository. Manually adding labels for every use of the font icons is impractical, as most folks adding the icons are not code savvy, they just use the WYSWYG editor.
<a class="ts-font-icons-link " href="http://*/news/rss.html" target="_blank" title="RSS Feed"><i class="ts-font-icon icon-rss_ko" style="background-color:#ffffff; width: auto; height: auto; font-size: 31px; line-height: 100%;color:#353a3d;"></i></a>
Wouldn't it have be better to add the Title element to AT instead of removing it from the Specification?
Joseph
- Next message: Birkir R. Gunnarsson: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Robert Fentress: "Is it okay to change ARIA role with JavaScript after page load?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message in Thread: John Foliot: "Re: WCAG 2.1 - 1.3.5 - How to capture a violation?"
- View all messages in this Thread