There is a problem with the results displayed from a search using this
page.
When tabbing through search results this screen reader user hears only
machine relevant link URI data, even though end user titling text is
visually presented for each link.
Since the text not being voiced is already on screen, this would be an
appropriate place to use the HTML 5 Title Attribute to programatically
associate the on screen titling text with the link URI.
Better still, use standard link strategies to hide the machine
data--users don't need that!
From a user report:
There is a problem with the results displayed from a search using this page.
When tabbing through search results this screen reader user hears only machine relevant link URI data, even though end user titling text is visually presented for each link.
Since the text not being voiced is already on screen, this would be an appropriate place to use the HTML 5 Title Attribute to programatically associate the on screen titling text with the link URI.
Better still, use standard link strategies to hide the machine data--users don't need that!