X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

keyboard accessibility

Kuphostiwe

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.

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.

Isisombululo esikhethiwe

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).

Funda le mpendulo ngokuhambisana nalesi sihloko 0

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Adobe® Acrobat® Plug-in for Web Browsers, Version 15.010.20059
  • A plugin to detect whether the Adobe Application Manager is installed on this machine.
  • BlackBerry AppWorld plug-in
  • Plugin that detects installed Citrix Online products (visit www.citrixonline.com).
  • Provides information about the default web browser
  • DivX OVS Helper Plug-in
  • DivX Web Player version 2.1.1.94
  • The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
  • Garmin Communicator Plug-in Version 2.7.1.0
  • The Google Earth Plugin allows you to view 3D imagery and terrain in your web browser.
  • Version 5.41.3.0
  • The hpvirtualrooms-plugin is used to launch and update the hpvirtualrooms application.
  • Displays Java applet content, or a placeholder if Java is not installed.
  • LogMeIn remote control components
  • Picasa plugin.
  • RealPlayer Plugin
  • Shockwave Flash 21.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.0.3
  • 5.1.20513.0
  • XHTML editor.
  • iPhoto6

Isisebenziso

  • Firefox 45.0.2
  • Umsebenzisi oyi-ejenti: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
  • I-URL Yokweseka: https://support.mozilla.org/1/firefox/45.0.2/Darwin/en-US/

Izandiso

  • Firefox Hello Beta 1.1.14 (loop@mozilla.org)
  • Adobe Acrobat DC - Create PDF 15 (web2pdfextension@web2pdf.adobedotcom) (Akusebenzi)
  • DivX HiQ 2.1.1.94 ({6904342A-8307-11DF-A508-4AE2DFD72085}) (Akusebenzi)
  • DivX Plus Web Player HTML5 <video> 2.1.1.94 ({23fcfd51-4958-4f00-80a3-ae97e717ed8b}) (Akusebenzi)

I-Javascript

  • incrementalGCEnabled: True

Imidwebo

  • adapterDescription:
  • adapterDeviceID: 0x6920
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: 0x1002
  • driverDate:
  • driverVersion:
  • info: {u'AzureCanvasBackend': u'skia', u'AzureFallbackCanvasBackend': u'none', u'AzureContentBackend': u'quartz', u'AzureSkiaAccelerated': 1}
  • numAcceleratedWindows: 2
  • numTotalWindows: 2
  • supportsHardwareH264: No;
  • webglRenderer: ATI Technologies Inc. -- AMD Radeon R9 M395 OpenGL Engine
  • windowLayerManagerRemote: True
  • windowLayerManagerType: OpenGL

Okuthandwayo Okulungisiwe

Misc

  • Umsebenzisi JS: Cha
  • Ukufinyeleleka: Cha
the-edmeister
  • Top 25 Contributor
  • Moderator
5412 izisombululo 40317 izimpendulo
Kuphostiwe

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

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
cor-el
  • Top 10 Contributor
  • Moderator
17589 izisombululo 159123 izimpendulo
Kuphostiwe

Isisombululo Esikhethiwe

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).

See: *http://kb.mozillazine.org/accessibility.tabfocus 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). *http://kb.mozillazine.org/about:config

Umnikazi wombuzo

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.

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.