By piccoloprincipe
via nczonline.net
Submitted: Feb 17 2013 / 07:08
In today’s web applications, dialog boxes are about as common place as they are in desktop applications. It’s pretty easy to show or hide an element that is overlayed on the page using a little JavaScript and CSS but few take into account how this affects accessibility. In most cases, it’s an accessibility disaster. The input focus isn’t handled correctly and screen readers aren’t able to tell that something is changed. In reality, it’s not all that difficult to make a dialog that’s fully accessible, you just need to understand the importance of a few lines of code.
-
Neo4j/Cypher: Keep Longest Path When Finding Taxonomy
-
Unit testing code depending on the ASP.NET WebApi HttpClient
-
Google App Engine, PHP and Silex. Setting up a Login Provider
-
Traversing the GC Heap with ClrMd
-
Data-Driven Test Automation
-
Prevent JavaScript code blocking the UI thread with setTimeout + handy stopWatch to profile JS code
Add your comment
