To improve the look of it for the client I have added some javascript
which hides the buttons and uses onclick events on the labels so that
the submit button doesn't need to be clicked.
I've done something somewhat similar recently, and found this was
finally an excuse to use the noscript
Kenny Graham wrote:
To improve the look of it for the client I have added some javascript
which hides the buttons and uses onclick events on the labels so that
the submit button doesn't need to be clicked.
I've done something somewhat similar recently, and found this was
finally an excuse to
Hi Chris,
Perhaps your question is more suited to a JS/DOM list/blog (e.g.
evolt.orgor others [1]) than WSG? More JS-type guys there, but I'll
give it a go:
An example page would be helpful (I've mocked-up a quickie at [2])... but I
wonder if the probem is your assumed DOM structure?
On
James Denholm-Price wrote:
inputs[i].style.display = 'none'
hides the input element but the next line:
inputs[i].onclick = function() { submitform(); return false }
attaches an onclick event handler to the (now hidden) element -- it's
possible that IE does not honour the label relationship
What are currently accepted practices for using noscript for
serving content to those with js turned off?
In particular I'm talking about eye candy things on a web page that
do not take away from the content if the non js visitor is served a
static equivalent as opposed to a you need js to
On 5 Mar 2007, at 13:52:35, Bob Schwartz wrote:
What are currently accepted practices for using noscript for
serving content to those with js turned off?
In particular I'm talking about eye candy things on a web page
that do not take away from the content if the non js visitor is
served
Bob Schwartz wrote:
What are currently accepted practices for using
serving content to those with js turned off?
In particular I'm talking about eye candy things on a web page that
do not take away from the content if the non js visitor is served a
static equivalent as opposed to a you need js
Nick, Ian,
Like this:
function copy() {
var container = document.getElementById(copy)
var oldtext = document.getElementById(copy1)
var text = (\251 + (new Date()).getFullYear() + F\351d
\351ration Internationale F\351line);
var p = document.createElement(p);
Best practice would be to avoid noscript where at all possible.
Start by assuming that the user does not have JavaScript enabled, so
that the simple version is part of the content, then use JavaScript to
hide or modify this to show your enhanced version.
I'm curious if you'd (both singular and
On 5 Mar 2007, at 17:35:22, Kenny Graham wrote:
Best practice would be to avoid noscript where at all possible.
Start by assuming that the user does not have JavaScript enabled, so
that the simple version is part of the content, then use
JavaScript to
hide or modify this to show your
Bob Schwartz wrote:
Nick, Ian,
Like this:
function copy() {
var container = document.getElementById(copy)
var oldtext = document.getElementById(copy1)
var text = (\251 + (new Date()).getFullYear() + F\351d
\351ration Internationale F\351line);
var p =
Hi all,
I've got a couple of questions regarding DHTML and how to ensure content is
accessible usable via screen reader.
Say you have a web page with a link to Subscribe to updates - when the user
hovers on the link, a form would be displayed below (standard dhtml show/hide).
The form would
It is difficult to give a definitive opinion without seeing your
implementation but I have never seen a design of this kind that was
accessible to a screen reader if the content was displayed on hover.
I doubt that displaying it on focus would work either. JAWS (and some other
screen readers)
We are holding a Pubstandards in Melbourne on the 7th March 18:30 at The
Sherlock Holmes Inn on Collins Street.
For all those who dont know what Pub Standards is, Please visit the London
Pubstandards website at http://www.pubstandards.co.uk
If you are interested in coming along to the pub to
Here's the rule of thumb concerning screen readers and hidden content:
Start with it in place from the beginning, then hide it with javascript
once you run some tests to make sure it works (ie event handlers etc)
That way you are safe. Trying to create this interactivity with a
screenreader
I have the task of writing the database/dynamic stuff behind an e-commerce
site. The design work and static pages are done by a professional design web
dev house in Brisbane, and yesterday I got hold of their work. My job now
is to merge their stuff with the shopping cart and other components
Hi all,
We have recently unveiled a new project on all things green,
eco-friendly and organic:
http://geofeat.com/
I would really appreciate feedback on issues related to standards,
usability and accessibility. This is an ongoing project, and there are a
number of things I have yet to implement
I think it looks great! Just a couple of things I noticed:
1. Your ordered lists could do with the text being indented rather than
wrapping under the number.
2. Your directory top 10 links don't change bg-color when they receive
:focus
3. Your main nav links don't change on :focus like they
I like the clean layout but to be honest when I read your description I was
thinking I wuld see more green seeing its a 'greeny' website
nothing like green for the corporate ID
On 3/6/07, Sarah Peeke (XERT) [EMAIL PROTECTED] wrote:
Hi all,
We have recently unveiled a new project on all
Fantastic work, Sarah.
My only comment is that I'd put your rounded corners in spans instead of
divs. Seems like it'd be more semantic. Being they're just holding images
and not really divisions.
Respectfully,
Mike Cherim
http://green-beast.com/
- Original Message -
From: Sarah
Sarah Peeke (XERT) wrote:
We have recently unveiled a new project on all things green,
eco-friendly and organic:
http://geofeat.com/
I would really appreciate feedback on issues related to standards,
usability and accessibility.
Sarah :)
Quick look in XP, Sarah.
Doing well in
21 matches
Mail list logo
