I write a lot. I'm writing this blog post in the rich text editor that's provided with WordPress, and I trust it will output nice clean HTML. This is good way of working, options often my writing involves much lengthier documents, and often I'm writing in collaboration with others. The tool of choice for these projects tends to be Microsoft Word, and often the final document will be published either in PDF or HTML. I also evangelize a lot, encouraging authors to take a few simple steps to ensure the documents they produce are options to readers with disabilities. Most authors I work with are writing and editing in Word, and when their document is finished they will publish and distribute it in PDF, motivated primarily by the desire to ensure consistency across platforms, and in some cases binaires protect it from modification. I'm also a Mac user, as are many of the people I work with. This blog post documents my quest for Mac-only solutions for converting Microsoft Word documents to accessible tagged PDF and clean, accessible HTML, but my lessons learned on this quest might apply to users pdf other platforms as well. First, let's consider what I mean by "accessible document". Here are a few basic features that an accessible document should have:. Here's a sample accessible Word document that I often use in trainings on this topic at the University of Washington. It has been prepared with accessibility in mind, and includes all of the features listed above. It includes an image with alt text, a main heading and multiple secondary headings, an unordered list, two tables with column headings identified, document language identified as English, and a single sentence identified as French. Regarding alt text, Word Windows and Options provide two fields Title and Description instead of one, with the idea that images sometimes require both a short and long description. This is analogous to the alt and longdesc attributes that have historically been used for this purpose in HTML. In my sample document, I've used both fields for testing purposes. Regarding data tables, my sample document includes both a simple and complex table. On the simple table, the header row can be flagged as a header row within Table Properties Row tabwhich helps screen readers to understand which cells contain the column headers. The complex table is more challenging to make accessible for screen reader users, and no word processing application, including Word, is up to the challenge. This level of detail is supported in both HTML and tagged PDF, but not in Word. Therefore, making the complex table accessible after converting to PDF or HTML will always require some post-production work, either in binaires HTML editor or Adobe Acrobat Pro. With all this in mind, I conducted the following tests using a few of the most common word processing applications:. Each of these tools is free and cross-platform except Word Perfect. That's two strikes, and I confess I'm only including this tool for nostalgic purposes. I learned to crawl as a computer user on Word Perfect, so I thought I'd try their day trial and see how they perform these days on accessibility. If their product is more accessible than all the others, perhaps this could be the key that turns their business around and enables them to regain prominence in the word processing market! Open Office and Libre Office are very similar products, as the latter was forked from the former in After four years of independent development though, there are a few important pdf between the two products as we'll see. All tools tested use heading styles similar to Word, and the import process successfully preserves the original heading structure. Alt text is, frankly, pdf bit of a mess. I intend to explore this in more depth in a future blog post, but for now here's a summary of what happens to Title and Description when a Word doc is imported into other tools:. To summarize, Libre Office is the only tool that successfully imports all alt text from the original Word document. The Table Properties dialog binaires Google Docs does not include any options related to row or column headers, so this information is lost on import. All other tools tested include a "Heading rows repeat" option or something similar, accessible within a Table Properties dialog. And for all of these tools, this setting survives the import from Word. Curiously, after importing my sample document, the primary document language was identified as French, apparently affected by the one French sentence at the bottom of the document. This doesn't seem to be due to options though as the same thing happens if the French sentence is moved to the top. In WordPerfect, the language of the document is correctly identified as English, but the language of the French paragraph did not survive the import. Open Office and Libre Office provide the best, most intuitive support for multi-lingual documents better than Word. After importing my sample Word document, the language of all parts is accurately identified. In Windows, when you create an accessible document using Microsoft Wordthen save as PDF, the default output is a "tagged PDF", which has most of its semantic structure and accessibility features intact. Unfortunately "tagged PDF" is not supported in Word for Binaires. In Word for Mac you can Save as PDF, but the output is not a tagged PDF, and therefore does not have the underlying structure necessary to support accessibility. All of the original document's structure and accessibility features have been lost. So to date my message has always been: You can create a reasonably accessible document in Word for Mac, but if you need to convert it to PDF you have to do that final step in Windows. This message is typically met with groans of displeasure from Mac users. And for some, it isn't even an option because they don't have convenient access to Windows. Also, there are some technical problems with this approach as fonts and other styles don't always survive the migration from one platform to the other. So, we desperately need a Mac-only solution for exporting to accessible tagged PDF. Although Windows is off the table as an option, it's worth examining the tagged PDF that Word for Windows produces. It's not perfect, but it's pretty good. The heading structure is preserved, unordered lists are tagged as lists, images include alt options using the Description field, not the Title fieldand table headers are correctly tagged as TH. One problem is that language is not preserved for foreign language content options the document. In my sample document, the overall document is identified as English, but the French paragraph is not identified as French. This is a significant problem for mixed language documents. Google Docs supports downloading to PDF, but the result is not a tagged PDF. All structure and accessibility features have been lost, just as with Word for Mac. All other tools tested provide an option to export to tagged PDF. It's doc checkbox located within the Settings dialog, which is accessible from the dialog that appears after you initiate the export process. In all tools doc option is not checked by default. Once checked, the output from Open Office and Libre Office is the most accessible output of all tools tested. It is comparable to the output produced by Word for Windows heading structure is preserved, list structure is preserved, and table headers are identified. The output from these tools differs from Word's output in two significant ways:. I should mention that in my sample document there is actually a problem doc the heading structure of my Open Office output: The main heading was exported to PDF as H6 rather than H1, despite its clearly using a Heading 1 style within Open Office. This may be a bug that's unique to my document, perhaps a problem with the original Word file or introduced during the import; I tried creating a new test file from scratch and my Heading 1 was correctly exported to H1 in that PDF. That said, this was not a problem with my sample document in Libre Office, so Open Office does seem to be at least partly at fault. Word Perfect's tagged PDF is not a good one. So, Word Pdf is not a serious contender. That said, for nostalgia buffs it's worth noting that they're the only tool that allows users to Binaires As WordPerfect 4. The thought of authoring web pages using a word processing application may make some of you cringe, and rightfully so. Microsoft Word is particularly notorious for generating code that is loaded with seemingly endless lines or proprietary markup even for doc simplest of documents. That said, Binaires understand authors wanting to use word processing tools. They have many features that are options designed to support writing and editing, and are particularly well-suited for collaborative authoring. Once a document is finished though, how should authors publish it for online distribution? Most authors seem to prefer PDF. I encourage authors to consider exporting to HTML instead, as it's much easier to make accessible and responsive, and it's truly an open standard whereas PDF's openness is debatable. But if we're going to encourage authors to distribute their pdf in HTML, they need to be able to convert their document easily. All of the tools tested, including Word for Windows and Word for Mac, now provide an option to export to a relatively clean HTML document, without proprietary markup. In recent versions of Word for Windows, this is the "Web page, filtered" option. In Word for Mac, the naming is a bit more confusing. There are two options for saving a document as a Web Page:. The first of these options XHTML produces a single file with image data embedded into the HTML. However, this is not well-implemented and from my testing yields buggy results that don't render well across browsers. Save As HTML seems to be the better of the two options. This includes an "HTML version" dropdown which provides a list of doctypes including HTML5. There's also a "Use relative font sizing" option. Both of these features are unique among all the tools I tested. However, don't get too excited. The only accessibility feature that survives the export to HTML is alt text for images. Valid code isn't necessarily good code. All other binaires generate HTML output with heading structure intact. It is worth noting that Open Office exports the main heading in my sample document as H1, not H6 as it did when it converted the same file to PDF. Google, Open Office, and Libre office also generate output with list structure intact. However, Microsoft Word does not. In both Word for Windows and Word for Mac, list items are tagged as paragraphs and contain symbol characters for bullets. Regarding alt text, all tools other than Word Perfect have options the Microsoft model and offer two fields for alt text, Title and Description. However, there are differences in which fields they use for output and how they deliver them. This is not the same for HTML as it is for PDF. Here's the summary for HTML:. Google is the only tool other than Word Perfect that does not support language somewhat surprising for the maker of Google Translate. There are no lang attributes in Google's output. Libre Office is the best of the tools tested at generating accessible tagged PDF. Its tagged PDF is even better than Word for Windows, given its support for language. So if you're a Mac user, or a user on any platform pdf needs to export multi-lingual documents from a word processing application to PDF, Libre Office may be your best bet. It also seems to import Word documents gracefully, so it might be a viable tool even in a collaborative environment where others are using Word. This would of course require more extensive testing. Neither Google Docs nor Word Perfect exports to an accessible tagged PDF, so neither tool can be taken seriously. For HTML output, either Libre Office or Microsoft Word could work. Open Office produced identical HTML output to Libre Office in my test, but I favor Libre Office of the two, given Open Office's clumsiness with importing my Word file and the apparent bug in which it exported my H1 binaires an H6 in the PDF test. If your documents include lists, Libre Office is better than Word since Word botches the lists. If your documents include both lists and tables, pick a tool and resign to the fact that you will have to do some work in an HTML editor to correct problems after exporting. And depending on which tool you use, note how it exports alt text and use the appropriate field s again, watch for a future post specifically focusing on this issue. All of the tools tested produce HTML files that include gobs of inline or internal embedded CSS styles. But I don't want any styles! When publishing to HTML, authors often will be publishing their documents to an existing website where style is defined in a CSS file. This is a strong use case for separation of content and structure from presentation. It would be great if tools would provide an option to "export content and structure only" but so far I haven't found one. I've tried using filters such as Word2CleanHTML. They do clean up Word's code, but they do so at the cost of accessibility. Another tool that may have once offered a solution is Virtual This tool was originally developed at the University of Illinois and doc formerly known as the Accessible Web Publishing Wizard for Microsoft Office. Unfortunately it doesn't seem to be actively developed anymore, as the home page proudly boasts of their new release that now supports Office I sent them pdf inquiry to check on status of the product but I never received a reply. Maybe, just maybe, the much-anticipated next version of Word for Mac will export to tagged PDF and generate good clean HTML that minimizes the need for post-export processing. Please stand by, and hope and doc In case you want to do some testing of your own, here are all the files I produced while doing this research:. Thanks for this, T. I will be reading back through this again today and may have some specific comments and questions. The last time I did a similar review with MS Office for the Mac v 11, SP1 was three years doc and my findings were similar to those reported here. I too recommended folks use LibreOffice on the Mac if they wanted to create accessible documents. I also recall getting very inconsistent results regarding the doc to pdf conversions. It is also "disappointing" that Office on the Mac does not work with VoiceOver. BTW, what did you use to "test" the PDFs for accessibility. There are some known bugs in the accessibility checker for Adobe Acrobat Pro that I do not believe have yet been fixed. At least one of them had to do with the language of the document reporting it was missing when it wasn't. Hi John, to test the PDFs I reviewed the tag structure using the Tags Pane options Adobe Acrobat Pro. Yet another option for converting from Word to HTML is the "Paste from Word" button in CKEditor. After copying and pasting the content from my sample Word document, then viewing the source, I see that headings, lists, and table headers are preserved; and alt text is a Word-like mashup of Title and Description. The only thing that's missing is a lang attribute on the French paragraph. Weekly Roundup of Web Design and Development Resources: Terrill Thompson is technology accessibility specialist with the University of Washington, web developer, musician, outdoor adventurer, and seeker of truth. All content of this website copyright - by Terrill Thompson unless otherwise indicated. Home Now Music Consulting Quick Tests Contact. Options for Accessibility Posted on June 30, by Terrill. Here are a few basic features that an accessible document should have: Headings and subheadings that clearly communicate the overall structure of the document. This helps screen reader users to understand how the document is organized, and users can easily and efficiently navigate the document by jumping between headings. Listsexplicitly marked up as lists so screen reader users can easily understand the nature of the content e. Alt text for images so people who are unable to see the images can access the message these images are trying to communicate. Language explicitly identified, both of the document and of any parts that deviate from the primary document pdf, so screen readers can accurately pronounce the text this is especially important in mixed language documents such as those used in a foreign language course. Then, repeat this procedure for each block of text that deviates from the default language. With all this in mind, I conducted the following tests using a few of the most common word processing applications: For applications other than Word, import my original Word binairesand examine whether the structure and accessibility features of the original document are preserved. Convert the document to PDF and examine whether the document's structure and accessibility features are passed on to the PDF. Convert the document to HTML and examine whether the document's structure and accessibility features are passed on to the HTML file. The tools I tested Microsoft Word for Mac and for comparison, Word for Windows Google Docs Apache Open Office Libre Office Word Perfect Each of these tools is free and cross-platform except Word Perfect. Importing from Accessible Word Importing Headings All tools tested use heading styles similar to Word, and the import process successfully preserves the original heading structure. Importing Lists Lists are also preserved, although not always as gracefully as headings. Open Office recognizes the list as a list the unordered list button is pressed when the list has focus but for my sample document it pdf unable to display the bullets correctly, and a new bullet had to be selected from the list settings. This was not a problem in either Libre Office nor Google Docs. In Word Perfect, the list is displayed correctly as a bulleted list, but the numbered list button is pressed, which I suppose makes my list an ordered unordered list. As it turns out, this ultimately doesn't matter because Word Perfect doesn't export list tags to either PDF or HTML, but I'm getting ahead of myself. Importing Alt Text Alt text is, frankly, a bit of a mess. I intend to explore this in more depth in a future blog post, but for now here's a summary of what happens to Title and Description when a Word doc is imported into other tools: Like Word, Google supports two fields named Title and Description, but they don't map accurately to Word's fields. The Title field from the original document is imported into Google's Description field, and Google's Title field is blank. The Description field from the original document is lost. Open Office and Libre Office have two features for specifying alt text. If you right click on an image within the document, the context menu includes a "Description" option which brings up a dialog that includes both Title and Description fields. There's also a separate "Alternative text only " field available in the Picture Properties dialog. This latter field actually maps to the Title field. In Open Office, none doc these fields is populated from the original Word file after importing. Libre Office has fixed this problem and both Title and Description are correctly populated after import. Word Perfect only has one alt text field, located in an "HTML Options" menu that's accessible from a context menu by right clicking on an image. This field is not populated doc either of the alt text fields in the original Word document. Importing Table Headers The Table Properties dialog in Google Docs does not include any options related to row or column headers, so this information is lost on import. Great post, thanks for doing all of the work and sharing everything. John Brandt on July 4, at 3: Terrill on July 4, at 4: Terrill on July 4, at 6: Subscribe via RSS About Terrill Terrill Thompson is technology accessibility specialist with the University of Washington, web developer, musician, outdoor adventurer, and seeker of truth.
La demonstration par A+B de l’arnaque des Options Binaires :
La demonstration par A+B de l’arnaque des Options Binaires :
Noe, Stephanie Marie (2009) Mechanisms of aluminum-containing vaccine adjuvants: Implications of the relationship between the movement of antigen in vivo and immunopotentiation.
May the Lord in His Kindness, Compassion and Understanding forgive me for these outbursts and pent up inner dispositions that have been and are mine. Amen.
WHAT the Jews do, WHY the Jews do it and, HOW the Jews do it.
Your arguing nonsense, if you read what I said, when a human becomes viable to live outside of the womb, then its to late for the mother to abort.
Noe, Stephanie Marie (2009) Mechanisms of aluminum-containing vaccine adjuvants: Implications of the relationship between the movement of antigen in vivo and immunopotentiation.
May the Lord in His Kindness, Compassion and Understanding forgive me for these outbursts and pent up inner dispositions that have been and are mine. Amen.
You are invited to the department party on Monday, May 11 from 12:15 to 1:30.