How to hide "Messages" section in Phabricator - phabricator

I am using Phabricator for a long time. It was working fine until I mistakenly press some key combination on my keyboard. Now it shows me "Messages" section all the time (Code review mode, tickets details mode and etc.). It cuts a lot of useful space.
I tried to find answer on 'Phabricator User Documentation' but no success.
Does anybody know how to hide "Messages" section?
I am using Safari 8.0.7 on OS X 10.10.4.

Use "?" to bring up keyboard shortcuts for that screen.
"\" toggles the Conpherence panel on/off.

Related

How do I test the accessibility of my Firefox extension's toolbar button (and attached popup)?

I'm writing a Firefox (web)extension. I have a browser_action in my manifest.json, with a default_popup. I want my extension to be accessible by all users, including those with vision impairment.
So I'd like to, as I change and develop things, test what it's like to (for example) interact with this feature, using only the keyboard. How do I do this? How do I focus and thus "click" the toolbar button, without a mouse?
Ideally, without actually running special screen reader software every time.
So I'd like to, as I change and develop things, test what it's like to
(for example) interact with this feature, using only the keyboard. How
do I do this? How do I focus and thus "click" the toolbar button,
without a mouse?
You can use commands to set a keyboard shortcut.
_execute_browser_action: works like a click on the extension's browser action
You may also add commands.update() (Firefox 60+) API to let users change that keyboard shortcut.
Thanks for considering accessibility. Just to clarify, because I don't think you meant this, but you can do keyboard testing without a screen reader. Just don't use your mouse :-) Seriously.
In my current firefox, I have an address bar, the search field, then a bunch of plugins on a toolbar.
On a PC (should be similar for a Mac, but Cmd instead of Ctrl):
I can move my keyboard focus to the address bar with alt+d or ctrl+L (cmd+L)
I can move my keyboard focus to the search field with ctrl+k (cmd+k)
Interestingly enough, I could not get my focus on the toolbar. I could have sworn I could tab from the address field, to the search field, to the toolbar, but it's not working now.
If you can get your focus there, then you should be able to use the left/right arrows to move between tools and then space/enter to select the tool.
If you want to play with a screen reader, NVDA is free.

Accessible Table of Contents

