http://rahulgonsalves.com/research/site/
I'm throwing together a quick site to try and fund my travel to an
accessibility conference. I haven't had too much time to check it, or
think it through, but I would appreciate a page check, and general
suggestions/comments. Also, I don't have
On Nov 18, 2007 1:19 AM, Patrick H. Lauke [EMAIL PROTECTED] wrote:
James Jeffery wrote:
Not every anchor needs extra advisory information, so I don't see an
issue here.
The title attribute is optional, but a title can help to clearly and
accurately describe a link and for a website
@webstandardsgroup.org
Subject: Re: [WSG] AccessResearch // Page Check
On Nov 18, 2007 1:19 AM, Patrick H. Lauke [EMAIL PROTECTED] wrote:
James Jeffery wrote:
Not every anchor needs extra advisory information, so I don't see
an issue here.
The title attribute is optional, but a title can help
] [mailto:[EMAIL PROTECTED] On
Behalf Of James Jeffery
Sent: 18 November 2007 10:32
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] AccessResearch // Page Check
On Nov 18, 2007 1:19 AM, Patrick H. Lauke [EMAIL PROTECTED] wrote:
James Jeffery wrote:
Not every anchor needs extra advisory
Of James Jeffery
Sent: 18 November 2007 19:02
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] AccessResearch // Page Check
[quote cite=http://juicystudio.com/article/using-title-attribute.php;]
Values of the title attribute may be rendered by user agents in a variety of
ways. For instance, visual
James Jeffery wrote:
Some do, some don't. I would rather provide to those that do and give
the disabled a greater benifit for those that make use of the title
attribute.
Link text should make sense to *everybody*. If they don't, don't just
fix it for the poor disabled users, fix it for
I see where you are coming from, in a way.
It seems that there is a problem, not with developers, but with
accessibility overall if there is no way to provide additional
information for link text.
Anchor text such as The Future or Our Projects may be intended,
but to the average user they can
James Jeffery wrote:
Anchor text such as The Future or Our Projects may be intended,
but to the average user they can scan the page quickly and get an idea
about what The Future is relating to.
If they're written and constructed well, even completely blind users
with screen readers can scan
- The first thing that struck me was the blatent missues of the em element.
- Missing title attribute from your anchor's
- No indication as to who or what your site is about. At least a logo or name.
- Why use XHTML? If you are not using anything XML related you should
be using HTML. HTML is
http://rahulgonsalves.com/research/site/
James Jeffery wrote:
- Missing title attribute from your anchor's
Not every anchor needs extra advisory information, so I don't see an
issue here.
- Why use XHTML? If you are not using anything XML related you should
be using HTML.
Why not? Who
James Jeffery wrote:
- The first thing that struck me was the blatent missues of the em element.
- Missing title attribute from your anchor's
- No indication as to who or what your site is about. At least a logo or name.
- Why use XHTML? If you are not using anything XML related you should
be
Not every anchor needs extra advisory information, so I don't see an
issue here.
The title attribute is optional, but a title can help to clearly and
accurately describe a link and for a website thats based around
accessibility he should be using the title attribute where needed. He
has an
James Jeffery wrote:
Not every anchor needs extra advisory information, so I don't see an
issue here.
The title attribute is optional, but a title can help to clearly and
accurately describe a link and for a website thats based around
accessibility he should be using the title attribute where
On 18-Nov-07, at 1:18 AM, James Jeffery wrote:
- The first thing that struck me was the blatent missues of the
em element.
grinI like misusing me some ems!
Seriously, though, yes. I am using a technique that I saw on Stu
Nicholls site, CSS Play [1], which uses ems. Using a div, or a
On 18-Nov-07, at 5:06 AM, James Jeffery wrote:
He has an abbreviation in his link: 'FAQ' which should be wrapped in
abbr/abbr and he should use the title attribute here to add more
clarity.
Thanks for catching this one James. I did forget to add an
abbreviation for this. I have updated the
Ah shoot, mixed up my footnotes. I need some tea. Apologies to all
for increasing your inbox count.
The Ragged Float technique used by Stu Nicholls on CSS Play is
located here:
http://www.cssplay.co.uk/menu/flow.html
The WSG article on using xHTML versus using HTML is located here:
Rahul Gonsalves wrote:
Hi,
http://rahulgonsalves.com/research/site/
I'm throwing together a quick site to try and fund my travel to an
accessibility conference. I haven't had too much time to check it, or
think it through, but I would appreciate a page check, and general
17 matches
Mail list logo
