RE: [WSG]WCAG 2.0 enlarging text to 200% ?
Thanks for reply Patrick, very interesting - looking at that I do agree that it would be 6 steps according to the latest Firefox browser. I'm not really understanding this point very well and I'm not sure how this is measurable and testable across a wide range of platforms? What if the websites default size is set in percentage to 75% and then another website has default setting of 110%? --- Large scale (text) Note 4: When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text. Relative scaling can be calculated from the default sizes in a similar fashion. Heather -Message d'origine- De : li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] De la part de Patrick Lauke Envoyé : vendredi 12 décembre 2008 11:39 À : wsg@webstandardsgroup.org Objet : RE: [WSG]WCAG 2.0 enlarging text to 200% ? Heather With WCAG 2.0 finally coming out yesterday - I was wondering how many ctrl + clicks in (firefox for example) 200% is? I would say it was 3 but some colleagues argue 2 or 4 ? Any suggestions? I'd say conceptually that's quite a nitpicky argument...say a page broke spectacularly after 4 resize steps...would they then argue but it passes WCAG 2.0's SC, because it's 3 steps that go to 200%? Also, by default, Firefox 3 has whole page zoom (text, images and all) enabled, and has to explicitly be set to only resize text. With that said, go to about:config and look for toolkit.zoomManager.zoomValues, and this will show the various zoom factors at each step. In my case (which should be the default) these are: .3, .5, .67, .8, .9, 1, 1.1, 1.2, 1.33, 1.5, 1.7, 2, 2.4, 3 So, nominally 200% (which, according to the Understanding... bit for that SC, means 200%, that is, up to twice the width and height - so really a 400% increase in total area) is actually 6 steps, if you want to go purely by numbers. P Patrick H. Lauke Web Editor Enterprise Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 webmas...@salford.ac.uk www.salford.ac.uk A GREATER MANCHESTER UNIVERSITY *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: [WSG]WCAG 2.0 enlarging text to 200% ?
Heather With WCAG 2.0 finally coming out yesterday - I was wondering how many ctrl + clicks in (firefox for example) 200% is? I would say it was 3 but some colleagues argue 2 or 4 ? Any suggestions? I'd say conceptually that's quite a nitpicky argument...say a page broke spectacularly after 4 resize steps...would they then argue but it passes WCAG 2.0's SC, because it's 3 steps that go to 200%? Also, by default, Firefox 3 has whole page zoom (text, images and all) enabled, and has to explicitly be set to only resize text. With that said, go to about:config and look for toolkit.zoomManager.zoomValues, and this will show the various zoom factors at each step. In my case (which should be the default) these are: .3, .5, .67, .8, .9, 1, 1.1, 1.2, 1.33, 1.5, 1.7, 2, 2.4, 3 So, nominally 200% (which, according to the Understanding... bit for that SC, means 200%, that is, up to twice the width and height - so really a 400% increase in total area) is actually 6 steps, if you want to go purely by numbers. P Patrick H. Lauke Web Editor Enterprise Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 webmas...@salford.ac.uk www.salford.ac.uk A GREATER MANCHESTER UNIVERSITY *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG]WCAG 2.0 enlarging text to 200% ?
The way I read it, the 200% relates to 'twice the size the font appears at a client browser's default setting'. What if the websites default size is set in percentage to 75% and then another website has default setting of 110%? This 200% business is nothing to do with CSS font-size values. (Which depend on the absolute baseline size of the font on your site, set by either you of the browser's default) It's not measurable or testable. It's just there to highlight the fact that users need to (and want to) resize the font and that sites should allow them to do that. On 12/12/2008 11:19, Heather heat...@serensites.com wrote: Thanks for reply Patrick, very interesting - looking at that I do agree that it would be 6 steps according to the latest Firefox browser. I'm not really understanding this point very well and I'm not sure how this is measurable and testable across a wide range of platforms? What if the websites default size is set in percentage to 75% and then another website has default setting of 110%? --- Large scale (text) Note 4: When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text. Relative scaling can be calculated from the default sizes in a similar fashion. Heather -Message d'origine- De : li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] De la part de Patrick Lauke Envoyé : vendredi 12 décembre 2008 11:39 À : wsg@webstandardsgroup.org Objet : RE: [WSG]WCAG 2.0 enlarging text to 200% ? Heather With WCAG 2.0 finally coming out yesterday - I was wondering how many ctrl + clicks in (firefox for example) 200% is? I would say it was 3 but some colleagues argue 2 or 4 ? Any suggestions? I'd say conceptually that's quite a nitpicky argument...say a page broke spectacularly after 4 resize steps...would they then argue but it passes WCAG 2.0's SC, because it's 3 steps that go to 200%? Also, by default, Firefox 3 has whole page zoom (text, images and all) enabled, and has to explicitly be set to only resize text. With that said, go to about:config and look for toolkit.zoomManager.zoomValues, and this will show the various zoom factors at each step. In my case (which should be the default) these are: .3, .5, .67, .8, .9, 1, 1.1, 1.2, 1.33, 1.5, 1.7, 2, 2.4, 3 So, nominally 200% (which, according to the Understanding... bit for that SC, means 200%, that is, up to twice the width and height - so really a 400% increase in total area) is actually 6 steps, if you want to go purely by numbers. P Patrick H. Lauke Web Editor Enterprise Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 webmas...@salford.ac.uk www.salford.ac.uk A GREATER MANCHESTER UNIVERSITY *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** The information in this email and any of its attachments is intended solely for the addressees and is confidential. If you receive this message in error, please immediately notify the sender, destroy any copies and delete it from your computer system. The contents may contain information which is confidential and may also be privileged. Any part of this email may not be used, disseminated, forwarded, printed or copied without authorisation. Liability cannot be accepted for any statements, views or opinions made which are clearly the sender's own and not expressly made on behalf of any of the companies below. Global Radio UK Ltd (6251684), Global Radio Holdings Ltd. (4077052) Registered Office, 30 Leicester Square, London, WC2H 7LA This is Global Ltd (6288359) / Global Talent Group Ltd (3601691) / Global Talent Publishing Ltd (3509421) / Global Talent Management Ltd (4631297) / Global Talent Records Ltd (3598411) / Global Talent Music Ltd (5522116) / Global Talent TV Ltd (4506139) Registered Office, 73 Wimpole St, London. W1G 8AZ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: [WSG]WCAG 2.0 enlarging text to 200% ?
Thanks everyone for your answers. I'm much less confused now as I think I had misinterpreted the SC. Kind Wishes Heather -Message d'origine- De : li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] De la part de Gunlaug Sørtun Envoyé : vendredi 12 décembre 2008 13:14 À : wsg@webstandardsgroup.org Objet : Re: [WSG]WCAG 2.0 enlarging text to 200% ? Heather wrote: I'm not really understanding this point very well and I'm not sure how this is measurable and testable across a wide range of platforms? What if the websites default size is set in percentage to 75% and then another website has default setting of 110%? Doesn't really matter as long as it can handle 200% resizing measured against a browser's own web page normal text defaults. --- Large scale (text) Note 4: When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text. Relative scaling can be calculated from the default sizes in a similar fashion. Web page normal text defaults to 16px on 96DPI screens in nearly all my browsers on that resolution. Checking default-settings on other resolutions is easy, as one only has to override, or ignore, a page's own font-size declarations and leave the browser's own settings at default. Checking web pages ability to handle browser-defaults, usually messes up a large number of pages too a point where further testing becomes a purely academical exercise. So, when I really want to test if a page can take 200% font resizing, I blow it up by setting minimum font size to around 32px on my screens - that's 200% of browser's own default at my end. I use use such testing to see if my own designs are reasonable accessible when put under stress. Of course, this blows most designed web pages apart to a point where content becomes covered up and inaccessible, and then it doesn't matter much if someone has figured out whether these pages meet a WCAG checkpoint or not. Too much font resizing? Well, maybe. At least one is somewhat on the safe side with regards to that particular WCAG2 guideline if a document survives reasonable well and remains accessible and usable. Once that test is over it is time to zoom the page and see what happens... regards Georg -- http://www.gunlaug.no *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