Does anyone know if the aria authoring web page is keyboard accessible(https://www.w3.org/TR/wai-aria-practices-1.1/) ? Looking for keyboard interaction assistance to move focus between the left and right pane.
It'd be nice if browsers took advantage of landmarks so that keyboard users would benefit. Currently, only screen reader users benefit from them. Most applications on a PC allow the F6 key to navigate to different areas. Try it in Word, Excel, browsers, whatever desktop apps. It even sort of works on the authoring practice page, but not completely (at least not in firefox).
We had to implement our own landmarks dialog that we invoked with Ctrl+F6 (so it'd be similar to F6) and we'd query the page for landmark roles and display them in a dialog to allow you to quickly jump to a section of the page.
Skip links are about as close as you can get now, but even that wouldn't help on a page like the authoring practice. If I had tabbed through half the links in the left nav panel and then decided I wanted to move the main contents in the right panel, a skip link wouldn't help. I'd have to navigate back to the skip link in order to jump to the main section. It'd be nice to hit a key while I was in the middle of the left nav to jump me to the right side.
You could use the accesskey attribute to allow a shortkey to move between the two, but those are hard to discover. JAWS will tell you about the accesskey but NVDA and VoiceOver will not. If you don't have any indication on the screen that there's a shortcut/accesskey, then how will people know it's there. Once they know about it, it's great. For example, wikipedia has an accesskey='f' on the search field, but you might not know that. Once you do know it, it's great to be in the middle of a wiki article and hit alt+shift+f (on firefox and chrome) or alt+f (internet explorer) to quickly jump to the search field.
You could do the same with a left panel / right panel configuration if you had an accesskey on an object in the left panel and a different accesskey on an object in the right panel. Just make sure users know about it.

How can I prevent JAWS screenreader from reading key strokes?

I'm trying to test the screenreader dialogue on my application for 508 compliance. It works mostly how it should except a problem I'm running into is when I navigate element to element the screenreader reads each keystroke like so "TAB" when I want to traverse through my application. How can I turn this off while testing? I'm running JAWS 17.
You can't and you shouldn't. Different verbosity settings like functional keys announcement, punctuation reading, repeated characters announcement, treatment of dialog controls and so on, and so forth, — all of these are entirely up to the screen reader and the user who adjusts these settings. Just like, for example, speech rate or pitch. As a JAWS user, I wouldn't be happy, and more than that, I would be angry if some app developer forced me to turn off my Tab announcement or changed my punctuation level.
Update: If you just want to turn off keystrokes announcement for yourself, do the following:
Press Insert+6 on the number row to go to JAWS Settings Center. You can do this from the JAWS main menu, but the single keystroke is much faster.
If you want to make your change by default for all apps, press Ctrl+Shift+D to open the default file.
In the search box type labels and search for Key Labels.
In the dialog that appears turn off the announcement for all of the keystrokes you don't want to hear. Note that if you mute Tab, all of the keystrokes like Shift+Tab and Ctrl+Tab will be muted automagically.
click OK several times to leave Settings Center and save your settings.
It's just a user setting options.
If you do that in your jaws, it's coild bé different for an other person !

Text console for development in JAWS?

I'm working on a web application and I want to make it easy to use via screen reader.
Testing stuff in JAWS is time consuming.
Is it possible to make JAWS display text instead of reading it?
I don't want actually to hear the content during development.
I just want to see what would be read by JAWS.
There is no speech viewer for Jaws, as far as I know. However, you can make it write all speech output to a log file using the "/z" switch. Unfortunately, you cannot view the log file in a text editor while the screen reader is running, because it is locked.
Open a command prompt or bring up the Run dialog by pressing Win+r and type:
"jaws_executable" /z"log_file"
Where "jaws_executable" is the full path and file name of the Jaws application and "log_file" is the location and name of the speech log file.
Important: There should be no space between "/z" and the log file name.
This is an old thread, but since it came up top in my search I thought I'd update it. JAWS 15 has just introduced this capability through the "Speech History" feature. Follow these directions to enable it:
If you miss one or more messages spoken by JAWS, you can press
INSERT+SPACEBAR, followed by H to open a Results Viewer window
containing up to the last 50 announcements spoken by the synthesizer.
When the Speech History window opens, you are placed on the line
containing the most recent announcement. To clear the history, press
INSERT+SPACEBAR, followed by SHIFT+H. The history is also cleared when
you lock the computer or completely log off. If you do not want JAWS
to maintain a speech history, clear the Enable Speech History check
box in Settings Center.
Read more in the JAWS 15 What's New document under New Speech History for Speech-only Users.
For those of you stuck with JAWS 14, Nektarios Paisios answer using the "/z" log worked best for me.
I believe there is a visual indicator in JAWS, but my version of JAWS is being a bit wonky. These days, NVDA plays pretty similarly to JAWS, so you can use that, and it has a speech output console: Right click the NVDA icon in the system tray, select Tools, and Speech Viewer.
The easiest way to see what a screen reader 'sees' is to disable the CSS. This will show you everything on the page that the screen reader can access. This will give you a good idea what is going on during development until you want to get into the more complicated stuff.
See http://www.iheni.com/quick-tip-testing-web-content-for-screen-readers-without-a-screen-reader/. This site has a lot of useful info too http://webaim.org/articles/.
You can enable the Braille Viewer in Start Menu > All Programs > JAWS 14.0 > Braille Viewer.
Braille Viewer will render visual text output of what would be sent to a braille display. It sometimes uses abbreviations or shorthand but is a close representation of the speech output.
Also take a look at Fangs Screen Reader Emulator for Firefox. It will render a text output of what a screen reader would announce on a page, in the correct read order, though it does not render dynamic content.
JAWS is supplied with a Braille Viewer in the 'Utilities' folder, which will render any text from the focus.

Telerik RadTextBox becomes readonly after selecting a Chrome AutoFill option

Wondering if anybody has seen this issue before or fixed it:
When the form loads, I can manually type into my address field (all fields are RadTextBox) with no issues
If I start filling the form from the top, after I enter the first few characters of my email address - Chrome provides a list of email addreses for me to choose from, If I select one - it fills in the rest of the form with the information associated with that email address.
So far so good.
When I now try to edit the subsequent fields, I cannot - they have become readonly!!!
In trying to solve this, my instinct is to open Chrome developer tools to see the difference between the fields that work, and those that don't.
But lo and behold - as soon as I open developer tools - the problem goes away!
Any ideas?
All Thanks to Stefan Sedich!!!
http://weblogs.asp.net/stefansedich/archive/2008/11/04/bug-with-latest-google-chrome-and-asp-net-validation.aspx

Resources