My Plans for the Next Few Months

The last few months have been busy with helping run the last BarCampDC, interviewing and getting my current job as “Web Content Accessibility Manager” (big fancy title) for ARMY.MIL, and a bunch of other things.

BarCamp and AccessibilityCamp

In the near future I’m looking into when we might have the next BarCampDC, along with contemplating, doing an Accessibility Camp here in Washington, DC. I saw a twitter a few weeks ago about a group in San Antonio, TX, that did an accessibility camp.

We have started talking with the powers that be about getting a venue for the next BarCampDC, which we are thinking of doing in May or June. Hopefully we can get even more people to come out and enjoy the fun of BarCamp and maybe even give a talk on what they are passionate about. I’m going to try and get some more information about dates and locations for both events early next week before heading to Austin, TX, for SXSWi.

The other event I’m thinking of trying here in DC, is an Accessibility camp, which will probably be a lot smaller, with only two, maybe three rooms, depending on the number of people interested in attending. This one could go either way, meaning that a ton of people will want to come or just a dozen or two, I will have to wait an see.

The first item of the other three I need to start back working on once I’m back from SXSWi is a whole bunch of blog posts further explaining slides from my “Is Your Website Accessibile? If not, practical ways to make it so.” presentation.

Adding Video to Posts

The next item on the list would be to start using Clearleft‘s SilverBack application to create a bunch of tutorials explaining and showing how to use things like JAWS, other accessibility coding issues, and additional information for my blog posts. Silverback is spontaneous, unobtrusive usability testing software for designers and developers, uses the Apple iSight to record the person and all their movements and clicks on the screen. Seems to me to be a great way to create tutorials.

Conclusion

The final project would be to finish the two applications that I have been working on for the last year or so off and on. The two applications are an accessible version of Magnolia.com and a wine inventory system. It will be a way for me to learn both PHP and MySQL, along with creating more real world examples of how to do coding, using web standards and making your web application accessible.

What is everyone else looking to do in the next few months, especially after getting all pumped up after SXSWi?

Posted in Accessibility, Austin, TX, BarCamp, BarCamp DC, SXSW, Texas, Web Standards | 3 Comments

Times Running Out Before BarCampDC2

It seems like just the other day that we started planning for BarCampDC2 (like RefreshDC on steroids). When it was actually sometime in the middle of the summer and we never got serious until late August. Time is going by quickly and we only have less than two weeks before the actual event on Saturday October 18, 2008 at CDIA Boston University. I case you missed getting a ticket we are still taking names for the BarCampDC2 waiting list.

We managed to sell out the first set of tickets in about 36 hours, by just using twitter, a few blog posts, and a lot of word of mouth with probably some e-mails sent to friends and co-workers that they should sign up soon.

The even more amazing thing is we have have like 30 local individuals, big companies, and even a few start-ups willing to sponsor the event. They all chipped in a little bit here and some more over there so that you all could come to the event and not have to pay for anything. There are even a few people that are sponsors and will be out of town the day of the event, that’s how much they care about the DC geek community. Here is the list of sponsors we have now, I will update the list as we add more sponsors.

By them making donations you will get to have a continental style breakfast, lunch, snacks and drinks during the day, and a free t-shirt to commemorate the event.

Who knows we might have some extra money left for drink or food after. Not making any promises I have nothing to do with the money except making my contribution.

I would like to thank the following people for their great help so far, Justin Thorp, Shaun Farrell, Peter Corbett, Keith Casey, and others that have here and there.

The final great big thanks you has to go to CDIA Boston University and Bill Chenaille and the schools staff for lending us this great space to have the event in.

Posted in BarCamp, BarCamp DC, Boston University, CDIA, CDIA Boston University, Center for Digital Imaging Arts, DC Tech Events, DC Technology Network, Refresh DC, Washington, DC | Leave a comment

BarCampDC2 – October 18, 2008 – 9:00 AM – 6:00 PM

As you may have heard the registration for the for the BarCampDC2 event will open this evening (September 22, 2008) at around 8:00PM.

Here is some of the important information before registering you will need to know.

When

