NVDA ignores title if it is identical to anchor text.So the outcome in situations B, C and D above are different: It may be noted that neither aria-label or title is available to keyboard-only users but the title is exposed as a tooltip when one mouses over the element. This will reduce the dependence on the CSS off-screen text method for providing such supplemental text to aid non-sighted users. anchor text or aria-label) needs to be supplemented with advisory text, the title is more suitable. In situations where text that is different from the anchor text needs to be rendered to aid vision impaired users, the aria-label is the better choice. The aria-label gains preference even over the anchor text in determining the accessible name for a link. NVDA developers are working on providing a better experience when a link contains aria-label as per the thread Regarding the accessible name calculation for aria-label within links?, which in part, motivated this article.īoth aria-label and the title are listed in the text alternative computation algorithm with the title having the lowest preference.This is akin to interrogating a link for presence of a title attribute with JAWS (or Window-Eyes) The title attribute is read by VoiceOver on OSX when the user explicitly checks for presence of help text on the element (VO+Shift+h).JAWS 15 provides the best user experience followed by VoiceOver on iOS.The test links are not indicative of markup to be used for download links for PDF (or other) file types. Default verbosity settings were used for all screen readers.VoiceOver was used with Safari on OSX and iOS.For JAWS, the above behavior is the same in Firefox and Internet Explorer (Windows 7).Both Aria-label and title present besides anchor text: Aria- label present besides anchor text:ĭ. Both Aria-label and title present besides anchor text: Annual Report 2013 Markup: Annual Report 2013Ĭ.
0 Comments
Leave a Reply. |