donate

The Martlet

Editorial: Current students left out by website redesign

May 01, 2008 | Volume 61 Issue 1 | 12 Comments
Share |
Gord Duff comic

Home should be a sight for sore eyes, not an eyesore. But UVic’s newly redesigned home page is causing headaches for those of us set in our ways.

It seems as though we’ve finally left the ‘90s and launched into the new millennium — not bad for the first drastic overhaul since the website’s creation. But websites are meant to be user friendly, and while the UVic site is certainly trying to befriend potential applicants — a noble goal — it’s left the current students stranded.

Granted, we’re supposed to be the university educated here, and most of us have been using the Internet for years, but there’s something reassuring about coming home. When “home” (be it in the form of a website) gets changed and moved around, we can’t help but feel at least a twinge of resentment.

As with any new launch the site is still working out its kinks, so criticism might be premature. But as soon as the UVic home page loads, the four main options are Apply for admission, Ask a question, Check application status, or Take a tour. What about those of us just wanting to check our WebMail, scan our grades on WebReg, or see this year’s timetable? We can still do that with the new site, but it’s not obvious or easy to get to.

UVic has added a handy “Who are you?” drop-down menu to access information personalized for students in specific groups — Aboriginal students, international students, mature students, newly accepted students and people interested in graduate studies. What category do the 19,000 plain old current students fall into, though? We’re pushed casually to the side.

Granted, we haven’t been left completely out of the loop — there is a “Current students, faculty & staff” button on the far right of the menu bar. We could feign anger over being placed last in the line of tabs, behind prospective students, parents and counsellors, prospective faculty and staff, alumni and donors, and visitors. But clicking our button only leads to a more confusing page that seems to encourage users to log-in to Campus Security services (a closer look reveals this placement is nothing more than a hair too close to the login site for uSource).

Maybe we don’t like change, but mostly we’re a little hurt. There’s something sad about losing the ease with which we could view our latest news around campus, surf the links (albeit often dead ones) about things we cared about — like the UVic calendar, or merchandise from the bookstore. Yes, we can still do that, but it’s kind of like losing your crib to the new baby in the family. We’ve been booted out, overlooked, left to navigate the cold world on our own, while UVic’s website laughs and coos over all the young-uns who demand its time. Fantastic.

The new website does house a “UVic Experiences” section, where web surfers can read the blogs of real UVic students, faculty and staff to see their experiences at the university. That could be construed as a little homage to us oldies, or as just another tactic for us to help reel in the newbies.

As far as finding basic info, such as when tuition is due, it almost seems necessary to be tech savvy. Sure, we could phone the registrar’s office, but isn’t the purpose of websites to have pain-free easy access to information?

The biggest complaint may be that everything about the site feels promotional. While there is an element of allure to the new shiny look (still laid out in those classic UVic blue, yellow and white overtones), it lacks the genuine feeling that the old site held tight.

We might just be whiny babies. After logging into uSource, the links can take you everywhere from news and on campus entertainment to finding out the current weather at UVic. These capabilities may outweigh those which the old site presented us with. And launching the new site was thoughtfully left until the beginning of summer, after the craze of finals ended. It just doesn’t make swallowing a new dose of change any easier.

Share |

12 Comments

The Martlet has an open comments policy and will endeavour to promote healthy discussion. We strive to act as an agent of constructive social change and will remove racist, sexist, homophobic, or otherwise oppressive comments.

