=== leoquant is now known as Poison-Ivy === Poison-Ivy is now known as leoquant [13:25] is there a way for users to define their own stylesheets in a browser for accessibility changes? [13:26] kind of like how you can specify font settings that get applied over whatever the page says to use [13:28] if things aren't hardcoded, yes. but generally people don't like to use them because they break things and make it all look really ugly [13:28] (or at least, it's possible in firefox) [13:29] ok, so we'd have to provide users a way to enable/disable accessibility stylesheets [13:29] Pendulum: Possible in a lot of browsers [13:30] (we are taught that when we learn about precidence of styles :) ) [13:30] nigelb: the question was how to tell the browser to apply the accessibility styles, and when not to [13:31] so you could set everything at high contrast but you would have to view every website that way [13:31] there's no way to specify just for certain pages (afaik) [13:31] there are CSS media types for things like "speech" instead of "screen", are these used by browsers? [13:33] i don't actually know [13:34] if so, we can produce different styles for the Ubuntu web theme for these media types [13:34] http://www.devseo.co.uk/blog/view/pure-css-speech-bubbles [13:34] also not sure if this is implemented in any browsers: http://www.w3.org/TR/CSS2/aural.html [13:36] scrool to the bottom of the page on my link to see examples [13:37] UndiFineD: not what I was talking about [13:37] UndiFineD: i can't even read that link as the page is giving me a headache :-/ [13:38] Pendulum: how about something like tihs; http://www.w3.org/Style/Examples/007/alternatives.html [13:38] it works in Firefox at least [13:38] mhall119: your link was fine [13:38] not chrome, but I'm going to assume people who need accessible stylesheets won't be using chrome [13:38] is that a safe assumption? [13:39] tbh, I have no idea. I don't know what charlie-tca uses and he's generally our best test on accessible style sheets [13:43] okay, I'll look for him later, but I think if we can make an alternate, accessible style what people can switch to easily, that'll solve a lot of our ally bugs [13:46] http://www.w3.org/TR/2004/WD-css3-speech-20041216/ <-- is this the whole specification ? [13:46] yes! [13:46] mhall119: I would be totally in favour of that! [13:46] mhall119: also, talk to AlanBell because I think he may be willing to help [13:47] ok, I'm hoping the design team will give us some CSS to use [13:47] * AlanBell reads back [13:48] I will spend some time tomorrow to get such a page working [13:48] oh, ok. I think where I got on this was that newz2000 was going to let me write an accessible stylesheet and he agreed to probably not reject it [13:49] lol, good enough for me [13:49] I will put it on my own page, trying to get faisal spoken ;) [13:49] actually, I think we might want more than one accessible stylesheet for the different profiles [13:52] my initial suggestion was to install the simplemente theme as an optional theme [13:53] he would prefer to incorporate the features of that theme into the light theme like the navigation and screen reader support. I am not sure how practical that is. [13:53] and he talked about a stylesheet loaded through means as yet unknown, which would increase the font size and contrast [13:54] mhall119: is reset.css just something from the wiki theme or is it all over the place? [14:07] mhall119: problem with getting the browser to select an alternative stylesheet is that it doesn't appear to be sticky, so you go to a page of the wiki, choose your fancy high contrast stylesheet, go to another page and you are back to square one [14:16] AlanBell: reset.css doesn't sound familiar to me, so maybe just the wiki theme [14:17] hmmm, not using the same sheet across pages on the same site would suck [14:19] AlanBell: i'm fairly certain there's a way that should be able to make it sticky since other sites can [14:20] or are you talking about browser specific style sheets rather than stylessheets offered by the website itself? [14:24] Pendulum: I could easily be wrong [14:25] I went here in firefox http://www.w3.org/Style/Examples/007/alternatives.html selected one of the other sheets, hit refresh and it flipped back to the initial view [14:25] hmm [14:26] because the BBC definitely can get it right as the ouch! stylesheets stay across the site when you change pages [14:26] and considering how much they've messed up the ouch site otherwise... [14:28] I can only see "basic page style" and "no style" on the ouch site [14:36] mhall119: well, generally user stylesheets are first [15:13] nigelb: how do users assign sytlesheetS? [15:14] mhall119: users will have to create it. Like body {font-size: 20px;} in a mystyle.css and ask browser to use that [15:14] the exact options vary [15:14] I've heard some browsers allow per site user stylesheets [15:49] http://userstyles.org/styles/15509 [15:49] it is a browser plugin [15:53] it would be nice if browsers would send a "Enable Accessibility" Header attribute [18:06] ok, this works really well: http://imtranslator.net/Translator-For-Firefox-ImTranslator_v_3_3_5.asp [18:06] just tested it quickly [18:29] mhall119, what can be done is this: http://dl.dropbox.com/u/7607669/speech_useragent.png [20:12] UndiFineD: I don't really want to resort to making people setup custom UAs [20:13] no this is a step in between, i would rather offer something correctly [20:13] without changing [20:14] by the user [23:49] done a bit more on http://pad.ubuntu-uk.org/faisal