Potential Three Ships Requests

[alixtii]

Fandom: Bones
Pairing: Temperence Brennan/Peyton Perotta/Daisy Wick

Fandom: Sarah Jane Adventueres
Pairing: Rani Chandra/Maria Jackson/Luke Smith

Fandom: Stargate: Atlantis
Pairing: Samantha Carter/Jennifer Keller/Rodney McKay

Fandom: Stargate: Atlantis
Pairing: Samantha Carter/Rodney McKay/Jeannie Miller*

Fandom: Sanctuary
Pairing: Clarra Griffin/Will Zimmerman/Kate Freelander

Fandom: Veronica Mars
Pairing: Cindy Mackenzie/Veronica Mars/Madison Sinclair

Fandom: Veronica Mars
Pairing: Cassidy Casablancas/Cindy Mackenzie/Lilly Kane

Fandom: Transformers (2007/2009/2011)
Pairing: Mikaela Banes/Maggie Madsen/Carly Spencer

Fandom: Veronica Mars
Pairing: Cindy Mackenzie/Keith Mars/Veronica Mars*

Fandom: Harry Potter
Pairing: Draco Malfoy/Pansy Parkinson/Ginevra Weasley

Fandom: Chuck
Pairing: Chuck Bartowski/Ellie Bartowski/Sarah Walker*

Fandom: Chuck
Pairing: Ellie Bartowski/Alex McHugh/Sarah Walker

Fandom: Chuck
Pairing: Ellie Bartowski/Sarah Walker/Anna Wu

Fandom: Chuck
Pairing: Chuck Bartowski/Jill Roberts/Sarah Walker*

Comments

qyxQOaalkxnD

[(Anonymous)]

Interesting. I wonder how much of the prlbeom stems from lack of education. I doubt that it is the whole prlbeom given that issues aren't always(often even) fixed after they are bought to the designers attention. However as I read though the article I realized that I have taken 5+ college level computer science courses* and none of the addressed the spefic accessibility issues you mentioned at all. In fact IIRC only the most recent of the classes covered accessiblity at all(we spent about a minute on it). I still only kinda understand why the preview screens are a prlbeom and thats just because I read sites like this. Even assuming that it doesn't make them actually care more about accessibility it's way easier for someone to realizes for themselves in advance that a feature is going to be inaccessible to scrap it/fix it with methods they already know than it is for someone to:admit they made a mistake, go back to something they though they were done with improvise a new design, integrate the changes into an existing site, program ect and deal with the backlash from non/differently disabled users who liked the site the original implementation. Trying to outright remove the feature would genrally run into the sunk cost faclicy and even more backlash from users who like the feature not to mention the loss of face for who ever decided the feature was a good idea in the first place. On a semi-related note does anyone have any good recouces on how to desing more accessible interfaces?*Which admitatly don't yet include HCI or the other interface heavy courses that would be the most likely source for this sort of info and could be non-indicative of the state of computer design education overall.