Required form fields in HTML5

One of many changes in forms that HTML5 is promising involves required form fields. In HTML 4 or XHTML, some scripting is needed to create a required form field.

With HTML5, there is a new attribute available for required form controls. The attribute is required. The browser or user agent will check on this and notify the user if the requirement is not met.

Here’s an example using an input element.

<label>Name: <input name="name" required></label>

Easy, right?

In HTML5, there is no need to use the syntax required="required". Dare I say it? In HTML5, all that’s required is required.

Make Rounded Corners with CSS3

There’s a new version of Cascading Style Sheets (CSS) in the works—CSS3. With this new set of rules for styling your blogs and web pages, you can do things that previously could only be done with images.

One bit of magic that you can do with a CSS style rule now is make rounded corners. You can apply rounded corners to borders, fieldsets, or anything that has a border line around it.

Everything on a web page is in a box. Every paragraph, heading or image you stick on a web page is bounded by a box. Usually you aren’t aware of the box, because you don’t see the borders—the boundaries of the box are not visible. If you put borders on the box, the edges of the box are made visible. Borders frame the element on the page and help separate one sort of content from another. The default borders create square cornered rectangles.

I’ve used rounded corners in several places on this blog. Here’s a specific example. I have a slideshow from Flickr in my sidebar. I put a border around the heading and the slideshow to separate that particular bit of content on my page into a unique element. I made the border have rounded corners.

The Rounded Corner How To

Find the relevant rule in your stylesheet. Every part of your page probably already has some style rules in place. If there’s already a border rule, change it. If it doesn’t have a border rule yet, add it. Here’s what I did in the part of my stylesheet where I styled the slideshow:

#womenintechslides {
border: solid 1px #3CF;
-webkit-border-radius: 8px;
-moz-border-radius: 8px;
border-radius: 8px;
}

I’ll explain the rule. I added the slideshow to my HTML page using a div with the ID “womenintechslides.” The rule styles that div. First I set the border itself. I made it solid. I made it 1px in width. I made it an aqua color represented by the code #3CF. That much alone would add a border, but the border would have square corners.

The CSS3 property that rounds corners is border-radius. For that property, give a value in pixels to set how curved you want the corner to be. If you go beyond about 18px for the radius, it starts to look bad (pixelated), but try various numbers to find what you like.

CSS3 isn’t set in stone yet. The various browsers are adopting bits of it at different rates. You have to add a couple of redundant border-radius declarations aimed at different browsers, at least for now. The -webkit-border-radius declaration is meant for webkit browsers like Safari and Chrome. The -moz-border-radius one is for mozilla browsers like Firefox. If you put the standards rule—border-radius—last, it will be the one used when all browsers finally get CSS3 implemented using the same rules. By that time, you’ll only need the border-radius rule and the others can be dropped.

That’s the whole magic trick: border-radius. Go round something off.

CSS Summit

Environments for Humans is putting together the 2nd online CSS Summit for July 28. If you are teaching CSS and want to get an intensive (and interactive) training session on CSS3 right at your own desk, I suggest you check this out.

I just attended an Environments for Humans (e4h) summit and can testify to the fact that it went well technically, the speakers were excellent, the interaction is immediate, and the presentations were top notch. The CSS Summit has a wonderful roster of speakers and promises to be a great CSS3 learning experience.

Act fast, the first 50 tickets are a bargain.

Useful Links: SVG, BAM, InterACT

Doug Shepers from the W3C put together a slideshow in SVG, HTML, CSS and JavaScript that is worth your time. It’s an SVG demo. Play with it. View it in the latest Firefox.

BAM or Blog Accessibility Mastermind is a six lesson course offered by Glenda Watson Hyatt of Do It Myself Blog. I haven’t looked inside the course, but I suspect it’s a good one.

Based on the interest and number of questions Derek Featherstone got during his accessibility presentation at the recent InterACT Summit, I’d say interest from educators about accessibility is very high right now. There’s a free online course from the Web Standards Project (WaSP) InterACT curriculum about accessibility. The course is a perfect resource for teachers. It’s a stand alone course. If you are teaching with InterACT with Web Standards and its chapters on accessibility, the online material a great time saver. Online materials such as exam questions, grading matrices, assignments, objectives, and resources go hand in hand with the material in the book.

