keyboard accessibility
I am a keyboard only user, by preference. I have always been able to navigate around a website using the tab key. Recently this has stopped working. I looked on the forums and it talks about a config variable accessibility.tabfocus but when I go into config the variable does not exist. I am using FF 45.0.2 and OSX 10.11.4.
What has happened.
I am having to use Chrome at the moment as it seems to work.
Giải pháp được chọn
See:
Note: In OS X (as of 2005-01), if this preference is not explicitly set, the “Full Keyboard Access” setting in System Preferences will be honored. All builds before that date (e.g., Firefox 1.0.x) will ignore that setting.
This pref doesn't exist by default, so if you want to use it instead of the system settings then you need to create a new Integer pref with the name accessibility.tabfocus and set the value to what you want (7 is to tab through all the fields).
Đọc câu trả lời này trong ngữ cảnh 👍 0Tất cả các câu trả lời (3)
Sounds like you're looking for caret browsing. Not sure that works the same on MacOSX as it does in Windows OS's though.
http://kb.mozillazine.org/Accessibility.browsewithcaret http://website-archive.mozilla.org/www.mozilla.org/access/access/qa/win-webcontent-kbnav.html#caret-browsing
Giải pháp được chọn
See:
Note: In OS X (as of 2005-01), if this preference is not explicitly set, the “Full Keyboard Access” setting in System Preferences will be honored. All builds before that date (e.g., Firefox 1.0.x) will ignore that setting.
This pref doesn't exist by default, so if you want to use it instead of the system settings then you need to create a new Integer pref with the name accessibility.tabfocus and set the value to what you want (7 is to tab through all the fields).
I am happy to say that cor-el solution works and I am also using caret browsing.
A few comments:
Why has Mozilla made this solution so difficult to find and so difficult to implement? At a minimum accessibility.tabfocus could be included in the config file with its default setting like most other attributes. That would mean that I would have just had to change the default value to 7, which is much easier than having to create a extra attribute.
But I would suggest that it is made even easier by adding it to the accessibility section of preference so the feature can be set on without the complexity and danger of having to edit a config file. Surely that is not a significant piece of code.
A slightly more radical suggestion is that the accessibility section should be renamed personalization as the feature can be useful to a variety of people not just those with disabilities.