Re: [whatwg] [wf2] Late comments and questions on Web Forms 2.0

On Wed, 8 Mar 2006, Henri Sivonen wrote: > > Source level > The language is en-GB-hixie not en-GB-x-Hixie (as defined in Hixie English > 1.0-pre38 :-). Fixed. > 1.9. (and elsewhere) > It appears that "conformant" is not generally accepted in dictionaries. > ("Conforming" is.) It's commonly use

Re: [whatwg] False orthogonal nature :read-only and :disabled in WF2

On Tue, 21 Feb 2006, Matthew Raymond wrote: > > In the Web Forms 2.0 spec, under "8.2. Relation to CSS selectors"[1], > there is the following statement: > > | :read-write > | Matches form control elements that do not have the readonly > | attribute set (including password fields, althoug

Re: [whatwg] oninput event

On Tue, 14 Feb 2006, Ric Hardacre wrote: > > yes that's exactly the use i can foresee, i have this problem in an app > I'm working on currently, we can either use onChange or onKeyPress to > activate the totalizing function for a series of quantity and length > boxes. (e.g. 12 at 4 meters, 8 at

Re: [whatwg] Dynamic content accessibility in HTML today

I'll think about it what you say about the checkbox. Honestly it hasn't come up before. You're right in that if images are turned off then this example is no longer accessible to sighted users. While screen readers aren't the only important thing, they are important. If we put an alt text the

Re: [whatwg] oninput event

On Mon, 13 Feb 2006, Christian Schmidt wrote: > > Quote from the current working draft (10 January 2006) > : > > UAs may delay firing the input event if the data entry is rapid. > > Authors must not rely on this event firing once for each

Re: [whatwg] [wf2] changing the size DOM attribute of

On Sat, 11 Feb 2006, Anne van Kesteren wrote: > > I agree (with the part after the comma of the last sentence). Given that > per > > the option should be selected, it should remain selected when changing > some factor that

Re: [whatwg] [wf2] changing the size DOM attribute of

On Sat, 11 Feb 2006, Anne van Kesteren wrote: > > Browsers disagree on what should be selected in such cases. Simple > testcase: > > > > Opera 9 passes that test and I heard Safari nightlies do too. Internet > Explorer and Firefox fail t

Re: [whatwg] Web Forms 2.0 proposal

On Sat, 11 Feb 2006, Sean Hogan wrote: > > If I'm reading the spec correctly then "pattern" is used to prevent/allow form > submission, and to highlight an invalid entry. > > What I am suggesting is a filter that can be matched against for each keypress > event. If keyCode matches then the charact

Re: [whatwg] form validation of values that aren't entered by the user

On Wed, 1 Feb 2006, Hallvord Reiar Michaelsen Steen wrote: > > I suggest that > 1) willValidate should exclude readonly controls. Nothing the user > can do about those anyway. Ok. Changed. > 2) We should ignore maxlength errors for default values. Something > like the following pseudokode: >

Re: [whatwg] Dynamic content accessibility in HTML today

On 14/08/06, Aaron Leventhal <[EMAIL PROTECTED]> wrote: I hadn't considered putting an alt text on it, because the image's function is described by the role itself. It's got nothing to do with it's function, you've got an image in the page, to be accessible a user has to be able to find out wha

[whatwg] WF2: enctype value dispatch

Hi, http://www.whatwg.org/specs/web-forms/current-work/ 5.6 has "The value of the enctype attribute must be dispatched using a case- insensitive literal comparison." This text doesn't make any sense to me. regards, -- Björn Höhrmann · mailto:[EMAIL PROTECTED] · http://bjoern.hoehrmann.de Weinh

Re: [whatwg] Parsing entities

On Mon, 14 Aug 2006, Simon Pieters wrote: > > Ok. So the "i" is not consumed, just peeked at. Only when you see > "¬in" then you consume the "i" and "n" aswell. That was a bit unclear > to me at first. Right. I've added an example to the spec. -- Ian Hickson U+1047E

Re: [whatwg] Dynamic content accessibility in HTML today

On Mon, 14 Aug 2006 11:09:53 -0700, Aaron Leventhal <[EMAIL PROTECTED]> wrote: I'm suggesting something else, more like: 1) Use the role and state documents that will be public drafts soon, to find gaps in your set of elements. If those semantics aren't available in your set of fully functio

Re: [whatwg] [Web Forms 2.0] autofocus attribute

On Mon, 14 Aug 2006, Grey wrote: > > "Shouldn't" means it is not strictly forbidden. Indeed; there might be some valid use cases, which is why it is "should" and not "must". > And even if it was; the behaviour in the case authors break the rule > isn't what I want. I want my UA to ignore anyth

Re: [whatwg] Parsing entities

