User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180605171542 Steps to reproduce: Try to display the title of an abbreviation like <abbr title="World Health Organization">WHO</abbr> without a mouse or screen reader. Keyboard only users can't focus on it. Not sure that mobile users can either Actual results: You can't display it without hover. Expected results: I'd be able to see a World Health Organization tool-tip like you do on hover.
Reproducible on desktop side on latest 60 Release and 62 Nightly, but I'm not particularly sure if this is something that should be fixed browser side, therefore I will initially triage this in the keyboard navigation to get additional opinions.
Status: UNCONFIRMED → NEW
Component: Untriaged → Keyboard: Navigation
Ever confirmed: true
Product: Firefox → Core
Sorry, but where else would this issue be fixed? There is no AT involved. With mobile users it's the same thing, other than it isn't available to anyone.
(In reply to Mike Gifford from comment #3) > Sorry, but where else would this issue be fixed? There is no AT involved. > With mobile users it's the same thing, other than it isn't available to > anyone. IMO, it kinda'of makes sense to me not to be able to focus it with keyboard, since abbr is in essence a tool tip, so my expectations for it are to work on hover. Also, nowadays most of the existing mobile devices have touch screens, so I'm at a loss why this could be a problem for mobile. Just to clarify, my opinion is a bit trivial, so in comment 2, I just triaged this bug and set an initial component in order for this bug to be discussed in a better suited section of Bugzilla. Apologies if that was confusing.
The same problems apply to tool tips in general. It's a flawed pattern for many with disabilities. I don't know if I can use HTML here but <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> guidelines don't give exceptions for tool tips. How do you hover on a tooltip with a smart phone? It's click or nothing last I checked.
https://developer.paciellogroup.com/blog/2013/01/using-the-html-title-attribute-updated/ seems to indicate comment 0's example is "NOT USEFUL or are of LIMITED USE" (caps in the article). Am I reading that correctly?
the limitation to it's usefulness is because of browser implementation: "The title on the abbr element is well supported by screen reader software, but its use is still problematic, as other user groups cannot access the expansion. It is recommended that the expanded form of an abbreviation is provided in plain text when it is first used in a document, and/or a glossary of terms that provides the expanded form is provided. This is not to suggest that that the expansion should not be provided using the title attribute, only that due to its limitations, an expansion in plain text should also be provided." So because browsers don't make good use of this, relying on the title attribution is problematic. This is a good place to change that so that keyboard only users and other assistive technology users can benefit from the description of the abbreviation.
OK, let's get Alex into the conversation as he's the accessibility module owner.
@title and abbr is indeed a problem when there's no mouse, but this is rather UX thing than accessibility one. However how about adding a small reference on the top corner of an element, maybe a question mark link, and when you click it, a popup appears? It would solve the problem, but might be felt heavy for the user interface.
(In reply to Anne (:annevk) from comment #10) > This is bug 97223 or bug 273704, right? I like the idea, however it seems doens't solve the problem for not focusable or not tabable elements.
This is a long-standing cross-browser problem. I don't expect us to prioritize resourcing to pursue this actively, but I'm leaving this open instead of outright WONTFIXing in case someone comes up with a solution that's acceptable both to users and to Web authors and is willing to implement the solution, too.
Priority: -- → P5
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.