`
softstone
  • 浏览: 484275 次
  • 性别: Icon_minigender_1
  • 来自: 北京
文章分类
社区版块
存档分类
最新评论

对Web标准的9大误解

阅读更多
Misunderstanding #1: "We Need Separate Print Pages"
This is old news, but why do I consider it noteworthy? Because it's the #1 application where media-dependent CSS, on top of media-independent HTML, ought to come into play... and yet, and I'm guessing, only 5% of all pages make use of it. You'd think after years of evangelizing done by web developers, the likes of CNN or Wired would have gotten the point.

Misunderstanding #2: "We Need an Alternative Mobile Web on Top of the Existing Desktop Web"
WML, the WAP's Wireless Markup Language, is dead today for a good reason: there was no need for this species in the course of web evolution. Even before WML was invented, plain vanilla HTML was created to be media-independent. Not by accident, but by design, because platform-dependence was one of the main problems Tim Berners-Lee tried to solve when inventing the World Wide Web and HTML.

Misunderstanding #3: "Accessibility Means to Always Use Alt Text"
The meaning of alt text is to serve as replacement (hence, "alternative") when the image the HTML intends to serve cannot be seen. There's a variety of reasons for that to happen; the user is blind, the medium doesn't support images, the user disabled images on purpose so she can browse on low-bandwidth, or the Googlebot comes around to visit.

Misunderstanding #4: "Sites Always Become More Accessible With CSS"
The biggest advantage of CSS is simply that it helps developers create websites much faster by separating layout and content. As far as that's possible, and it's certainly not possible 100% – which brings us to our next point.

Misunderstanding #5: "With CSS We're Completely Separating Content and Layout"
CSS doesn't completely separate content from its layout – only a template system can do that. CSS has its place on top of the template system, and greatly simplifies the HTML (if you think there's div soup today, you've got to see true 1996 table soup... it's worse.)

Misunderstanding #6: "With CSS, You Can Do the Design Later"
The real problem I'm seeing here, however, is that some people – heck, I was often one of them – tend to forget to add a fine-tuned design at all, happily using valid HTML + CSS as excuse for not having a page layout (relying on user stylesheets alone is not an option). Have you ever come across one of those black-on-white sites of nothingness, where the only graphical element is a "valid HTML" badge?

Misunderstanding #7: "The Web's Becoming More and More Accessible Every Day"
I think the biggest factor making accessible web sites a reality today is that most people simply don't do HTML anymore – they use ready-made blog templates. And several blog templates deliver good, strict (X)HTML.However, there's another movement throwing needles at the high-flying balloon of accessibility, and partly, usability; it's The Return of JavaScript (Episode III: A New AJAX).

Misunderstanding #8: "The Semantic Web is Just Around the Corner"
Today, the W3C is putting much of its efforts behind the Semantic Web (also described by Tim Berners-Lee in the second part of his book Weaving the Web). But Cory Doctorow put it so well back in 2001: people lie, and people are lazy. And I got a feeling even the W3C misunderstands why some of their web standards took off (they are relatively simple to apply, and certain complexities can be ignored without dangers), and I also got a feeling lower-case semantic web AIs, e.g. Google's Q&A feature, will be quicker to show results.

Misunderstanding #9: "CSS Hacks Are Always Superior"
Those hacks are fun, sure, but are they superior to HTML table layout hacks? Well, a little, but CSS hacks are still just that: hacks. Workarounds that will cause troubles with every new browser. Workarounds the new developer won't get when you're away, unless she's a CSS expert. So instead of thinking that CSS hacks are a great way of developing websites, it's better to use them sparingly and accept them as what they are: an often necessary evil.
分享到:
评论

相关推荐

    web标准设计页.pdf

    然而,在这一过程中,对Web标准的理解往往存在误解,例如认为Web标准等于使用DIV+CSS替代XHTML+CSS,或者误以为Web标准不允许使用JavaScript。 1.1 Web标准是什么? Web标准是由W3C(万维网联盟)和其他标准化组织...

    WEB标准化页面制作指南.doc

    WEB标准化页面制作指南是网页设计和开发领域的重要指导文档,旨在确保网站的高效、一致性和可维护性。以下是对这份指南的详细解析: 1. **引言** 引言部分通常阐述了编写该指南的目的,它强调了标准化在网页制作中...

    论web标准的网页制作和符合web标准的网站UI

    在描述中提到的“Div CSS谬误”是指国内开发者普遍将Div+CSS视为Web标准的代名词,这是一个误解。Div(文档对象模型中的一个元素)和CSS(层叠样式表)只是实现Web标准的一种方式,它们用于分离网页内容与表现,使...

    对JAVA语言的十个常见误解

    ### 对JAVA语言的十个常见误解 #### 误解一:JAVA是一种HTML编程技术 很多人误以为JAVA与HTML有着紧密的联系,甚至将JAVA视为一种HTML编程技术。实际上,JAVA与HTML是两种完全不同的技术。HTML主要用于定义网页的...

    《Web前端设计基础——HTML5、CSS3、JavaScript》课后答案整理.pdf

    - 采用Web标准的优势包括更佳的访问性、兼容性、可维护性和搜索引擎优化等。 4. HTML5文档结构 - HTML5文档基本结构包括、和等标签,其中标签定义了文档的标题,是中必须的元素。 - 元素是HTML文档的基本单元,...

    Web前端开发规范

    1. **促进团队一致性**:规范有助于确保团队成员遵循相同的标准和实践,这有助于避免误解和冲突。 2. **提升协作效率**:当每个人都了解并遵守相同的规范时,协作变得更加顺畅。 3. **塑造团队文化**:共同遵守的...

    Web开发用屏幕尺和屏幕取色器

    无论是设计师和开发者之间,还是在跨部门合作时,统一的尺寸和颜色标准都能降低误解,提升项目的整体质量。 总的来说,"Web开发用屏幕尺和屏幕取色器"是Web开发领域不可或缺的辅助工具,它们简化了设计和开发过程中...

    web前端开发的未来和发展

    他们负责实现设计概念,构建符合Web标准的可访问和响应式页面,同时还需要处理浏览器兼容性问题。前端开发者精通HTML、CSS、JavaScript,以及各种库和框架如jQuery、YUI等,还涉及到SEO优化、Ajax、DHTML和模块化...

    Tomcat与Java Web开发技术详解(第2版) ,重新制作了完整书签目录,附勘误表

    同时,书中还介绍了如何在Tomcat中部署WAR文件,以及对部署配置文件web.xml的解析,帮助读者理解应用程序的生命周期管理和上下文环境。 此外,书中深入剖析了Tomcat的工作原理,如请求处理流程、线程模型、session...

    web测试全面解析

    总的来说,Web测试是一个多维度的过程,旨在确保Web应用在功能、安全、易用性和技术兼容性等方面达到高质量标准,为用户提供无差错、安全且愉悦的在线体验。通过全面的测试策略和严格的测试实践,可以显著提升Web...

    Axure 8 Web前端 移动前端 后台 元件库 交互原型 系统框架.zip.zip

    元件库的使用使得设计过程标准化,减少了重复工作,同时也保证了设计的一致性。 2. **Web前端与移动前端设计**: 在Web前端设计中,Axure 8支持创建响应式布局,适应不同屏幕尺寸和设备类型。设计师可以利用其拖放...

    WEB应用程序UI模版代码编写及使用规范

    通过标准化操作,减少误解、重复工作和效率低下,提升团队的整体协作能力。 三、技术原则 1. 代码规范化书写:保持代码风格一致,有助于团队成员之间的协作和代码阅读。无论是个人的前后工作,还是团队成员间的...

    Web 站点设计规范.doc

    以下是对这些规范的详细说明: 1. **关于命名的约定**: - **一般命名约定**:遵循一致性原则,例如,使用小写字母、数字和下划线组合命名文件。默认的HTML文件通常命名为`index.htm`。命名应具有描述性,便于理解...

    Programming the Mobile Web.pdf 手机网页开发

    本书首先纠正了一些常见的误解,这些误解可能会阻碍开发者正确地进行移动网页开发。 - **“这不是移动网络;这只是网络!”** 这个观点强调了移动网络与传统桌面网络之间的一致性。虽然移动设备有其独特性,但底层...

    从四个方面谈谈Web标准的价值所在

    Web标准是互联网发展过程中的一个重要概念,它定义了一套规则和指南,旨在确保网页内容能够被各种设备、浏览器和用户无障碍地访问。Web标准的价值主要体现在四个方面:面向访问者、面向开发者、面向运营商以及面向...

    AxureUX交互原型Web元件库精简版.zip

    这个精简版的元件库可能包含了常用的按钮、表单元素、导航栏、菜单、滑块、图表等多种Web设计元素,这些元素都是根据最新的设计趋势和最佳实践定制的,能够满足大部分Web项目的初期设计需求。 使用Axure UX交互原型...

    Web前端开发的现状和未来.ppt

    这一变化反映了行业对专业技能的细分和重视,同时也催生了大量的前端技术书籍,如Web标准、Ajax、jQuery等框架的出现,推动了前端开发的快速发展。 行业内前端的位置: 前端开发在现代互联网产品中占据了核心地位,...

    W3C标准 W3C代码标准规范

    ### W3C标准详解 #### 一、W3C标准的目的与重要性 ...遵循W3C标准不仅是技术上的需求,更是对用户负责的表现。通过标准化的开发流程,可以构建更加健壮、兼容性强且易于维护的Web应用,为用户提供更好的上网体验。

Global site tag (gtag.js) - Google Analytics