Monthly Archives: May 2008

alt=”waste”

Tuned out from HTML@W3C working group for a few months. (I was very busy at work, and participation in the working group is entirely a free time activity.) Ran across this long and apparently continuing argument that seems to boil down to whether <img> tags should be required to have an alt attribute to be accepted as HTML5 conformant. One or more of the guys associated with accessibility at their place of work seem to be arguing for mandatory alt usage.

Just to be clear, if the writer is not attempting to make a document accessible, then all we need for HTML is:

    <img src="a.png">

The above is an image with no extra information for accessibility.

All of the following is a waste of time:

    <img src="a.png" noalt>
    <img src="a.png" alt="">
    <img src="a.png" alt=".">
    <img src="a.png" alt="*">
    <img src="a.png" alt="boilerplate-put-in-only-because-it-is-required">
    <img src="a.png" alt="not-very-meaningful-text">
    <img src="a.png" alt="downright-misleading-text">

The above is ritualistic waste – about the only good it will do is give global warning a tiny boost, and perhaps delay the next ice age.

Frankly, I do not care about accessibility. Except when I do.

When I do not care about accessibility, if an HTML5 conformance tester bugs me until I waste time putting in bogus attributes, I am going to regard HTML5 conformance as a somewhat bogus waste of time. The vast majority of web pages have been and will be written from this frame of mind. Any attempt to force accessibility on this population is going to fail. Worse – attributes added for HTML conformance, but lacking meaningful human-semantic value, are likely to make pages a bit less accessible.

When I do care about accessibility, I need help – big time. Somehow I doubt that just filling in a few attributes is going to do the trick. I have never been part of an organization big enough to have folk dedicated to accessibility. That means I am pretty much on my own. Sure, I could go through and mindlessly fill out a bunch of alt attributes. I am sure this will make some bureaucrat happy, but I doubt the result will be very good. What I really need is something that will let me test the page as a whole, and give me some insight into how alternate browsing tools present the page.

Also it always kind of bugged me that the text inside an alt attribute could not be styled. Seems like the text should be treated like other text. Sometimes a little emphasis in the right place goes a long way.

This argument is a waste of time. Requiring alt attributes when the writer is interested in accessibility is a waste of time. Making HTML documents non-conformant because they lack meaningless boilerplate is a waste of time.

A test for accessibility (usable without expertise in accessibility) is a great goal, but pretty near independent of what should be the main concerns of the HTML working group.

Accessibility is a noble goal. You cannot force people to be noble.

Posted in html@w3c | Leave a comment

Is IIS still (as) relevant?

My preference for the server-side of web applications is Java (or Javascript in the JVM). In the past that meant I needed to allow for running a Java web server (like Tomcat or Jetty) behind IIS. For many applications it made sense for IIS to be the front-end web server. Most desktops were (and are) using Internet Explorer as a web browser, and used Microsoft’s security scheme. This meant using integrated Windows authentication which eliminates a lot of explicit logins, and was a lot more practical in most cases. Originally the only way to use Windows authentication was to use IE and IIS in combination, as the protocol was proprietary and undocumented by Microsoft.

For a long time we were pretty much locked to running Java code somehow behind IIS.

Since then the Samba folk have decoded the once-secret Windows authentication protocol, and provide an usable implementation in Java (JCIFS). The implementation was first available a few years back, but as with most new software the first few versions tended to be troublesome (to varying degrees) when deployed. A bit too risky for a product installed on hundreds of unique company intra-nets.

At the same time, Microsoft continues to make changes to IIS. Seems that every new version of IIS causes existing web applications (deployed on or behind IIS) to break in new and interesting (not!) ways, and more often than not at a customer site rather than in development testing. Microsoft has good reasons for continuing to improve IIS, but those same “improvements” are a continuing source of grief for both development and our customers.

Would sure be nice to get off the IIS upgrade (not-so-merry) merry-go-round…

Another constraint was the chance that the customer might want to install other web applications on the same server box. Those other intra-net applications were likely to require IIS.

On recent reflection – I am not sure that the once-required solution still makes as much sense.

  • The non-Microsoft implementations of NTLM authentication seem a lot more reliable.
  • Cheap/powerful hardware and widespread use for virtual machines (VMware and the like) means each web application is most likely on it’s own individual machine (virtual or not).
  • New and future versions of IIS are pretty much guaranteed to cause future grief.
  • Pure Java-based solutions can be run on non-Windows platforms.

Ditching IIS would sure make my (professional) life easier…

Posted in Security, Software, Web | Leave a comment

Not so much (electromagnetic) noise?

Do not know what to make of this…

My car has one of those common remote lock gizmos – no more than a little radio transmitter that sends a weak coded signal. Around here (densely populated southern California) the range is only about 20-40 feet (at most). Given all the other electronic gadgets in this area, the level of electromagnetic noise is likely quite high, and the limited range is not a surprise. Ditto for the remote to open the garage door from the car – I pretty much have to be directly in front of the house for the remote to work. When out in less densely populated areas, the car remote works from 100-200 feet away. Pretty much what you would expect.

Now comes the part less easy to figure out.

In the past several years there are stretches of time when the range of my local wireless network drops radically. Sometimes the drop is only for a few hours. Sometimes the drop lasts for weeks. Could be due to some noisy electronic gadget used by one of my neighbors, but no way to be sure – at least without somewhat-fancy laboratory-type gear.

There is another possibility.

My neighborhood is up in the foothills, with a view covering much of southern Orange County. Millions of people down there, as well as many electronic and defense-related businesses. Atop nearby hills there are some left-over odds & ends – clusters of antennas and the like. Some might be left-overs from the Marine base that was once nearby. Some might still be in use. There is some chance that my area could be in a “spotlight” or beam of what amounts to electromagnetic noise from somewhere down below the hills – a beam meant for some other purpose, but with the effect of raising the local noise level.

Just an idle speculation – nothing more.

Yesterday I hit the car remote from about a hundred feet away – and it worked! Odd. As we approached the house I (prematurely) hit the garage door opener from the end of the street (much too far away) – and it worked. Now wait just a second ….

Nothing proved, just curious.

Posted in General | Leave a comment