I guess that I have the largest width of the available region for the text editor window because it only allowed me to extend the length of the page. This means that there is a grid style limiting this.
But I did learn that there is a “text” editor, the default is more WYSIWYG, into which you can code your own HTML. That is good. I can do that.
Font Size is More Important in Editing than Display
The very first lesson for using any editor by a low vision user is that he can read a much smaller font than he can edit for typos reliably. He may be able to read a normal font but because of his poor vision, he will need a much larger font to correct his typing.
Zoom in the Browser does not solve the font-size problem
I just proved this using the full-feature editor on my WordPress Site in its full screen mode. This mode is not responsive. That means if you zoom the text size the available viewport is smaller than the area used by the editor and because the text blocks are delimited by carriage-return, which is the convention used by WYSIWYG editors from Word on, formatting is not preserved. Going out of the full-screen mode remedies this but the padding chosen for the widget is so great that the viewport for the text entry is much reduced. If the padding is configurable, that would be a good compromise, but as supplied the WordPress editor is a good tool with a disadvantageous configuration. I am beginning to see an insidious force at play behind grid CSS designs that drive layouts on sites that cater to advertisers who want access to the right and left margins of the page. It is the case that users must fight with commercial interests for valuable screen real estate made crucial by the need for accessable and responsive designs.
Markup may help Low Vision Users more than WYSWIG
One of the reasons I have resorted to HTML and other markup approaches to drafting documents is that font size is not an issue for entering content. This is a problem because of the appearent ease of text entry with WYSIWYG editors in the mode of Microsoft Word. Provided a low vision could zoom and pan through the inputted text without spoiling its formatting, there is less of a problem overall. If the input font-size upsets the output then the use of markup must be considered, eg. TeX or HTML or XML. There are a host of specialized markups that are immune to zooming in the editor, so even though the typesetting standard might call for 12pt font, and the low-vision user might need to use 36pt or even 48pt font to edit that a markup would still produce typesetting to the standard required.
My vision is poor. I have concluded that Face Book would not comply with ADA Sec 508 if its user interface we used by any Federal Employee as an essential part of his/her job and the Face Book could be sued as a result.
Rather than find a lawyer I am trying to find a solution. I investigated the APIs published by facebook.com to see if there was a programatic solution; one that allows me to edit text with a comfortably large text and post to my Face Book Timeline. The font size used at the edit step is significant for low vision users to find and correct typographic errors. The ability of such users to read text at near-normal font size is not the same as the ease with which they can find and correct their own errors as they type. That can be a source of confusion for low vision people. The brain fills in content even when the error rate at seeing it accurately is high. High enough to lead to a large number of typos when they are entering text.
Face Book recently added functionality that allows for re-edits of comments in others’ Time Line posts, but did not extend this feature to the creation of Time Line posts themselves. If you want to correct one typo on a Time Line post you must delete and re-enter the post, and the only way to do that would be able to use your clipboard to copy the entire errant post to a temp file and copy and past the entire post back into the text area and correct formatting before send. In addition Face Book does not allow for direct uploading of a text file to the Time Line; to which my answer has been to post a screen capture of the content usually as an HTML page with style. That makes the point that not providing more than a text area costs Face Book more in resources to host an image of the content than if they accepted the content itself. I understand the security concerns of uploading users’ files, but they can’t be significantly more than hiding malware inside an image, which can be done. At worst Face Could allow only pure text or static HTML. Test areas don’t handle source code, although what is wrong with being able to post source code to your Time Line if your page was about programming, for example?
Anyway, I have been looking into alternative ways to get my ideas onto my Face Book Tine Line. An app of some sort from a third party might be a good solution. I heard about a WordPress plugin and I am going to explore that avenue.
I went to Stanford Univ. and live close to the campus and the local medical clinic is affiliated with the University Hospital, which is arguably one of the best such institutions in the world, so why, if the clinic I use is affiliated with the hospital and sends patients to doctors in the hospital staff. the billing remains totally separate? I am on Medicare and they pay most of the outrageous charges from the hospital, contrary to what Mitt Romney suggested, don’t use the ER, they will charge you or your insurance $2000 just to walk in the door and maybe up to twice that even if they don’t admit you to stay in the hospital, when the effective treatment amounts to what a Nurse Practitioner and OTC drugs could do.
Besides all that, the billing has months of latency and comes in drips and drabs, and although the clinic bills are easy to manage the hospital bills are easy to lose track of and wind up in collections, which invites more nightmares.
Oh, I have a working system at U 11.04, but it broke a few things and Upgrade Manager won’t let me upgrade further to get into a supported release. I filed a bug against the Update Manager because it doesn’t really help me to solve the problem, and some of the tools in the GUI are modestly broken because of the upgrade from Gnome 2 to UNITY and back to Gnome Classic. I really haven’t heard any good feedback except that my release is no longer supported, I knew that.