On Dec 3, 2007 7:48 AM, Jixor - Stephen I [EMAIL PROTECTED] wrote:
When I have used them the caption has always come form the link's title
attribute so I would assume that to be accessible?
Accessible to whom?
Some points to bear in mind:
1) Many (most?) screenreaders do not read the title
Hi all,
Many people would not yet have considered how business and organisations
are going to handle video as a standard document format. Can we get some
feedback about how much interest there would be in a proposal for
standard guidelines related to upload, storage, display of video and its
Matthew Pennell
1) Many (most?) screenreaders do not read the title attribute by default.
2) Many (most?) screenreaders are perfectly able to execute JavaScript, so
when the user clicks the link, what happens? It might announce that the
document structure has been updated (by the addition
Wow who decided it was a good idea to have screen readers support
javascript and not title attributes!
You could make make the image point to an html file with the same
filename and folder as the image then the javascript could replace with
.htm with .jpg.
Matthew Pennell wrote:
On Dec 3,
Wow, nobody decided whether or not it was a good idea or not. Screen readers
sit on top of the regular browser (in most cases on Windows, Internet
Explorer). They don't support javascript, they read the browser's DOM. The DOM
is affected by javascript. As users work their way through a page,
Hello All,
I'm working on a Likert scale questionnaire (Strongly Agree/Agree/
Undecided/Disagree/Strongly Disagree) with 20 questions and some
Googling came up with the following approach...
http://www.enterpriseaccessibility.com/articles/
AccessibleRadioButtons.html
...and I was
I don't recommend that solution. We have tested this kind of form with a
highly proficient screen reader user, and he could not understand it at all.
In fact it was one of the few tasks he has ever failed to complete. This is
one of those cases where marking up content so it is semantically
Hi Nick,
The sample code on this page you link to does not look ideal. As has been
mentioned on this list a few times, title attributes are often ignored by
screen readers. And the use of a table element to lay out the form is a
little odd.
Unless I am missing something, I'd say it would be much
On Behalf Of Matheus Neves
Hi all,
I see everybody using lightbox as a good solution for photo galeries,
i´d like to know if anyone now anything about it´s SEO friendliness
and if it´s also following acessibility guidelines.
I did something not as nice as lightbox, but IMHO a bit more
Hi to the List,
I'm working on an advanced form Layout for a complicated questionnaire
application.
I've setteled on a nested fieldset/legend/list/label/input markup wich
is semantically correct imho. And now i'm running (expectedly) into
some Problems in IE6/7. I've uploaded a testcase for the
Steve Green wrote:
I recommend using label elements for each radio button and hiding them
off-screen.
Possibly even better for keyboard and screenreader users: swapping out
the radio buttons approach with a single SELECT. However, this of course
throws the expected visual design out the
What happens if you use add the for attribute for the label? Does that
help correct any of the problem? Other than that I don't see anything
that should be causing too much of a problem.
Lord Armitage wrote:
Hi to the List,
I'm working on an advanced form Layout for a complicated
Hi Patrick,
Actually I had already prepared one as an alternative version to
discuss with the client so glad you brought it up independently.
Nick
On 04/12/2007, at 5:10 AM, Patrick H. Lauke wrote:
Steve Green wrote:
I recommend using label elements for each radio button and
hiding them
Hi Steve,
I don't recommend that solution. We have tested this kind of form
with a
highly proficient screen reader user, and he could not understand
it at all.
In fact it was one of the few tasks he has ever failed to complete.
This is
one of those cases where marking up content so it is
On 04/12/2007, at 12:07 AM, russ - maxdesign wrote:
Hi Nick,
The sample code on this page you link to does not look ideal. As
has been
mentioned on this list a few times, title attributes are often
ignored by
screen readers. And the use of a table element to lay out the form
is a
I have never had to use a CMS and know very little about them. I have a
client who wants to update his site himself and my hosting company
supports Joomla.
My question is: do I design the site in the normal way and then append
the CMS or is the site designed within Joomla? Am I restricted
Hi Lyn,
In order for them to work correctly, CMS systems usually restrict you to
using/designing application specific templates (some even incorporate
templating languages). You'll likely need to work with the CMS from the word go.
Bear in mind that if you haven't worked with CMS driven
Hi Lyn,
I have worked with Joomla! quite a bit - and do be honest I am not a great
fan. It is quite powerful in what you can do with it. Too answer your
question you are not limited in your design, however there is a bit of a
learning curve when it comes to Joomla! Also, you do not do your design
The problem with the code below is that the content of the legend
will be
read before every label. That makes it very difficult for a
screen reader
user to read it fast. I would just have the question in a p or
possibly
even a header element.
Once the user has read through a few questions
Steve Green wrote:
The problem with the code below is that the content of the legend will be
read before every label. That makes it very difficult for a screen reader
user to read it fast. I would just have the question in a p or possibly
even a header element.
However, if the user is in JAWS'
The problem with the code below is that the content of the legend will be
read before every label. That makes it very difficult for a screen reader
user to read it fast. I would just have the question in a p or possibly
even a header element.
Once the user has read through a few questions and
I'd think a little bit more about what you want your CMS to do before
jumping in with Joomla. I've only given it a cursory look over before
because I wasn't that impressed particularly by the sort of templating it
uses and the code it outputs. If your client just wants to edit pages
Thanks Adam and John
I think it will be just a matter of adding the odd photo and bit of text
so will check out WordPress etc. It certainly won't be a full-blown
management system that is required.
Thanks for the input.
Lyn
Western Web Design
Hi Lyn,
Personally, I had a bad experience working with joomla, and as a CMS, my
clients are not big fans either. I found it easier to build my own CMS for the
clients.
MT
Adam Martin [EMAIL PROTECTED] wrote: Hi Lyn,
I have worked with Joomla! quite a bit - and do be honest I am not a great
Undoubtedly it's the cleanest way to achieve the required functionality, and
there are fewer accessibility issues.
However, it is less easy for a user to quickly review their answers because
they have to read the text rather than just look at the physical position of
the selected radio button.
I have made such radio inputs highlight the selected item to make it
even more clear what the user has selected. Thats the radio and label
obviously, not just the radio. Of course that is only possible via
javascript however it still seems worthwhile.
Steve Green wrote:
You're right, and
You're right, and this is a problem we always have. Users develop different
ways of approaching forms, and some will jump in and out of forms mode to
make sure they read anything that is not in a label e.g. validation rules.
However, in the example given, I think the legend is way too long and
On 04-Dec-07, at 4:09 AM, Lyn Patterson wrote:
I have never had to use a CMS and know very little about them. I
have a client who wants to update his site himself and my hosting
company supports Joomla.
My question is: do I design the site in the normal way and then
append the CMS or
I would firstly consider what the content that your client wants to be
able to update himself actually is. If its highly complicated then you
might want to try to convince your client that it is not a good idea to
update it themselves. That said I try to convince all clients regardless
of job
Thanks Stephen and Rahul
Yes, I always try to do all updating myself and this is the first
client that really needs to do it as it will be a fairly frequent event.
I had a talk to him and it will only be replacing one photo with
another and changing a bit of text so nothing too onerous.
What is it you like best about texpattern. I've done one Mambo site and
really wasn't happy at all with they system once I learned it.
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Rahul Gonsalves wrote:
On 04-Dec-07, at 4:09 AM, Lyn Patterson
This makes me think does anyone know of a really good comparison table,
I have seen some that just have a few technical features listed but they
actually are fairly useless for most concerns.
Michael Horowitz wrote:
What is it you like best about texpattern. I've done one Mambo site
and
This is a pretty good resource for comparing CMSs.
http://www.cmsmatrix.org/matrix
Lisa Kerrigan
Website Editor
www.business.vic.gov.au
Department Innovation, Industry and Regional Development
Level 31, 121 Exhibition St
Melbourne Vic 3000
Tel: 03 9651-9176
Fax: 03 9651-9988
Email:
33 matches
Mail list logo
