Hey NewsGrail,

Thanks for the bug report. Could you pass on the markup aswell please, just incase? I'll get Ruadhan to look into it as soon as he gets back from his holidays.

Thanks,
Daniel

haven't tried button but maybe consider using input type image as submit, it definatelly works and has one adventage that it has the same look on each browser

<input type="image" src="/i/submit.gif" alt="Confirm" class="iSubmit"/>

Firstly, I'd recommend that you simply don't use accesskeys at all, as they are incredibly unpredictable :(
Secondly, that button change may be enough to fix the issue, but I'd have thought that button would work ...

I mulled over abandoning accesskeys, but it seems everyone everywhere "officially" specifies to do so, including your own ready.mobi test. They're the UK government's almost-entirely-numeric ones, which I believe are the most widely available and least conflicting. If it becomes a problem I'll remove them.

Thanks for the advice artur, but I think there's more reasons to use HTML than images, particularly on a mobile and I do have a specific reason for using button in this location. It's input type="submit" elsewhere.

As far as the button type goes - fair enough. I'll have Ruadhan look into it when he gets back for you anyway.

Accesskeys are a bit of a bone of contention I believe. Standards "officially" state that they should be used (and supported) whenever possible, but in practice, it doesn't work like that at all. All S60 phones have dropped support for them, in favour of browser specific functionality (such as 1 goes back, 3 goes forward, 5 reloads - that kind of thing). They're also useless on any touch screen device that doesn't have a keypad.

Either way - there are plenty of perfectly legitimate use cases for keeping them, so if it suits you, why not?! :)

The validator still fails to recognise <button type="submit"> as a submit button...