Open Bug 1698998 Opened 4 years ago Updated 4 years ago

Dynamic results that look like built-in results don't have proper accessibility/a11y

Categories

(Firefox :: Address Bar, enhancement, P3)

enhancement
Points:
3

Tracking

()

People

(Reporter: adw, Unassigned)

References

(Blocks 1 open bug)

Details

Another thing highlighted by Daisuke's unit converter (bug 1697722): The top-most row element that dynamic results can modify is .urlbarView-row-inner, not .urlbarView-row itself. When you specify attributes in the view template's top-level object, they're set on the inner, not the row. If the whole row is supposed to be selectable, then the only thing you can do is set the selectable attribute on the top-level template object, and then the inner is the element that ends up being selectable. It looks fine, but it messes up a11y because the selectable element is not a direct child of the rows container, so screen readers don't announce it correctly. (Bug 1692615 had the same problem.)

The view template and update mechanisms should probably allow the row itself to be modified, maybe only in certain ways. I'm not sure why it doesn't work that way now. I might have had third-party extensions in mind, or just extensions in general, and thought that it wasn't wise to give them control over the row.

Blocks: 1699616
See Also: 1698980
You need to log in before you can comment on or make changes to this bug.