I have a desktop application, and in this application there is a non-modal dialog where a user can make changes to something. The dialog has a Close button and a Save button. The Save button does not close the dialog, because we expect users to be making these changes, checking the result, and then possibly making more changes.
The state of the dialog will always be valid, there are no required fields or anything like that.
We have come up with two options for the save button:
- Leave the Save button enabled at all times. When a user clicks it, it will briefly display a check mark or perhaps a short success message for a couple seconds.
- Disable the Save button until a change has been made, then enable it. When clicked, it will go back to being disabled.
I can see pros and cons to each approach. Is there any accepted standard or a reason why one approach is better?
I have trouble typing the password on the login screen. The keyboard is very slow and cannot type on the login screen, only when the system is booting up from total shutdown.
There is no problem if the system was on sleep mode and open back on. It only happens after the total shutdown. And they keyboard is totally fine in the system itself. The issue is only on the login screen.
So, I need to use on-screen keyboard and type the password with the mouse on the login screen after everytime I shut down my laptop. Would love to fix this issue to avoid typing password with the mouse. Please help :'(
I’m using Ubuntu 19.04 and Acer Vivobook15.
I have a Dell XPS 9370 with a touch screen. When I wake it from sleep mode, but never during initial log in, sometimes the physical keyboard won’t register any input. When this happens I can still log in by swiping the screen to activate the onscreen keyboard.
Currently running Ubuntu 19.04, but have had the issue since I installed 18.04 fresh on it. Can supply any other details. Have a feeling this is something stupid but it’s driving me crazy.
I have a Kubuntu 18.04 installed and I’ve been playing around with my NVidia driver (I confess). By that, I mean that I had NVidia driver 430 installed and working completely. But then since I could not make NVidia PRIME work, I uninstalled the driver and reinstalled. I believe I’ve done that more than a couple of times (maybe one too many).
Anyways, the last time I installed the driver, it worked just like any time before that. But then after a reboot, the resolution is now fixated on something pretty low. After some searching online, I found that it might mean that the driver is not properly loaded. And I need to disable the secure boot. But then, I remembered that I had done this before and in fact each time I boot the system, before grub menu, it says
Booting in insecure mode or something like that. Still, I followed the instructions on this post but of course, you cannot disable something that is already disabled!
To give you a little bit more information:
$ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: GP102 [GeForce GTX 1080 Ti] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:c0000-dffff
Does anyone know how to install my NVidia driver properly?
So as the title said my account has been disabled.. twice. Both times was out of nothing, while scrolling thru my feed. Cant seem to get them both back. First time it was disabled I couldnt even make a new one – like I was ip banned, so I got a friend of mine to create it for me. Everything was going well and today this one got disabled too. I messaged support – no reply. And now I have no idea what to do. Facebook is the main platform I use to communicate with people and I need it….
Facebook account has been disabled
I have just purchased a office 365 business essentials subscription. Within the team site I need to modify the out of the box Edit Form for a new custom list. However, the Form Web Parts button from the ribbon is disabled. I am the global admin so do not think this is a permission issue. Any help would be much appreciated.
Just switched from apple to lenovo (carbon 7th gen), installed Ubuntu (19.04, with 5.0.0-25-generic). However, the touchpad randomly is disabled upon reboot (it is activated in the system settings). After rebooting the touchpanel sometimes starts to work, sometimes doesn’t. This happens only with the ubuntu partition, not with Windows. Can somebody help?
Tengo este codigo html < button disabled=”disabled” id=”proceed” class=”coss center”>Proceed
y quiero usar un codigo script para que en vez de decir disable sea enable, o simplemente que no aparezca el boton disable
Very related to this question: Accessible Disabled State but that is about how to style disabled buttons to make them accessibility compliant, but my question is slightly different.
Is it actually an accessibility requirement for disabled features to be contrast compliant?
You are not hiding functionality from visually impaired people by making it grey on grey because the feature is unavailable to everyone, so they are not missing out on features because of this. Yes, it’s always better for everything to be contrast compliant, but that might not be relevant here.
The situation is this – we have to disable features of our web application when the system is undergoing scheduled maintenance. Therefore we don’t want to remove the buttons altogether because we want the user to know that the feature is only temporarily unavailable. Additional messaging is provided on the page stating that some features are unavailable.
We designed a standard inactive state button (dark grey text on lighter grey button background) but it has come back to us with the concern that it may be failing DDA compliance. However I disagree with that concern for the reasons I state above. Am I mistaken, or is it OK to have grey-on-grey buttons for such situations?
Note: I’m not looking for any alternative solutions (leave that to the linked questions) my query is specifically about whether or not this is an accessibility concern.