BlogmyQuery – BMQ

When the W3C unveiled the HTML5 logo earlier this week some people (including myself – see HTML5 now includes CSS3, SVG and WOFF?) felt that the message this sent made it more likely for people to confuse different web technologies.

One important reason for this feeling of added confusion was the wording in the logo’s FAQ, which stated that

The logo is a general-purpose visual identity for a broad set of open web technologies, including HTML5, CSS, SVG, WOFF, and others.

Read full post

Posted in HTML 5, Web Standards.

I doubt many of you missed it, but yesterday the W3C unveiled an HTML5 logo. Having a nice-looking logo for HTML5 is neat, but I think it’s unfortunate that the W3C are reinforcing the widespread misconception that HTML5 is pretty much anything “Web� that isn’t Flash.

Read full post

Posted in HTML 5, Web Standards.

When fine-tuning some media queries I noticed that layout changes seemed to happen at different window widths in Safari than in Firefox or Opera. When making the browser window narrower, media queries that specify a max-width kicked in a bit earlier in Safari.

The difference seemed to be around 15 pixels, so I thought it might be related to the vertical scrollbar. After reading the section about width in the Media Queries specification, I think Safari (and the other WebKit browsers I have tested in) are not following the spec, while Firefox and Opera are.

Read full post

Posted in Browsers, CSS.

In WordPress there are several ways of creating navigation menus. One way is to use the wp_list_pages function to output a list of pages. It works, but unfortunately the resulting HTML is less than ideal.

For many reasons I like my HTML tidy, without redundant class, id, and title attributes. I’ve found two different approaches to cleaning up the HTML created by the wp_list_pages function, and I’ll explain both here.

Read full post

Posted in WordPress.

Not that we have any drive-through ATMs (Automatic Teller Machines) that I know of here in Sweden, but apparently they are common in the US. These ATMs, like most others, tend to have Braille keypads, which understandably puzzles some people. If you need Braille to read the numbers on an ATM, you’re hardly allowed to drive a car, right?

One reason for drive-through ATMs having Braille keypads is that it doesn’t make sense for manufacturers to put different keypads on machines depending on where they will be used. It’s easier (and probably cheaper) to put Braille keypads on all of them. But even if that wasn’t the case, it still wouldn’t be pointless to have Braille keypads on drive-through ATMs.

Read full post

Posted in Accessibility.