include-pattern-feedback: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
Line 15: Line 15:
== Hyperlink Include - Screen Reader Testing ==
== Hyperlink Include - Screen Reader Testing ==


Some concerns have been raised over what implications using empty hyperlinks may have on assistive devices such as screen readers. The concern is that an empty link may be read out, partially read out or result in some other confusing scenario for the user.
Some [http://microformats.org/discuss/mail/microformats-discuss/2006-July/004693.html concerns have been raised] over the implications using empty hyperlinks may have on assistive devices such as screen readers. One concern is that an empty link may be read out, partially read out or result in some other confusing scenario for the user.


In response, a [http://allinthehead.com/demo/include.html test page] consisting of a number of empty hyperlinks in the style suggested by the pattern has been created. A 'good' result is that none of the links be read out.
In response, a [http://allinthehead.com/demo/include.html test page] consisting of a number of empty hyperlinks in the style suggested by the pattern has been created. A 'good' result is that none of the links be read out.

Revision as of 12:44, 21 July 2006

Include Pattern Feedback

Objects and Browser Behavior

Over at Yahoo! Local, we were using the object include pattern for all our hReviews on business detail pages and review listings. That is, until we realized that Safari and Internet Explorer both try to embed the entire page with every OBJECT call. (Firefox correctly recognizes that it's a local object and doesn't reload anything.)

On a page with 20+ reviews, this means a substantial increase in load time and memory consumption. As a result of this (bad) browser behavior, we removed the objects entirely.

Any suggestions for workarounds or modifications to the pattern?

-- AndyBaio


Hyperlink Include - Screen Reader Testing

Some concerns have been raised over the implications using empty hyperlinks may have on assistive devices such as screen readers. One concern is that an empty link may be read out, partially read out or result in some other confusing scenario for the user.

In response, a test page consisting of a number of empty hyperlinks in the style suggested by the pattern has been created. A 'good' result is that none of the links be read out.

Test Results: JAWS 7.0 with Firefox 1.5/Win

Tested by Phae 2006-07-21.

  • 31 dash include dash Mozilla Firefox
  • Page has no links
  • 31 dash include

Conclusion: the hyperlink include pattern presented no usability issues for this screen reader.