Saturday, October 18th, 2008, 8:00 AM6:00 PM

Where

Center for Digital Imaging Arts at Boston University
1055 Thomas Jefferson Street NW
Washington, DC 20007

Please make sure to only register if you know for sure that you can make it, since space is limited to the first 180 – 190 people. Also at time of registration you must choose your t-shirt size. The shirts should be American Apparel as I have been told and we will have women’s and men’s shirt sizes. For us larger guys, like myself we are planning on having sizes up to 3XL.

The ONLY place to register for the BarCampDC2 event is at the EventBrite website. Putting your name on the BarCamp wiki will NOT get you a seat at this event. Currently we have panel suggestions and will be adding more stuff there as time gets closer.

We are planning to have the panels be 45 minutes long and then have 15 minutes between sessions to get to the next room or mix and mingle with other BarCamp participants. Some more information to keep in mind.

  • Registration at 8:00 AM – 8:45 AM (submit panel talks at this time to help move things along)
  • Welcome BarCampers at 8:45 AM – 9:30 AM
  • Panels – 10:00 AM -6:00 PM
  • Lunch – around 12:30 PM
  • Event Ends at 6:00 PM
  • Clean up 6:00 PM -7:00 PM
  • Bar hopping afterwards 7:30 PM

We are looking for a few people to help set up Friday night (Oct 17) from 6:00 PM – 8:00 PM (?). Along with others to help out with registration, handing out t-shirts, helping with food, people to monitor rooms that others are not bring in food or drinks into the rooms, lunch, clean up after, etc.

So if you want to help please e-mail me at jfciii [at] jfciii [dot] com or on direct message me on twitter – @jfc3.

If we have not contacted you about sponsoring part of the event (max $250) and you would like to please contact me. For your sponsorship you will get your name on the back to the t-shirt (if payment in t-shirts are sent to printing), plus like two minutes in front of one of the panels about you or your company.

Hope you all will enjoy the event that a bunch of us have been working really hard to pull off.

Posted in BarCamp, BarCamp DC, Design, Design Patterns, Design Principles, Development, HTML, Information Architecture, Information Design, Programming, Refresh DC, UI, Washington, DC | Leave a comment

How to Hide “Required” from Visual Users, but Make it Available for All Others

How do most people usually designate that a field is “Required” in a web FORM? I would think that it is with an asterisk (*) after the actual INPUT field and it is sometimes made “bold” and “RED”. There are other ways to do this that are simple, use web standards, good design principles, and are 508 compliant.

When creating a FORM you should not make all fields required. By doing that nothing stands out to the person filling in your very important FORM. If most fields are required you should state at the top of the FORM or in the directions the fields that are NOT required.

Instead of just placing an asterisks after either the LABEL or the INPUT field in a FORM for a required field as most people do. You can actually place the word “Required” within the LABEL. Of course your using LABELs for your FORMS, along with FIELDSETs and LEGENDs.

Here is how to accomplish this for a web FORM and it can be easily accomplished by using a little CSS to hide the text that a field is “Required” to be filled in. The way to do this, that I use is to make it part your input fields LABEL. Here is an example of a few lines of code on how the code might look.

<label for=“username”><em>Required<em>User Name</label>

To hide the word“Required” you will be able to use the same CSS used for hiding “SKIP NAVIGATION” by adding a new class or stating that LABELs with an “EM“ in them will be displayed.hidden off the page.

Reminder please do not use “DISPLAY: NONE” in your CSS, since screen readers will not see it. Below is the CSS to visually hide the word “Required” from browsers.

.skip a, .skip a:hover, .skip a:visited, label em {
position: absolute;
left: -10000px;
top: auto;
width: 1px;
height: 1px;
overflow: hidden;
}

As you can see the CSS positions the link absolutely with a position of “LEFT” minus 10,000 pixels and a “TOP” position of auto. This will allow screen readers, Blackberries, Treos, etc. to see it but not browsers. That is as long as their CSS in turned on.

You can also place extra notes or instructions for a field inside the INPUT field with lighter text that is that will not go away once you start typing in the field. This can be done by using more CSS. Below is the XHTML code to accomplish this.