Hi, From: Ian Hickson <[EMAIL PROTECTED]> > I've read that several times. But it doesn't say that "i;" in "¬i;" > is going to be reparsed. ("noti" isn't an entity, but "not" and "notin" > are.) In "¬i;", the "maximum number of characters possible" that "case-sensitively [match] one of the ident

Re: [whatwg] Parsing entities

On Mon, 14 Aug 2006, Simon Pieters wrote: > > > > Section 8.2.3.1 "Tokenising entities", under "Anything else", covers this: > > "Consume the maximum number of characters possible, with the consumed > > characters case-sensitively matching one of the identifiers in the first > > column of the enti

Re: [whatwg] Dynamic content accessibility in HTML today

Jim, I hadn't considered putting an alt text on it, because the image's function is described by the role itself. Does the image for a checkbox using a standard html need an alt text? In any case, more effort on better examples is being put into Dojo, where the code will actually be used. Thi

Re: [whatwg] Parsing entities

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Mon, 14 Aug 2006, Simon Pieters wrote: > > I guess that for compat with IE and the Web[1] we have to treat > "Résumé" as if it were "Résumé". So how do we > handle "¬i;"? When the parser has come as far as "¬" it can't > return U+00AC yet because it c

Re: [whatwg] Dynamic content accessibility in HTML today

On 14/08/06, Aaron Leventhal <[EMAIL PROTECTED]> wrote: What browser/screen reader are you using? You need at Firefox 1.5 or later and Window-Eyes 5.5 or later or JAWS 7 or later. I'm not using a screen reader, accessibility is about not requiring a particular technology... Or did I miss a me

Re: [whatwg] Parsing entities

On Mon, 14 Aug 2006, Simon Pieters wrote: > > I guess that for compat with IE and the Web[1] we have to treat > "Résumé" as if it were "Résumé". So how do we > handle "¬i;"? When the parser has come as far as "¬" it can't > return U+00AC yet because it could well be "∉". But when it has > reac

Re: [whatwg] [WF2] Label with empty for attribute

On Mon, 14 Aug 2006, Anne van Kesteren wrote: > > On Mon, 14 Aug 2006 02:51:17 -0700, Matthew Raymond > <[EMAIL PROTECTED]> wrote: > > > > I think "for" should be treated analogously to "form". That would mean > > > > that the element is not associated with any control. > > > > > > Back compat wi

Re: [whatwg] Dynamic content accessibility in HTML today

I'm not at all arguing against having the better, more full-featured elements available in whatwg. I'm not saying that roles should subsume anything happening here. I'm suggesting something else, more like: 1) Use the role and state documents that will be public drafts soon, to find gaps in yo

Re: [whatwg] Dynamic content accessibility in HTML today

- Original Message - From: "Anne van Kesteren" <[EMAIL PROTECTED]> To: "James Graham" <[EMAIL PROTECTED]> Cc: "WHATWG" <[EMAIL PROTECTED]> Sent: Monday, August 14, 2006 6:48 AM Subject: Re: [whatwg] Dynamic content accessibility in HTML today | On Mon, 14 Aug 2006 06:36:40 -0700, James

Re: [whatwg] Dynamic content accessibility in HTML today

Anne van Kesteren wrote: So a while ago I posted http://annevankesteren.nl/2006/06/accessibility-ideas some of my thoughts regarding role=""... Basically, I don't really see authors taking extra steps to make things accessible. The same argument applies, presumably, to the alt attribute. And

[whatwg] Parsing entities

Hi, How are these entities handled? ∉ ª º ϖ &sugmaf; ⊆ ¹ ² ³ ⊇ ϑ Each of these have other other entities whose names are subsets of the above: ¬ ∨ π σ ⊂ ⊃ θ I guess that for compat with IE and the Web[1] we have to treat "Résumé" as if it were "Résumé".

Re: [whatwg] Dynamic content accessibility in HTML today

Anne, I said at the start of this thread that the best solution is to have widgets that are already accessible. However, we don't have a standard for that at the moment. We agree that accessibility experts should not be needed in order to make content accessible. It's not only big companies

[whatwg] XHTML and document.write()

Just a FYI. You have to deal with the edge case that the root element might be . Non conforming obviously, but what's supposed to happen should still be defined. I guess you would ignore calls to document.write() in such cases or perhaps copy the element and put it inside a element and try again.

Re: [whatwg] [Web Forms 2.0] autofocus attribute

On Mon, 14 Aug 2006 11:56:02 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote: On Sat, 28 Jan 2006, Grey wrote: "Authors should avoid setting the autofocus attribute on multiple enabled elements in a document. If multiple elements with the autofocus attribute set are inserted into a document, each

Re: [whatwg] [WF2] Label with empty for attribute

On Mon, 14 Aug 2006 02:51:17 -0700, Matthew Raymond <[EMAIL PROTECTED]> wrote: I think "for" should be treated analogously to "form". That would mean that the element is not associated with any control. Back compat wins this one I think. That and what's the point of having a with a cont

Re: [whatwg] Dynamic content accessibility in HTML today

On Mon, 14 Aug 2006 06:36:40 -0700, James Graham <[EMAIL PROTECTED]> wrote: But XBL works with ~0 assistive technologies and is presumably going to be complex to implement properly. Whilst, in general, I agree that having elements used in the correct way to provide semantic information is de

Re: [whatwg] Dynamic content accessibility in HTML today

Jim, What browser/screen reader are you using? You need at Firefox 1.5 or later and Window-Eyes 5.5 or later or JAWS 7 or later. - Aaron Jim Ley wrote: On 13/08/06, Aaron Leventhal <[EMAIL PROTECTED]> wrote: So we already have truly accessible DHTML widgets that are key navigable and usabl

Re: [whatwg] Dynamic content accessibility in HTML today

Anne van Kesteren wrote: On Mon, 14 Aug 2006 06:22:40 -0700, Aaron Leventhal <[EMAIL PROTECTED]> wrote: I like the role attribute because it's already usable in Mozilla, to make accessible web applications. What's the advantage of using class/appearance instead, if there is no browser already m

Re: [whatwg] Dynamic content accessibility in HTML today

On Mon, 14 Aug 2006 06:22:40 -0700, Aaron Leventhal <[EMAIL PROTECTED]> wrote: I like the role attribute because it's already usable in Mozilla, to make accessible web applications. What's the advantage of using class/appearance instead, if there is no browser already mapping this informati

Re: [whatwg] Dynamic content accessibility in HTML today

So you are saying this should be mapped to assistive technologies via the CSS3 "appearance" property or via special values in the class attribute? The role attribute currently describes behavior, and is added so that users with disabilities know what the behavior for a given element is, accord

Re: [whatwg] Dynamic content accessibility in HTML today

James Graham wrote: > Matthew Raymond wrote: > [...] where a proper CSS presentation for the users primary media is not available [...] >>> This is almost always the case on the real web. >>Yeah, the web masters are so lazy that they can't be bothered to add >> accessibility via CSS,

Re: [whatwg] [Web Forms 2.0] autofocus attribute

On Sat, 28 Jan 2006, Grey wrote: > > "Authors should avoid setting the autofocus attribute on multiple > enabled elements in a document. If multiple elements with the autofocus > attribute set are inserted into a document, each one will be processed > as described above, as they are inserted. T

Re: [whatwg] [wf2] addition and attributes of type ID

On Fri, 27 Jan 2006, Anne van Kesteren wrote: > > I was wondering if 13 of > perhaps could > be changed to say that all attributes where isId returns true should be > removed instead of just the one that was chosen as name of the > repe

Re: [whatwg] [WF2] Label with empty for attribute

Ian Hickson wrote: > On Sat, 21 Jan 2006, Anne van Kesteren wrote: >> I think "for" should be treated analogously to "form". That would mean >> that the element is not associated with any control. > > Back compat wins this one I think. That and what's the point of having a with a control in

Re: [whatwg] [wf2] "data" attribute set to the same value through script

On Sun, 22 Jan 2006, Anne van Kesteren wrote: > > What happens when you modify the data DOM attribute and set it to the > same value the data content attribute currently has? Would that result > in getting the file again and appending new data (if > type="incremental")? If a select or datalist

Re: [whatwg] [wf2] valueMissing versus missingValue

On Sat, 21 Jan 2006, Anne van Kesteren wrote: > > Currently the Web Forms 2 draft has both a valueMissing flag and a > missingValue flag. They are supposedly identical. Opera has currently > support for valueMissing (that's also what the (not yet public) test > suite is testing), but both are ea

Re: [whatwg] [wf2] "required" attribute and pseudo-classes

On Sat, 21 Jan 2006, Anne van Kesteren wrote: > > In I think the text > on :required and :optional should be clarified so that it is clear that these > pseudo-classes only apply to elements to which the "required" attribute > applies. > >

Re: [whatwg] [WF2] Label with empty for attribute

On Fri, 20 Jan 2006, Simon Pieters wrote: > > It is not defined what should happen when a label has an empty for="" > attribute. Consider the following example: > > foo > > Is the label element part of the .labels DOM attribute for the input? > What should the label's .control DOM attribute

Re: [whatwg] UA validation and the submit event

On Tue, 17 Jan 2006, Hallvord Reiar Michaelsen Steen wrote: > > Kayak.com is in trouble because they've set a maxlength that is smaller > than some of the data the script sets input value to. (I'm sending them > some feedback about that). However, the site shows an interesting > problem: the UA