While we can and should define mechanisms to let dynamic content, add-ins and the like negotiate to try to avoid conflicts, they may still occur at times. With HTML4 and below, the behavior in such circumstances is left undefined, and consequently is handled differently by different user agents and so cannot be planned for. By contrast, native applications can count on specific, platform behaviors; for example, on Windows if a menu has two items with the same underlined accelerator key, the user knows that pressing the key will move the focus sequentially between them, and they can activate the one with the focus by pressing the Enter key. 

Issue: Should the author be able to suggest ways to handle shortcut conflicts? If an author could specify that pressing a shortcut would move focus sequentially between the elements that have that accesskey, and wrap, they author could design keyboard UI to take advantage of this in a way that is not otherwise possible. On the other hand, issues such as whether sequential navigation wraps should ideally be under the user's control, since wrapping is a significant advantage to some users (e.g. those who need to minimize the number of input commands) but a disadvantage to others (such as those who may not be able to tell when wrapping has occurred). Should the HTML5 spec state instead that user agents should follow platform conventions?