Recent Bookmarks and Annotations
-
WebAIM: Blog - JAWS ate my tables about 10 hours ago
-
We as blind people aren’t going to get full web accessibility until Jaws is no longer a factor. Freedom Scientific has shown, repeatedly, that they have no interest in working with standards bodies, following standards (either web standards or desktop standards like IAccessible2), or helping developers in any meaningful way. Currently, Jaws is one of the largest factors holding us back from full accessibility. We as users and concerned developers need to launch a marketing blitz similar to the one that’s made huge progress in killing off IE6. That’s the only way we’re going to see any improvement in the situation.
-
Documenting the Hacks: CSS Browser Targeting | bradKELLETT about 11 hours ago
-
Modernizr about 11 hours ago
-
definition: anchors, elements/tags (HTML markup) | Motive Web Design Glossary about 13 hours ago
-
Naming anchors
Tips and best practices for name and id values
-
name and id values must be unique within any one document, i.e. the same value should not be used for more than one element, however an element may have the same value for both name and id attributes- content authored to the XHTML 1.0 specification must use
id attributes to identify fragments [2]. For the purposes of backward compatibility, use the same value for both the name and id attributes. For example: <a name="pagetop" id="pagetop"></a>. This avoids potential complications with older (typically version 4) browsers not recognising the id attribute [3].
-
-
support for the
name attribute of the
<a> element is
deprecated in the
XHTML specification and is to be deleted from future
XHTML specifications
[4]
-
HTML Anchors with 'name' or 'id'? - Stack Overflow about 13 hours ago
-
<h1 id="foo">Foo Title</h1> is OK in both HTML4 and HTML5. This won’t work in Netscape 4, but you’ll probably use a dozen other features that don’t work in Netscape 4.
-
ID method will not work on older browsers, anchor name method will be deprecated in never HTML versions... I'd go with id.
-
-
There's no semantic difference; the trend in the standards is toward the use of id rather than name. However, there are differences that may lead one to prefer name in some cases. The HTML 4.01 specification offers the following hints:
Use id or name? Authors should consider the following issues when deciding whether to use id or name for an anchor name:
- The id attribute can act as more than just an anchor name (e.g., style sheet selector, processing identifier, etc.).
- Some older user agents don't support anchors created with the id attribute.
- The name attribute allows richer anchor names (with entities).
-
The whole "named anchor" concept uses the name attribute, by definition. You should just stick to using the name, but the ID attribute might be handy for some javascript situations. As in the comments, you could always use both to hedge your bets. | |
|
|
|
| |
-
How to insert line breaks into a Textarea with JavaScript on 2009-12-01
-
Textarea max rows and max characters per row - JavaScript / Ajax / DHTML answers on 2009-12-01
-
Basically, row1 and row2 are seperated by a new line character ("\n").
Word wrapping visually shows multiple rows however it is still the same row.
So to limit number of rows, simply count how much new line characters there
are.
-
-
Web standards 1.0 and 2.0 compared - New Zealand Government Web Standards on 2009-11-27
-
-
-
-
-
-
-
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
-
Note - where circumstances prevent full adherence to this standard, contact the
web standards team to discuss.
-
agencies must use macrons.
-
Unicode is a now a required technology
-
Status: No longer required. Sites may retain height and width attributes for images if desired.
-
-
Height and width attributes are specified in the IMG element
-
Provide metadata to pages and sites
-
Changed - pages now require only descriptive title tags
-
-
The alt text ends with a full point and a space
-
only corporate (or "main" sites) are required to supply publicly available reports.
-
Superseded material is marked as superseded
-
No longer required. although good practice.
-
by convention government sites don’t carry paid advertising.
-
User agents now support explicit associations of labels with form controls, so the "until user agents" clause has been satisfied
-
the mandatory link is to the website newzealand.govt.nz
-
-
Scrolling text is allowable.
-
"Tables for layout" is not explicitly addressed in WCAG2.0, but it is highly recommended that tables for layout are not used.
-
-
Advise users when spawning a new window from a link or a form control (3.2.2, below), and never on focus (3.2.1, below).
-
-
No longer required. Accesskeys are no longer required for conformance to WCAG 2.0. It is an advisory item:
-
-
The About page is now required to contain more links than previously
-
consistent navigation is a standard.
-
changed. We now default to the Yahoo! ratings.
-
sites must not rely on cookies to function, but rather, should use cookies for enhancement
-
fieldset still required. Note “legend” tag required also.
-
Aurgasm | your favorite music you've never heard on 2009-11-27
-
HTML Purifier Live Demo on 2009-11-27
Groups
Dan smith havn't joined any group yet.