Originally Web posted Wednesday, 4 September 2013.
Content last modified Saturday, 9 January 2021 .
External links last verified Friday, 2 August 2013.
This page is minimally formatted, to maximize accessibility.
I chose it to be a dot com so as not to limit my options in terms of commercial activities, though so far in practice, it has operated as a non-commercial site. To date, there has not ever been and is no advertising on the site. There are occasional hyperlinks to products or services, for purposes of connecting site visitors to said entities. No one here receives any compensation for the existence or use of these links.
In 2013 i added a For Sale section, the first overtly commercial activity on the site (and barely commercial at that, being basically an online garage sale).
The intent of the creator of this site is that its content be accessible to as many people and well-behaved machines as possible. Since the site content is created and maintained by one individual in his “free” time and without compensation, there are limits to real-world accessibility testing and the creator’s skill limits.
For many years now and especially since the summer 2013 site redesign, this site’s pages have been written to comply with W3C standards. Some very old pages are still written to the HTML 3.2 or 2.0 standard, yet most are written as HTML 4.01 Transitional (yet even most of these could validate as HTML 4.01 Strict). Over time pages which require newer features will be HTML 5 or newer. Earlier pages use hybrid CSS and HTML styling, whereas starting summer 2013 new pages started being written with pure CSS styling. If there are accessibility problems related to color choices, these should be easily overridden by a user style sheet. If you find any color-related accessibility problems which border on horrifically bad, i’d like to at least read your findings and thoughts.
I started to test the revised Summer 2013 site with Apple’s VoiceOver. Then i read up and learned that CSS 2.1 aural is basically dead and CSS 3 speech is barely supported by anyone, anywhere, anytime. Given that i couldn’t find any screen reader nor voice browser which acknowledges either the aural nor speech forms of CSS and runs on OS 10.4 Tiger and a PPC Mac—or really any Mac and OS X for that matter—i gave up, and have not revisited the situation since. VoiceOver and the others apparently will do what they do, regardless of any CSS styles i might apply (sigh). Unfortunately, this site will remain a sight-privileged vision-normative website until the situation changes significantly for the better… if it ever does during my lifetime.
Most of my image alt tags should be legitimate, but some may be bogus (especially older ones). I will gladly consider fixing egregiously bad ones which are pointed out to me.
Please let me know if you are experiencing problems with accessibility on this site… i may choose to re-do the style sheets to provide an alternate sheet, or may consider making other changes as warranted. I’d also love to hear from you if you know of free software for any Mac and macOS/OS X version which has decent support for any flavor of CSS audio styling.
Many historical technical details are elaborated on the Site History page. As noted above in the Accessibility section, for many years now the site has been designed to W3C standards. Because this is a personal site, my testing abilities and interests have been and continue to be limited. So far i have lived my computing/online life with Apple products. Therefore, the reference WWW browser for design of this site has always been one particular Mac OS/OS X browser, usually with the previous browser as the “less enhanced” reference.
As of summer 2016, the reference WWW browser remained the years-long favorite Safari 4.1.3 for OS 10.4 Tiger. Despite being technically an “obsolete” browser, it was the one i use every day, all the way through September 2016 when my PPC PowerBook suffered a hard drive failure (i lost nothing) and i decided it wasn’t worth putting a new drive in it or keeping it as a primary Mac.
Since late 2016 through the present (January 2019), i’m using the current or near-current Safari. In January 2019 this was Safari 11.1.2, because i super-duper don’t like what Apple is doing killing my fave extensions in Safari 12. With the conversion to TLS/SSL encryption on 26 January 2019, certificate issues are likely to kill off a whole bunch of old WWW browsers, including many of my former favorites. While https is not essential for an old-timey text and pictures site like mine, apparently there can still be man-in-the-middle attacks without it, so i’m moving forward despite hurting some of these older WWW browsers (already in a world of hurt from our changed Internet Web World).
Sometimes i include support for features which don’t fully work for me, e.g. opacity in the early 20-teens.
Ever since of learning about the design philosophy of progressive enhancement, i have chosen it over “graceful degradation”. I start with a bare-bones HTML 2 or basic HTML 3.2 or core, unstyled HTML 4.01 or 5.x design on each page, then style them up with CSS to make them as nice as possible (in the eyes of someone with arguably little aesthetic taste and no design skills—think Dilbert or any other engineer doing artistic design). I feel that this makes the site as accessible as possible on as many different technology platforms as possible with very little effort on my part.
For the most part (there are some exceptions), these pages do not specify font faces, nor link colors (unvisited, visited, hover, active). If you are not liking what you’re seeing (especially the font face(s)), please consider changing your WWW browser’s defaults, as that’s likely what’s setting what you’re seeing.
I generally only test in my reference WWW browser and maybe one other. Sometimes i’ll test in several, such as when making a major change or learning about a new-to-me feature of HTML or (especially) CSS. For important major changes, i test on the newest stable general release Firefox i can run, in addition to Safari. I choose not to test in Google Chrome because i cannot abide Google’s user agreement, or truly Google at all (Google has become Evil, truly!).
This site has never been tested on, designed for, nor even considered the existence of any version of any of Micro$oft’s WWW browsers (not even MSIE 5 Mac, which apparently was a pretty decent WWW browser in its day) by any name. If you are having problems with this site in a Microsoft WWW browser, too bad: use a different WWW browser or go away!
This strong stance is based upon all the abuse I received in the late 1990s and early 2000s as a Mac user during the worst of the Browser Wars, when people/sites arrogantly told be to go use MSIE on Winblows or Shut The Fuck Up! I’ve been turning the tables ever since, and intend to continue to do so. As MS continues to be goaded into making IE and Edge more standards-compliant (Thank You, Mozilla and Firefox!), it is likely that there will be fewer and fewer issues with this site and M$ WWW browsers. Yet please be clear: i don’t care if 90% of site visitors come here using M$ browsers (and this hasn’t been true for years, if indeed it ever was)—I’m not implementing any hacks to work around Micro$oft’s bugs! Not Happening, ever!
Yes, i know. I’m a no-income person who spends a lot of time at home where i can just as easily use a full-function personal computer, for starters. I’m also concerned about effects of so much electromagnetic radiation of all sorts on my body, and don’t especially want to add more very powerful transmitters so close to my body. For these reasons, i don’t own any sort of current handheld device. The summer 2013 redesign was my first attempt at supporting iOS devices per Apple’s guidelines for website developers and other general WWW information. I’ve been given an (old) iPhone 4S, as received running iOS 7.1.1 then in 2019 updated to iOS 9.3.6—newest as this device will ever go. This is the only iOS device testing i have done or can readily do. I have no access to any Android OS devices, nor really much interest in designing for them, nor in making a duplicate site for mobile devices. Every page should now have a viewport tag, and i did my best attempting to set the tag to something reasonable for each page (viewed on the iPhone 4S). In February 2014 i finally learned the CSS image trick (see the 6 March 2014 entry on the site history page) and readjusted many of these tags on many pages to make them look better at initial zoom on the iPhone (e.g. suck less). If anyone has suggestions for easy alternate stylesheets for these devices which are cross-platform standards-compliant (a’la W3C or a similar standards body), let me know.