RE: [Flashcoders] Using Tab key as a game control
Thanks Kerry - that is a very helpful reply. I do have quite a few other keyboard shortcuts and mouse controls but I understand the ease of using the Tab key to toggle between buttons. I recently completed a game for a large organisation and the tab functionality was a must for the accessibility requirements. I think it is probably safer to remove the in game tab and shift tab controls or replace with alternative key shortcuts. Out of interest, do you think the user should be able to tab between each square on the crossword? A-Z: Enter the typed letter into the square Space bar: Change between Across and Down Del: Clear the selected square Backspace: Clear the selected square (or previous if square is empty) Arrow keys: Select the neighbouring square Tab: Select the next word Shift+Tab: Select the previous word Home: Select the 1st square in the selected word End: Select the last square in the selected word Click on an unselected square: Select the square clicked on Click on the selected square: Change between Across and Down Click on a clue: Select the corresponding word Thanks Paul -Original Message- From: flashcoders-boun...@chattyfig.figleaf.com [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Kerry Thompson Sent: 22 May 2009 16:47 To: 'Flash Coders List' Subject: RE: [Flashcoders] Using Tab key as a game control Paul Steven wrote: Is it a bad idea to use the Tab key as a game control. Basically in a crossword game I am creating, I was going to use TAB to move to the next word and SHIFT TAB to move to the previous word. I notice however that when I press the TAB key all the buttons on my game screen are appearing with yellow boxes around them. I assume this is some kind of accessibility thing? Yes, it is an accessibility issue. People with compromised muscle control use the tab key to navigate to buttons, URLs, etc. I've built accessible programs a lot in the past, and I've disabled the auto-tab feature. The programs I've written have been tailored to work with specific hardware tools like switches and programmable flat-panel keyboard substitutes. If you're not building alternate accessibility features, though, you might be in a bind. Tab is the way most people navigate crosswords, but I've done crossword games where you can click on the clue or in a blank space in the puzzle. On the other hand, you might be able to get away with disabling Tab. There are other Web tools, like Shockwave, that don't implement Tab for accessibility. However, I'm not an expert on current accessibility requirements. I would recommend you find out more about what the law (and your client) require. Others on this list, and on Flash Tiger, can probably help you with that. Cordially, Kerry Thompson ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Using Tab key as a game control
Paul Steven wrote: Out of interest, do you think the user should be able to tab between each square on the crossword? That's one way of doing it, and probably just fine. It's not the way I would implement it--not that you're wrong, but here's what I have done, just to throw out a few ideas. I see that you recognize that you need to know whether you're in across or down mode. My crosswords pretty much automatically decide that--you start, by default, in across mode, with the cursor in the 1st square of 1 across. Tab takes you to the first square of the next across. If you type in a letter, the cursor automatically advances to the next square. It helps if you do crosswords yourself, which I do (I'm not very good at them, but I do them). I often have an idea for what a word should be, but before I fill it in, I check the clues for the down words intersecting my current across word. I'll often see a word I *know* is right, and fill that out before going back to the across mode (my default mode, on paper or on the computer). So, I like your idea of using a key to change modes. I would use Clicking on a cue to auto-select the mode, too, as well as you choice of selecting the word. Basically, as long as your interface is consistent and logical (yours looks good), it's fine. If you can do user testing, that will go a long ways towards telling you how good your interface is. I would also have a pop-up help screen with all the options, or even have them on-screen, depending on the real estate you have. You might, though it's not mentioned in your interface summary. A-Z: Enter the typed letter into the square Space bar: Change between Across and Down Del: Clear the selected square Backspace: Clear the selected square (or previous if square is empty) Arrow keys: Select the neighbouring square Tab: Select the next word Shift+Tab: Select the previous word Home: Select the 1st square in the selected word End: Select the last square in the selected word Click on an unselected square: Select the square clicked on Click on the selected square: Change between Across and Down Click on a clue: Select the corresponding word All in all, it looks good, Paul. You're on the right track. Cordially, Kerry Thompson ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Using Tab key as a game control
Paul Steven wrote: Is it a bad idea to use the Tab key as a game control. Basically in a crossword game I am creating, I was going to use TAB to move to the next word and SHIFT TAB to move to the previous word. I notice however that when I press the TAB key all the buttons on my game screen are appearing with yellow boxes around them. I assume this is some kind of accessibility thing? Yes, it is an accessibility issue. People with compromised muscle control use the tab key to navigate to buttons, URLs, etc. I've built accessible programs a lot in the past, and I've disabled the auto-tab feature. The programs I've written have been tailored to work with specific hardware tools like switches and programmable flat-panel keyboard substitutes. If you're not building alternate accessibility features, though, you might be in a bind. Tab is the way most people navigate crosswords, but I've done crossword games where you can click on the clue or in a blank space in the puzzle. On the other hand, you might be able to get away with disabling Tab. There are other Web tools, like Shockwave, that don't implement Tab for accessibility. However, I'm not an expert on current accessibility requirements. I would recommend you find out more about what the law (and your client) require. Others on this list, and on Flash Tiger, can probably help you with that. Cordially, Kerry Thompson ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Re: [Flashcoders] Using Tab key as a game control
Hi, Your tab key is part of the Accessibility stuff - you can set the tab-indexes on components which you may be able to do dynamically - this would make the accessibility thing work automatically. Trouble is you might be stuck with that beautiful yellow outline :) HTH Glen Paul Steven wrote: Is it a bad idea to use the Tab key as a game control. Basically in a crossword game I am creating, I was going to use TAB to move to the next word and SHIFT TAB to move to the previous word. I notice however that when I press the TAB key all the buttons on my game screen are appearing with yellow boxes around them. I assume this is some kind of accessibility thing? I believe I can disable this using tabEnabled = false however I do not want to do this if it will reduce the accessibility of my crossword. Any advice appreciated! Thanks Paul ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