Is this support call hilarious? What do you think?

A call for help with a technical problem to a line called Builder Support is making the rounds of the Internet. During the anniversary of Pac-Man last week, there was a small Pac-Man game on the Google search page. The call is about that noisy Pac-Man game. Most people think it’s worth linking to and tweeting about because it’s hilarious. Here’s the call.

Did you think it was hilarious? Or even a bit funny? Responses from Twitter all retweet the idea that the call is hysterically funny. This person also called it a Google fail.

Check this video out — Old Lady’s Google Pac-Man Problem: Hilarious Tech Support Call http://youtu.be/xYWuW7_WfJU GOOGLE FAIL!!Thu Jun 10 20:12:23 via web

Everyone also assumes it is an old lady calling, a senior citizen. Who else could be so ignorant, right?

Old Lady Calls Tech Support To Remove Google Pac-Man–Hilarity Ensues http://huff.to/9UuJb5 #LOL /via @low78Thu Jun 10 20:10:03 via Twittelator

The headlines on Alltop and Techland both refer to the caller as either an old lady or a little old lady. The people at College Humor were particularly unsympathetic. I guess college kids never feel stymied by new information.

These are my feelings about the call.

  1. The support dude, Brian, was rude initially and actually laughed at the woman’s question. Why isn’t anyone talking about that?
  2. The caller, on the other hand, was very polite. She even asked if he had time to stay on the line while she tried his suggestion.
  3. After about three minutes of useless conversation, Brian finally figures out that he really does need to do something useful to help the woman with her problem. He doesn’t explain it very well, but he finally manages to get her to shut down the browser tab for Google. He doesn’t mention the volume control icon next to the game display.
  4. Who says she’s old? She’s a woman. She doesn’t know much about using a browser. Does that make her old? Is her polite behavior a symptom of age? You could argue that her voice “sounds old.” On the other hand, I am old, but people constantly tell me my voice sounds “young.” (Like this interviewer did.) Am I young or am I old on the phone? Why does it matter?
  5. Why is it funny? Was everyone who laughed born knowing how to close a browser tab? I don’t think so. They had to learn the first time just like the caller did. Is the experience of learning to close a browser tab different at age 6 than at age 96?

I’m pretty tech savvy. The other day my granddaughter brought me her netbook to show me something. I couldn’t figure out how to scroll down the page. Turns out there was a lovely little device next to the track pad meant just for scrolling. But I didn’t know that. I couldn’t read the page. Even the most accomplished user has an occasional moment of beginner’s mind. This story rubs me wrong because of the assumption that anyone so afflicted with a case of beginner’s mind regarding a browser problem must be old.

Maybe you don’t agree with me. Maybe you think the call was the funniest thing you’ve heard in years. Or maybe you’d like me to shut up because my complaints about ageism are bugging you. Don’t worry, they’ll be gone tomorrow. (Maybe.)

Cross-posted at BlogHer.

Useful links: Documentation, help files, child bloggers

Talk documentation to me lists some common sense steps for documenting a process. One of my pet peeves around the explosion of web apps, iPhone apps, and explosive new tools like Twitter is that the documentation and help information is inadequate. Putting someone in charge of documentation is always a good idea.

The Twitter Help Center is a good example. There was always something in the Twitter help files, but it was not very helpful for a long time. Now there are video tutorials on everything from how to retweet to how to find people. Twitter even has a YouTube channel for their videos.

How Young is Too Young? at Techipedia takes a look at successful child bloggers, some as young as 10. The kids respond to some questions about young bloggers and offer advice for young bloggers.

Useful Links: CSS3, elderbloggers

Showing and hiding content with pure CSS3 is a good tutorial from Opera developer Corey Mwamba.

Where it happens when you’re an elderblogger is one of the many things tossed around on Time Goes By. By that I mean, where the blogging happens. (Your mind doesn’t have to automatically go to those strange places, so stop it.) Here’s a series of photos showing where the elderbloggers blog.