://www.w3.org/TR/WCAG20-TECHS/H44.html
and
http://green-beast.com/blog/?p=254
I'd suggest just using:
div class=fieldlabel for=field-idLabel text:/label input
id=field-id name=field-key type=text/div
(substituting whatever you feel most appropriate for DIV)
--
Benjamin Hawkes-Lewis
://www.whatwg.org/specs/web-apps/current-work/#video
http://www.whatwg.org/specs/web-apps/current-work/#audio
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http
/forms/kbd.html
--
Benjamin Hawkes-Lewis
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
number if you're talking about,
say, boosting sales from a website.)
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help
much adoption).
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
that wrong too:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-August/016157.html
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
;
}
}
})();
//--
/script
/body
/html
Hope that helps.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
David Hucklesby wrote:
The validator still needs a DTD though.
If you mean the W3C validator, then no, it just got experimental HTML5
support.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
of them.
Any practical instance of which, in practice, has to deal not only with
tag soup HTML but also malformed XML, which rather undermines this point.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
standards
compliance creators strive for.
Standard is a pretty fuzzy word. Might be worth clarifying what
definition of standard you are applying here.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
options simple and visible.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
those
experienced with Pure CSS Drop-Downs assist my effort?
Why does the design require Pure CSS drop downs? Is there a plan for
keyboard accessibility here?
Note the famous Pure CSS dropdowns tend to require JS anyway in IE6 to
fake :hover support.
--
Benjamin Hawkes-Lewis
colors for
increased legibility, the header _and its text_ will likely be invisible.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
and Safari.
http://www.w3.org/TR/css3-content/
http://www.css3.info/image-replacement-in-css3/
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
-these are the two I frequently use.
Those are likely using completely different rulesets again, so you have
every reason to expect them to be different. They are as reliable as
their rulesets.
--
Benjamin Hawkes-Lewis
***
List
-title-attributes/
is a very useful discussion of the TITLE attribute from an accessibility
perspective.
I think the destination of a link is best made clear by the link text.
TITLE attributes are useful to provide tooltip text for icons however.
--
Benjamin Hawkes-Lewis
http://help.yahoo.com/l/us/yahoo/search/webcrawler/slurp-09.html?terms=frames
)
I have a client that seems determined to use them despite my best advice.
Use them how for what?
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
to make assumptions
about the height of the IFRAME content, and those assumptions will
inevitably break down under some conditions. (Try bumping up your text
size three or four steps and see what happens!)
--
Benjamin Hawkes-Lewis
different, not least because screen readers need
to interact with Flash functionality not just read Flash content.
However, sensible screen-reader users disable Flash.
Not when they want to listen to videos and audio on the web, they don't.
--
Benjamin Hawkes-Lewis
generic.
Sorry that's harsh, but I hope it helps.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh
.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
to write dates most
clearly in English is 9 February 2009 (or, somewhat worse, February
9th 2009) not any machine-readable readable syntax.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
mentioned using JavaScript to implement ARIA parameters. This is
a good idea...
Why?
but just how accessible would that be to a vision
impaired visitor with JavaScript turned off?
As accessible as your page normally is with JavaScript turned off to the
same user.
--
Benjamin Hawkes-Lewis
as an
enhancement rather than replacement whether dependent on JS or not.
I think the more serious compatibility problem with ARIA is the
immaturity and rapid pace of change of the draft specifications and
implementations.
--
Benjamin Hawkes-Lewis
are then styled display: block if a field
fails form validation. This breaks horribly when your styling
suggestions aren't applied, because the user will be confused by error
messages that do not reflect actual input.
Hope that helps.
--
Benjamin Hawkes-Lewis
publisher suggestions about font size and set
enforce their own preferences.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
practices generally see:
http://www.w3.org/WAI/intro/wcag.php
http://www.rnib.org.uk/xpedio/groups/public/documents/code/public_wacsitemap.hcsp
Hope that helps.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org
On 9/2/09 07:45, Chris F.A. Johnson wrote:
How can CSS overflow replace div style=clear:both;/div?
See http://www.ejeliot.com/blog/59
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
div/div
div/div
pbaz/p
are _all_ read:
bar
blank
baz
It also has a configuration setting for whether blank lines should be
spoken with the Say All command. If this is off (as it is by default),
then the above variations would all be read:
bar
baz
--
Benjamin Hawkes-Lewis
.org/TR/WCAG10/
[5] http://www.w3.org/WAI/intro/wcag.php
[6] http://dev.opera.com/articles/view/26-accessibility-testing/#usertesting
[7]
http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_seeitrightaudit.hcsp
--
Benjamin Hawkes-Lewis
on
how widely useful your vocabulary would be.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh
On 16/4/09 05:56, Gary Barber wrote:
Now it is
h#{
left: -px;
}
that had issues with screen readers.
Interesting. Not in my experience.
What screen readers and versions are you talking about? Do you have a
test case that demonstrates the problem?
--
Benjamin Hawkes-Lewis
be a correct method. But this assumption doesn't really reflect
the actual approach taken by screen reader developers. All popular
screen readers ignore speech- and braille-specific CSS.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
to your wondering is no. :(
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
/#ri20040808.101452727
http://www.w3.org/TR/i18n-html-tech-lang/#ri20040728.121358444
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
. Is this validator at fault then?
It's a testing assistant rather than a validator, strictly speaking.
And yes, I'd say it's at fault in this case.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail
which get shown to the user - rather
than using DOM methods to add and remove fragments to the DOM as required.
These do turn turn the partnership into a conflict.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
On 4/7/09 16:09, Felix Miata wrote:
On 2009/07/04 10:13 (GMT+0100) Benjamin Hawkes-Lewis composed:
On 2/7/09 17:07, Felix Miata wrote:
Zoom, minimum text size and magnifiers are defense mechanisms. The
basic problem is the pervasive offense - not respecting users'
font size choices
legibility for Joe than Joe and his browser vendor?
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
,
which includes some reports about poor support for implicit labels:
http://www.w3.org/TR/WCAG-TECHS/H44.html
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http
the document, you will find you have already closed the p
element begun with an opening tag (p) on line 57 with a closing tag
(/p) on line 72. So the validator correctly reports that it has found
a closing tag for an element that is not open.
--
Benjamin Hawkes-Lewis
-minutes-per-Windows-session limit)
* NVDA on Windows (FOSS)
* VoiceOver comes with OS X
* Orca on GNOME (FOSS)
The main hurdle here is not price, but developer inexperience with
with complex assistive technology.
--
Benjamin Hawkes-Lewis
Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
/articles/flashembedcagematch
For a useful JS library that abstracts a lot of the browser differences see:
http://code.google.com/p/swfobject/
Hope that helps.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
the rel attribute first, as in the example below, but does the
order of attributes matter or is the order convention, convention meaning,
that's what most people do?
Convention. I guess it puts the /purpose/ of the linked resource (namely, being
a stylesheet) first.
--
Benjamin Hawkes-Lewis
/PF/aria/complete#aria-level
(Those ARIA annotations are strictly unnecessary when UAs implement the Strong
native semantics and implied ARIA semantics from that table.)
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
On Wed, Nov 10, 2010 at 3:07 AM, Micky Hulse mickyhulse.li...@gmail.com wrote:
I wonder how many folks don't specify the http: part? It sounds like
there are no drawbacks.
Not quite:
http://www.stevesouders.com/blog/2010/02/10/5a-missing-schema-double-download/
--
Benjamin Hawkes-Lewis
for styling, feeds for feed autodiscovery), page
description (often excerpted in search results pages). Possibly Open
Graph Protocol metadata (http://opengraphprotocol.org/).
--
Benjamin Hawkes-Lewis
***
List Guidelines: http
fields before moving on to later fields.
I'd suggest adding a single progress element with JS, and tweaking
its value as the user actually completes the form.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org
for this?
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
this problem doesn't apply to other self-closing
elements, such as link.
Un-styled content flashing up in IE.
After reading, perhaps I could of worded the post a little better.
I guess - isn't the second topic an argument for ending with a link
as much as not?
--
Benjamin Hawkes-Lewis
of this sort, it is better to
differentiate the experience for known-bad browsers and assume all
other browsers are fully capable, so that users of capable minority
browsers are not locked out or forced to spoof. In other words: use a
blacklist not a whitelist.
--
Benjamin Hawkes-Lewis
want.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
);
not
background-image: url(foo), url(bar);
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh
on focus.
Food for thought:
http://www.w3.org/TR/WCAG20/#keyboard-operation
http://www.uie.com/articles/users_decide_first/
http://www.456bereastreet.com/archive/200705/accessible_expanding_and_collapsing_menu/
http://labs.benjaminhawkeslewis.com/rapid-access-hover-menu.html
--
Benjamin Hawkes-Lewis
in Chrome:
http://pastehtml.com/view/b7qe04of6.html
Do you have a testcase you can point to that fails in a named browser?
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http
in attributes using CSS generated content, e.g.:
dfn:hover:before { content: attr(title); }
However, you can't apply transform punctuation within the raw text
content into italics with CSS alone, for that you'd need JS too.
Hope that helps.
--
Benjamin Hawkes-Lewis
decide when that should happen is not.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
control of
the opening of new windows in such programs. At the very least, it's
predictable.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
On Thu, Dec 29, 2011 at 3:25 PM, Hassan Schroeder has...@webtuitive.com wrote:
On 12/28/11 8:08 AM, Benjamin Hawkes-Lewis wrote:
[snip]
Since they aren't navigating hypermedia, I'm not sure that's
comparable. But typically you have a fine degree of user control of
the opening of new windows
not a safe regex to validate email addresses. It will
exclude legitimate addresses like john.doe+la...@gmail.com.
I suggest just keeping it simple and checking for ^.*@.*$.
See also discussion at:
http://www.regular-expressions.info/email.html
--
Benjamin Hawkes-Lewis
62 matches
Mail list logo