ill
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
***
List Gui
On Thu, Dec 29, 2011 at 3:25 PM, Hassan Schroeder 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
>>
trol 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://webstandardsgrou
g Joe Random Site Author 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
***
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
***
List Gu
orks for me 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/guid
cusable and visible 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-
is an image that smoothly fades from one color to another."
My point was merely:
background-image: url(foo);
background-image: url(bar);
is equivalent to:
background-image: url(bar);
not
background-image: url(foo), url(bar);
--
Benjamin Hawkes-Lewis
**
describes the comma-seperated syntax you want.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
g sniffing 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.
-
ind 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 f
test case for this?
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
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://webst
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://webstandardsgroup
On Wed, Nov 10, 2010 at 3:07 AM, Micky Hulse 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 H
w.w3.org/WAI/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 Gu
.2.2
> I usually see 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, be
;t inherit outer object params).
For a discussion of Flash loading strategies circa 2007 see:
http://www.alistapart.com/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://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
"title", even if you do have useful advisory
information, it may not be the best place to put it.
http://www.paciellogroup.com/blog/?p=37
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
of screen
readers testing using pricy software".
You cannot freely test with the free JAWS demo thanks to EULA
restrictions, but the following are all free to test with:
* Window-Eyes Demo (30-minutes-per-Windows-session limit)
* NVDA on Windows (FOS
hrough the document, you will find you have already closed the "p"
element begun with an opening tag ("") on line 57 with a closing tag
() on line 72. So the validator correctly reports that it has found
a closing tag for an element that is not op
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://webstandard
support for definition lists,
but it's not especially pretty, which isn't surprising given the HTML
spec suggests using the element for "terms" and "descriptions", and also
for dialogs:
http://www.webaim.org/discussion/mail_messa
e is bad.
2. The default font size set in the browser constitutes a user choice
for body text to use that font size.
3. Publisher body text font-size suggestions override default font size.
Therefore:
4. Publisher font-size suggestions override a user choice.
Therefore:
5. Publishe
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 - no
essages and sucess messages) into the DOM simultaneously, then using
the "display" property to determine 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
t 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/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/
t;xml:lang" attributes:
http://www.w3.org/TR/i18n-html-tech-lang/#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/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
7;d suggest the answer 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
***
s, then you could make a case that:
@media screen, projection {
.thing {
display: none;
}
}
would 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 CS
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
is good or bad perhaps depends on
how widely useful your vocabulary would be.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join
.gov/
[4] http://www.w3.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
--
Benjami
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
**
On 9/2/09 07:45, Chris F.A. Johnson wrote:
How can CSS overflow replace ?
See http://www.ejeliot.com/blog/59
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http
inhawkeslewis/accessibility+ajax
And for accessibility best 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
**
nd
allow users to disregard 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
Help: memberh...@webstandardsgroup.org
***
d
with "display: none;", which 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
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
atibility for your content.
So as you can see, progressively enhancing with ARIA doesn't equate to
adding ARIA attributes with JavaScript, but rather to using ARIA as an
enhancement rather than replacement whether dependent on JS or not.
I think the more serious co
meone 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-
with this general point, though the way 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
HTML5, the drafting of XHTML 1.2
(which includes ARIA), and the gradual standardization of ARIA itself
are of significantly more interest than any draft of XHTML 1.1.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
ok too randomly 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/unsubscri
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-
ou 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-
rp-08.html?terms=frames
(although contrast
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
-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
are because I get different results from Cynthia Says and Total
Validators-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
a 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
means that if the user enforces their own colors for
increased legibility, the header _and its text_ will likely be invisible.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscri
red. Would 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 suppo
ons - they keep 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
***
fits which 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
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
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
'newText':'Text with JavaScript.'
};
// Check interfaces exist before trying to use them.
// Yes, the level of checking here is a little bit paranoid.
if (typeof this.window !== 'undefined' &&
typeof this.window.document !== 'undefined' &&
typeof this.window.document.getElementById !== 'undefined' ) {
// Get a reference to the P HTMLElement instance:
var p = this.window.document.getElementById('text');
// Internet Explorer does not support the standard textContent
// feature of the HTMLElement interface:
//
// <a rel="nofollow" href="http://developer.mozilla.org/En/DOM/Element.textContent">http://developer.mozilla.org/En/DOM/Element.textContent</a>
//
// But it does implement a similar non-standard property, innerText:
//
// <a rel="nofollow" href="http://msdn.microsoft.com/en-us/library/ms533899">http://msdn.microsoft.com/en-us/library/ms533899</a>(VS.85).aspx
//
// We can use typeof to detect which property is defined, if any:
if (typeof p.textContent !== 'undefined') {
p.textContent = strings.newText;
}
else if (typeof p.innerText !== 'undefined') {
p.innerText = strings.newText;
}
}
})();
//-->
Hope that helps.
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
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
E has seen much adoption).
--
Benjamin Hawkes-Lewis
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
, which is a not insignificant 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://webstandards
s17/page1.asp
http://www.cs.tut.fi/~jkorpela/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]
***
ts:
http://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
Unsubsc
lems with that pattern at:
http://www.w3.org/TR/WCAG20-TECHS/H44.html
and
http://green-beast.com/blog/?p=254
I'd suggest just using:
Label text: id="field-id" name="field-key" type="text">
62 matches
Mail list logo