Leave a Comment

  • Felix May 6, 2008, 11:26 p.m.

    If we all keep complaining about uSource, they'll eventually listen to us and get that text only link at the bottom working. Maybe if you say you're a visually impaired user and your screen reader can't make sense of all the javascript doilies, they'll be more inclined to listen.

    ~Felix.

  • Felix May 6, 2008, 11:26 p.m.

    If we all keep complaining about uSource, they'll eventually listen to us and get that text only link at the bottom working. Maybe if you say you're a visually impaired user and your screen reader can't make sense of all the javascript doilies, they'll be more inclined to listen.

    ~Felix.

  • DW May 7, 2008, 7:31 p.m.

    We are listening, and want to be able to provide an intuitive and user friendly interface. There is a project for the re-implementation of uSource, and as with the first implementation, we will be going out to the community (yes students) for consultation.

  • DW May 7, 2008, 7:31 p.m.

    We are listening, and want to be able to provide an intuitive and user friendly interface. There is a project for the re-implementation of uSource, and as with the first implementation, we will be going out to the community (yes students) for consultation.

  • Jane May 8, 2008, 6:49 p.m.

    Garth: Or you could just type wm3.uvic.ca into your address bar.

  • Jane May 8, 2008, 6:49 p.m.

    Garth: Or you could just type wm3.uvic.ca into your address bar.

  • Felix May 8, 2008, 11:02 p.m.

    DW: If my four or five oh for the love of god, don't roll it out the way it is! e-mails count as part of the first consultation process, I don't hold out much hope that you'll listen to us the second time around either.

    Some idiot will probably say I know! Let's re-implement the entire thing in Flash -- or better yet, Microsoft SilverLight! and manage to get that in place before anyone realizes.

    I think putting any javascript code in a system as important as student records and registration is a huge mistake. It should be implemented with plain, fast, mostly-textual pages, and all processing should be done server-side. In other words, largely the way it was before -- I understand that it was probably interfacing with some old VAX system covered in cobwebs via 9-pin serial cable, and I agree that such a system has to go -- but you can still do the new implementation in plain text.

    If you need better reasons than old school geek purity, try this:

    • it must work with screen readers and braille interfaces for the blind.

    • it must work on all web browsers on all computer systems. this is not an impossible task, if you stick to plain text.

    • instructions for use must be easily conveyable by telephone.

    • to minimize the amount of retraining, it should resemble the old system as closely as possible except in places where there's a genuinely good reason to introduce a new feature.

    ~Felix.

  • Felix May 8, 2008, 11:02 p.m.

    DW: If my four or five oh for the love of god, don't roll it out the way it is! e-mails count as part of the first consultation process, I don't hold out much hope that you'll listen to us the second time around either.

    Some idiot will probably say I know! Let's re-implement the entire thing in Flash -- or better yet, Microsoft SilverLight! and manage to get that in place before anyone realizes.

    I think putting any javascript code in a system as important as student records and registration is a huge mistake. It should be implemented with plain, fast, mostly-textual pages, and all processing should be done server-side. In other words, largely the way it was before -- I understand that it was probably interfacing with some old VAX system covered in cobwebs via 9-pin serial cable, and I agree that such a system has to go -- but you can still do the new implementation in plain text.

    If you need better reasons than old school geek purity, try this:

    • it must work with screen readers and braille interfaces for the blind.

    • it must work on all web browsers on all computer systems. this is not an impossible task, if you stick to plain text.

    • instructions for use must be easily conveyable by telephone.

    • to minimize the amount of retraining, it should resemble the old system as closely as possible except in places where there's a genuinely good reason to introduce a new feature.

    ~Felix.

  • DW May 9, 2008, 12:54 p.m.

    Ahhh.... Looking back at my ticket (I only have one from you) I have replied, but then looking at the mail headers you're not on them. I will E-mail you directly.

    Now, about accessibility, Javascript, and Jakob Nielsen :)

    There are some binding factors in our compatibility. We do try to meet and exceed WAI and Section 508 standards for accessibility. We also try to write our code such that it degrades nicely. We use jQuery so that the JavaScript is bolt-on and so that content is accessible without JavaScript, and we try to semantically markup and component-ize our code so that it can be syndicated or consumed through other means.

    Saying that though, there are a number of other factors at play including development costs, multiple contributers, time lines, vendor code bases etc...

    I also want to re-iterate that we are listening, and we will go out again for consultation (we usually ask for participation through the UVSS and the Martlet), so please feel free to participate.

    Cheers DW

  • DW May 9, 2008, 12:54 p.m.

    Ahhh.... Looking back at my ticket (I only have one from you) I have replied, but then looking at the mail headers you're not on them. I will E-mail you directly.

    Now, about accessibility, Javascript, and Jakob Nielsen :)

    There are some binding factors in our compatibility. We do try to meet and exceed WAI and Section 508 standards for accessibility. We also try to write our code such that it degrades nicely. We use jQuery so that the JavaScript is bolt-on and so that content is accessible without JavaScript, and we try to semantically markup and component-ize our code so that it can be syndicated or consumed through other means.

    Saying that though, there are a number of other factors at play including development costs, multiple contributers, time lines, vendor code bases etc...

    I also want to re-iterate that we are listening, and we will go out again for consultation (we usually ask for participation through the UVSS and the Martlet), so please feel free to participate.

    Cheers DW

  • Kramer June 6, 2008, 4:11 a.m.

    Will the program Timetable Assistant still work? Timetable Assistant makes it much easier to create your schedule. I believe the program gets its information from WebTT, and seeing as uSource is the new method of creating your schedule, I'm curious to see if Timetable Assistant will still operate.

  • Kramer June 6, 2008, 4:11 a.m.

    Will the program Timetable Assistant still work? Timetable Assistant makes it much easier to create your schedule. I believe the program gets its information from WebTT, and seeing as uSource is the new method of creating your schedule, I'm curious to see if Timetable Assistant will still operate.

 

Martlet Video

Sustainable Ecological Aquaculture:

The Martlet on Twitter

  • May 18, 2012, 6:27 p.m. It's not just "peaceful assemblies" under fire; Charest plans to withhold funding from student societies who don't play nice. #ggi #loi78
Join our mailing list