<label for=“username”><em>Required<em>User Name<strong>must not contain spaces<strong></label>

<input type=“text” name=“username” id=“username” size=“25” maxlength=“50” value=“”/>

The CSS to do this is fairly simple and follows below.

label strong {
color: #aaa;
font-size: .85em;
font-style: normal;
position: absolute;
top: 0;
right: -275px;}

Here is what the CSS is doing for the extra notes and instructions. It is first taking any STRONG elements within the LABEL and making it light gray color, the FONT-SIZE smaller and normal weight. After that it is absolutely positioned at the top left of the INPUT FORM field, as long as the LABEL is left or right justified to it and finally placing the information negative 275 pixels from the right of the beginning of the INPUT field.

Don’t forget to listen to your FORMs by using the Firefox extension Fire Vox. Here is an example how placing extra notes or instructions would look in a FORM, along with some “Required” field examples.

I hope this post is useful and further explains how to hide visual the word “Required” from my Accessibility presentation “Is your Website Accessible?”, please look for the most current presentation closer to the top of the list.

Posted in 508 Compliant, Accessibility, Adpative Technology, CSS, Design Principles, Development, Fire Vox, Firefox, FORMs, Helpful Tips, Helping Others, Layout, Programming, Screen Reader, Search, Skip Nav, Skip Navigation, Web Standards | 1 Comment

How to Set Up and Use Access Keys

Access keys allow people to use the keyboard instead of the mouse to perform certain functions. Mostly to move from page to page or a different section of the current pages content. By using web standards you can improve peoples use of your website.

Example HTML Code

The code involved to adding access keys to your website is very simple, you just have to add one extra piece of code to the links as shown below.

<li id=”about”><a href=”about.html” ACCESSKEY=”1″ tabindex=”300″>About</li>

Internet Explorer(IE), Firefox, Opera, and Safari each have their own way of using access keys. In most web browsers, the user uses the access key by pressing “ALT“ (on PC) or “CTRL“ (on MAC) simultaneously with the appropriate character on the keyboard.

The following are the different ways to use the access key function combinations broken by PC or MAC and then browser type.

PC

  • IE – press the “ALT“ key + access key and then press the “ENTER“ key to active the action.
  • Firefox 2.0“ALT“ + “SHIFT“ and access key.
  • Firefox 3.0“ALT“ + “SHIFT“ + access key and the“ENTER” key are required. I finally personally tested Firefox 3.o on Vista Basic and sometimes you need to hit “ENTER“ and other times you don’t. (UPDATED)
  • Opera – the user presses “SHIFT“ + “ESC“ followed by the access key (without “ALT“). Doing this will display the list of access keys over the current web page.

MAC

  • Firefox 2.0 -“CTRL“ + access key.
  • Firefox 3.0 – this has been changed so that the key combination only focuses on the link, “CTRL“ + access key and an “ENTER” is required after the access key combo. I have not personally tested Firefox 3.o as of yet.
  • Opera -“SHIFT“ + “ESC“ followed by the access key (without “ALT“). Doing this will display the list of access keys over the current web page.
  • Safari – “CNTL“ + access key.

Example Key Combinations

Here is an example of three access key combinations you can use for IE:

Text sizing buttons with Small (S), Medium (M), and Large (L) options.

  • ALT“ + “S“ to change to small text
  • ALT“ + “M“ to change to medium text
  • ALT“ + “L“ to change to large text
  • Finally you must click or press the “Enter “ button.

These key combinations are for IE on the PC and are used to set the text sizes that you want. You can make the text larger or smaller based on your preferences. This is what we have set up on my work website.

From some of the reading I have done I noticed that people that are creating mobile websites and applications, when doing so they are using just the numbers to make it easier for their users to navigate the website and application.

Please give these a try on your websites. I have access keys set up on my website, so please try using them with different browsers. If you have any issues please leave a comment.

Posted in Access Key, Accessibility, AccessKey, Adpative Technology, Best Practices, Content, CSS, Design, Design Patterns, Design Principles, Development, Firefox, HTML, Programming, Web Standards | 3 Comments