public marks

PUBLIC MARKS from Monique with tags standards & [en]

2012

The top 8 web standards myths debunked | Feature | .net magazine

Lea Verou takes a look at some of the misconceptions of web standards, what the W3C and its working groups actually do and how the standardisation process works

2011

Worldspace FireEyes « Deque Systems | Software, Training, and Consulting for Web Accessibility and Section 508 Compliance

Worldspace FireEyes is an unprecedented, nextgen web accessibility tool that ensures both static and dynamic content within a web portfolio are compliant with standards such as Section 508, WCAG 1.0, and WCAG 2.0.

2010

IE 9 does not resize text sized in pixels | 456 Berea Street

It would be great if IE behaved the same way as other browsers.

Proper Standards-Compliant Color Use in Web Design

Perhaps it is no secret to you that a good frontend design should be usable and accessible. That could be understood as having content that’s organized, readable, and understandable to everyone browsing the web, regardless of any impairment they may have.

Problems with Using Website Validation Services

This article aims to underpin the inherent issues of validating your websites through automated web services/tools and how using these tools to meet certain requirements can miss the point entirely.

Importance of HTML Headings for Accessibility

According to a screenreader survey, 76% of screenreader users use headings to navigate either ‘often’ or ‘all the time’. With that statistic we can’t argue how important headings are especially for people with disabilities.

2009

The importance of placement of HTML elements in a document « Marco’s accessibility blog

when you design dynamic content, write an accordeon widget or the like, please please please always take the time to chose an appropriate div element in the vicinity of where the user is, and add or remove the dynamic content there instead of taking the maybe easier, but far less intuitive, route to simply dump to the end of the document node’s children and then use some weird styling to craft it visually

Useful URLs

Useful URLs is a guide to URL design. It contains recommendations of best practice, along with explanations of the issues involved.

2006

Forget WYSIWYG editors - use WYSIWYM instead | 456 Berea Street

by 2 others
"Aside from those issues, which are very minor compared to the nightmarish markup most WYSIWYG editors spew out, WYMeditor is looking great. I really hope this editor catches on."

Visually Editing Semantics - What You See Is What You Mean- Standards Schmandards

by 1 other
But, if I was developing a CMS I would definitely monitor the progress of WYMeditor.

XHTML 2.0 versus HTML 5 (webapps 1.0)

by 1 other (via)
XHTML 2.0 is simpler than HTML 4.01 and HTML 5 (web Apps) by REDUCING the number of elements. Very interesting stastistics which is closer of the motto of the microformats.

Content-Type is dead - Hixie

by 4 others (via)
Discussion et tests sur le content-type HTTP, trop souvent ignoré par les clients Web

Clearance

by 2 others (via)
Blocs flottants, clear, overflow et scrollbars

Simple Clearing of Floats

by 2 others (via)
Blocs flottants, clear et overflow

March to Your Own Standard

Un code valide ou pas ? pourquoi ? (Mike Davidson)

BrainJar.com: CSS Positioning

by 7 others (via)
"To use CSS for layout effectively, it helps to know how it's used to position page content."

Tag Soup: Crazy parsing adventures

how browsers parsed HTML (Hixie's Natural Log)

Lessons From The Roundabout SEO Test

by 2 others
Tests de Mike Davidson à propos de l'influence du respect des standards sur le référencement

Invalid Code Can Get You Booted from Google

"invalid code, nested tables and some other HTML factors can affect rankings at the search engines"

Exploring Internet Explorer

by 5 others
Cascading Style Sheet Compatibility in Internet Explorer 7

SourceForge.net: WYM editor

(via)
Web-based WYSIWYM editor (What You See Is What You Mean), which goal is to produce XHTML-CSS compliant code. WYM editor lets the writer concentrate on the structure and the content of the document, not on the visual layout.