Before I start, I'd like to mention that you seem to be taking my last post rather personally. Don't. I have no interest in attacking or insulting you, only the expression of my opinion. You're welcome to take it, or ignore it. Your choice.
Originally Posted by
maverik
Splash page [...] I don't think that removing it is an option though because, from an ergonomic point of view, I need to catch surfers imagination [...]
However, you only need to do that once. On return visits, the splash page is nothing more than a hinderance. As I said, and cr3ative reiterated, at the very least place a link on it so that visitors (including search engines) can skip it.
Black text on a white background isn't going to do it for this client.
Where did I say you should only resort to plain text?
I've covered scripting in the websites help files.
Which is really very ironic: if a visitor has scripting disabled, how do you expect them to reach that document as they have to move through two script-only links to get there.
[...] they run the risk of excluding themselves from many/most websites.
In general, only because of incompetance or ignorance on the part of the author. Client-side scripting always was, and still is, an optional feature in user agents. It should not be used for critical functionality.
Its not my fault that Windows/Explorer leaks like a bucket
That's not the only reason why scripting is disabled. People are tired of authors - malicious or otherwise - fooling around with their browser just to make something "cool". Moreover, a scripting engine is implemented in all user agents.
In terms of 'No reason whatsoever' the reason is simple - its because this is the way I have been taught (at university) to build websites
That isn't a reason. If you were really taught to make a site dependent upon scripting, I'd ask for a refund of your tuition fees.
[...] I am NOT a programmer, I am a designer
That's fine. Authoring HTML documents isn't programming. Neither HTML nor CSS can be considered programming languages. The former describes the content of a document whilst the latter suggests how to display it.
I know what you are thinking.... stop building websites because you are messing in something you don't understand.
Where did you get that idea from? Anyone can, and should, be able to build a site. However, there's a different target for someone doing it professionally and someone doing it just to write about their favourite hobby.
That's fine when you have a budget that covers the time and expense [...]
What time and expense? There's a common misconception that creating accessible websites is far more time consuming than the "usual" way. This isn't true, as long as you know what you're aiming for. Two changes that would make your site instantly more accessible is the addition of alt attributes to your images, and removing the unnecessary scripting from your links.
With regard to alternative text, decorative images should specify an empty string. That is, alt="" Content-containing images, namely the images that contain text, should have alternative text that conveys that content. As for the links, change the
HTML Code:
<a href="javascript:;" ...
><img ... onMouseDown="MM_goToURL('parent','contact.htm');
return document.MM_returnValue"
></a>
pattern to
HTML Code:
<a href="contact.htm" ...><img ...></a>
In other words, replace the javascript:; href value with the second argument to the MM_goToURL function, and remove the onmousedown attribute from the images.
So if we can get back to the point. Has Dreamweaver compiled any code that might remotely effect the mouse button on a Windows PC? Yes or no?
Yes: the dependence upon client-side scripting, though that affects any platform.
if you would like me to become more educated can you point me to a document that explains how to 'Make Links, Links' rather than employing Dreamweaver to apply the link action.
The HTML Specification. That would be a good place to start. It's quite readable.
After that, I'd look at CSS so you can do away with some of the HTML 3.2-like mark-up. The cited document contains some material for learning CSS as well as the specifications themselves.
Originally Posted by
cr3ative
[...] don't use Dreamweaver, or Frontpage.
I'd like to qualify that, at least in part. Certainly I'd never advise someone to use Frontpage. That's just looking for failure. However, Dreamweaver isn't so bad provided you don't let it do the authoring for you. Don't use it's scripts and don't use WYSIWYG mode. However, do use its project management features.
Mike
Mouse button problems
Reply With Quote
Bookmarks