Ftrain is Accessible

At least, I think it's accessible.

Ftrain.com is a personal web site, and designed to be accessible to all readers. I've had to make some changes and screw with things a bit in order to make things work, so if something looks wrong to you, please email me.

Ftrain has always (i.e. for 5+ years) made an attempt to accommodate those using text-mode browsing, usually through special scripts that dynamically parsed content, and a number of people do read it that way, particulary, for some reason, Canadians.

Now, however, the dynamic, catastrophic interplay of web developers, CSS experts, and browser-makers has resulted in enough kludges, workarounds, and genuinely thought-about solutions that it is possible to build a single set of pages that work fairly well however they're viewed, whether by advanced jet-set browsers like Mozilla and I.E., text-only browsers like W3M and Lynx, or, I hope, screen-readers like JAWS. The odd kids out are Netscape 4.x, in which pages such as these explode all over the place, and Opera, which has some odd behaviors but works most of the time.

Ah well. I cannot please everyone. If a reader is using an outdated, broken software product, like Netscape 4.x, then the onus is, somewhat unfairly, on them to upgrade. However, if someone is using a software package that is the best possible tool for their particular way of reading - i.e. a screenreader for the blind - then I will try to conform to that standard - not perfectly, perhaps, but well enough.

So accessibility has long been the goal, but I've been too lazy to look into the specifics. Luckily for me, Mark Pilgrim created a web site called Dive Into Accessibility which offers a checklist for making your site easier to read for a variety of individuals with different needs, and then Michael Barrish took up Mark's challenge, and made his own site accessible. Since I have my own metadata-driven publishing system based entirely on XML, and I estimated that compliance with most guidelines would probably take 3 hours or so to put together, it was inexcusable for me not to be compliant.

Thankfully, those few hours really were only a few hours - I've been alt-tagging and meta-data-ing for a while, so adding some extra content to my template system was fairly straightforward. I'm sure I'm missing something, but I am able to say with moderate confidence that the 1000+ separate pages on Ftrain should be, in their greatest portion, readable to nearly anyone.

There are, I know, images from 1997 that don't have alt tags, and instead of proper div or hr tags I use three hashes to indicate a section divide, but the important things - that the fonts can be increased or decreased in size (I like to read sites at 200%, far back from the monitor), that the story comes before the navigation, that things flow in a simple, linear way as well as in their gridded form, as well as particulars like accessibility keys, relative links, and so forth, are all in place.

One note of interest - a lot of accessibility concerns overlap naturally with the general direction of XML-based content development. For instance, XLink links provide a much larger range of options for where and how links point to URIs than the regular href element - and can also support linkbases, which can be extremely metadata-rich databases of links. This leads to a change in approach: rather than having links as elements in a page, you include references to a database of links (which can be, among other things, bidirectional), which means that issues of, say, link consistency can be avoided - and adding title tags is no longer required, as a full summary of the link can be included in the link database, and propogated in a uniform manner on a link-by-link basis. Centralized databases of content are useful for ensuring the consistency of content - they can help you name, and refer to things, consistently. One of the most valuable parts of the LaTeX system for typesetting is the bibliography functionality - and large, shared bibliographies allow citations databases to be built up effortlessly. A single ID, a single reference, and suddenly data can explode out of anywhere.

The point? That accessibility, in addition to being a good thing to provide, is one facet of a larger range of issues about connecting data, and that humans and computers can all benefit from a little more metadata.

Thanks to Mark and Michael for the indirect goading.

And a big shout out to God.




Ftrain.com is the website of Paul Ford and his pseudonyms. It is showing its age. I'm rewriting the code but it's taking some time.


There is a Facebook group.


You will regret following me on Twitter here.


Enter your email address:

A TinyLetter Email Newsletter

About the author: I've been running this website from 1997. For a living I write stories and essays, program computers, edit things, and help people launch online publications. (LinkedIn). I wrote a novel. I was an editor at Harper's Magazine for five years; then I was a Contributing Editor; now I am a free agent. I was also on NPR's All Things Considered for a while. I still write for The Morning News, and some other places.

If you have any questions for me, I am very accessible by email. You can email me at ford@ftrain.com and ask me things and I will try to answer. Especially if you want to clarify something or write something critical. I am glad to clarify things so that you can disagree more effectively.


Syndicate: RSS1.0, RSS2.0
Links: RSS1.0, RSS2.0


© 1974-2011 Paul Ford


@20, by Paul Ford. Not any kind of eulogy, thanks. And no header image, either. (October 15)

Recent Offsite Work: Code and Prose. As a hobby I write. (January 14)

Rotary Dial. (August 21)

10 Timeframes. (June 20)

Facebook and Instagram: When Your Favorite App Sells Out. (April 10)

Why I Am Leaving the People of the Red Valley. (April 7)

Welcome to the Company. (September 21)

“Facebook and the Epiphanator: An End to Endings?”. Forgot to tell you about this. (July 20)

“The Age of Mechanical Reproduction”. An essay for TheMorningNews.org. (July 11)

Woods+. People call me a lot and say: What is this new thing? You're a nerd. Explain it immediately. (July 10)

Reading Tonight. Reading! (May 25)

Recorded Entertainment #2, by Paul Ford. (May 18)

Recorded Entertainment #1, by Paul Ford. (May 17)

Nanolaw with Daughter. Why privacy mattered. (May 16)

0h30m w/Photoshop, by Paul Ford. It's immediately clear to me now that I'm writing again that I need to come up with some new forms in order to have fun here—so that I can get a rhythm and know what I'm doing. One thing that works for me are time limits; pencils up, pencils down. So: Fridays, write for 30 minutes; edit for 20 minutes max; and go whip up some images if necessary, like the big crappy hand below that's all meaningful and evocative because it's retro and zoomed-in. Post it, and leave it alone. Can I do that every Friday? Yes! Will I? Maybe! But I crave that simple continuity. For today, for absolutely no reason other than that it came unbidden into my brain, the subject will be Photoshop. (Do we have a process? We have a process. It is 11:39 and...) (May 13)

That Shaggy Feeling. Soon, orphans. (May 12)

Antilunchism, by Paul Ford. Snack trams. (May 11)

Tickler File Forever, by Paul Ford. I'll have no one to blame but future me. (May 10)

Time's Inverted Index, by Paul Ford. (1) When robots write history we can get in trouble with our past selves. (2) Search-generated, "false" chrestomathies and the historical fallacy. (May 9)

Bantha Tracks. (May 5)

Tables of Contents