It is the true teacher who leaves the class knowing they have learned the most.

Tucson, AZ
Joined September 2006
Filter
Exclude
Time range
-
Near
As late as 2003! Made sense at that point to move to HTML, etc. I did better with structure, semantics as we had them, content clarity, order, meaning early on largely from linguistics, language and writing strengths. Logic and analysis too. First school computer? Punch cards. :D
1
1
Wow! My first home computer was a Commodore 64. 300 baud Hayes modem (not coupler, I was cutting edge lol). QLink was Commodore's BBS. I saw live, international chat for the first time and my life changed forever. :)
1
Replying to @ShaneHudson
There are existing systems all over. And they work although I do not know if #a11y scales to them, although theoretically it could if architected well originally.
Replying to @cgrymala
Way to learn alrighty!
LOL! Who remembers the convention we used if we used alt attribute values for spacers much less at all? :)
1
5
Despite IE3's #CSS advances, my typical rules were so presentational and illogical like most folks. We used pts not pxs or other options. Why? It was there. :P
2
6
Replying to @marybaum
I used vi. Emacs fanatics couldn't change that :) Of HTMLL editors, HotMetal first, went to Hot Dog, found and adored Homesite (Win as I contracted for MSN). Notepad, TextEdit, Visual Studio Code now, which I like a lot. Blogging? Wordpress despite #a11y issues. Personal loyalty.
Replying to @ShaneHudson
No, Lucerne. My memory banks are a big fragmented ;-)
1
Replying to @ShaneHudson
Yes, with targeted results. It was a very useful paradigm and I have seen it scale to Uni level research data when used with ontologies and in the most advanced case at the time I saw it, Selenium.
1
1
On Compuserve? Love it. Ah, The Well, GEnie, Prodigy, Delphi - multilne BBSs. Single line BBSs. Then Gopher, Telnet, Usenet, (FREENET FFS) - GREYBEARDS! Time for us to sit on rocking chairs and make statements like "these kids today!" Marco ;-)
This is tough as meaning is no longer specific. Devices meant media queries. Or, enhance a site with browser-based CSS like -moz etc. But what "content" and "web site" meant pre smartphone, autos, etc. has really challenged the "write once style anywhere". Web app ca 2005? Gmail.
Replying to @mholzschlag
I also see us selling “Responsive Design! So your site will look great on any device!” Responsive design, but for the grace of core image-handling in my favorite CMS, will download the desktop version of that restaurant’s site to your phone while you’re sitting in its bar.
1
2
Ha! You typed "Mold." Fact: In High School we all had rhyming nasty nicknames. Lee was "Flea". I was "Moldy." Fungus among us became the tagline. ColdFusion was human friendly. It had a brief renaissance in the late 2000s too :)
Frames could absolutely be crafted to be accessible to most especially if <noframe> content was made available. 12 frames with animated GIFs however did not my photosenstive epilepsy accomodate. One size never truly fits all, alas. :)
It's perception and personality, a value system. Our knowledge is power to me. Conversation, confrontation, learning, teaching, mediating, iterating, challenging assumptions as a constancy for myself and others can unite us with measurable patterns and inspire innovative inquiry.
Replying to @ShaneHudson
Did they? I can barely use the Web and insofar as esthetics it's not exactly CSS Zen Garden optimism. Sometimes I think presentation for document-based Web sites is pure waste. Of course, esthetic to me is often in the content, not the site's "design".
1
Mary articulatees what is exactly my concern for newcomers working legacy sites. If we don't have some exposure to at least the timelines and basics, how do we adapt? Of course, we are SUPPOSED to be backward compatible FULL STOP as a foremost design principle of Web, weren't we?
Replying to @mholzschlag
Still methodically stripping the floats out of stylesheets and replacing them with flex and grid.
2
2
Replying to @yatil
They had merit. Targeting content from one frame to another for example. And <noframes> helped but as noted made extra work. Then there were silly features like coloring browser and frame chrome, adding iframes into iframes. Honestly, it was very interesting and often just fun!
This was indeed problematic as was the ridiculous need to restate font presentation in every table cell. Also, a trailing </td> could break a page in a snap! I taught this stuff in 1998-2000ish. Remember Siege's "Creating Killer Web Sites?" He later stated he broke the Web :)
Don't forget the infinitely resizable transparent .gif files that propped all those tables open 👍🏻
1
5
Replying to @Spellacy
SO sorry. I meant the browser chrome that frames could (and at first only could) display, not Chrome the browser ;-)
1
Replying to @Spellacy
Hehe, with chrome? LOL!
1